Chrome has had a bug for ~6 months where for certain TLDs, it searches instead of going to the typed url. It happens for .no. Google isn't incentivized to fix it, since they now most likely get a visitor on their search page and earn some money.
Combined with a different issue, this is fairly dangerous: Google allows fake scam websites to pay to get the top ad. Above the URL you ended up searching for.
There are cases of people writing skatteetaten.no (our IRS) in Chrome, ending up in google search instead, and they then click the top result which is a phishing site stealing their credentials.
Why should I try? I don't use Chrome. I don't care about jumping through hoops to do free work for a big scummy company. I only knew of it from news reports recently after it finally got fixed.
Anyway, Chrome's responsiveness on some random issue isn't at all representative of Google as a whole, which of course, it is impracticable for laypeople to communicate with a real person there.
That, and also the plethora of search suggestions like 192.168.O.1 (notice anything wrong?) happily presented up there. No, DDG doesn't show them, so yes IT IS possible.
Combined with a different issue, this is fairly dangerous: Google allows fake scam websites to pay to get the top ad. Above the URL you ended up searching for.
There are cases of people writing skatteetaten.no (our IRS) in Chrome, ending up in google search instead, and they then click the top result which is a phishing site stealing their credentials.