[userbinator]

So if you have a user named "haha_funny" you already aren't allowed to give them the hostname "haha_funny.somesite.example" - and on some system it will just silently not work because it's invalid.

Not long ago I actually did come across a site that had an underscore in its domain name, and it worked both for me and apparently Google, because it indexed and showed a (relevant) page from that site. I only remembered it was on a *.tripod.com subdomain, and can't find that exact site now since I don't remember what I was searching for (it was a highly obscure and technical topic), but there do appear to be others there with underscores, e.g.:

http://computer_collector.tripod.com/

http://hattori_striker.tripod.com/

http://forgotten_dark_angel.tripod.com/

[pests]

In 2019 the CAs agreed not to issue certs to underscored subdomains making this less useful.

As evidenced by all your links being http.

(as an aside, it looks really weird seeing a bare http link in the wild - crazy that was the old norm!)

[tialaramex]

My browser is configured to auto-upgrade such links and I get a full screen interstitial when the upgrade fails (as of course it did for these)

This is now at a place where I'd recommend such configuration more broadly, it's not suitable for everybody, but many could benefit from just knowing all links are secured.

[jesprenj]

Wildcard certs match subdomains with underscores, as pointed out by a sibling comment. Example: https://_.4a.si./

[aaomidi]

A wildcard would still work for these fwiw

[jesprenj]

Google also indexed my site http://_.4a.si as seen here http://google.com/search?q=site:_.4a.si

[rvnx]

A live proof that CNAME records starting with _ exist.

[tialaramex]

There are.

There shouldn't be, but there are.