Context: For 13 years, Firefox had a test for the internal “Page not Found” page. That test loaded www.some-nonexistent-domain-27489274c8927.com.
This week, the test started to perma-fail in our CI. Why? Someone registered that domain.
Oh god. Not every computer is a VAX, not every port number 80, not every domain a .com. We have .invalid for a reason.
Yeah, the domain was changed to .test then.
.test is appropriate. A good resolution at least.
For those playing along at home, the actual domain in the ticket is www.some-nonexistent-domain-27489274c892748217cn2384.com, not www.some-nonexistent-domain-27489274c8927.com as listed in the description. The latter is unregistered, the former was registered on September 20 at 05:42Z.
The website is hosted on AWS us-east-1 (static Name Bright ‘site coming soon’ thingy), but the server that the root domain resolves to is on German hosting provider Contabo. The Contabo server is running wordpress, and the content looks to be low-effort with a lot of repetition. Seems shady.
[ec2-user@mybox ~] ping some-nonexistent-domain-27489274c892748217cn2384.com
PING some-nonexistent-domain-27489274c892748217cn2384.com (18.104.22.168) 56(84) bytes of data.
64 bytes from vmi948408.contaboserver.net (22.214.171.124): icmp_seq=1 ttl=59 time=84.5 ms
[ec2-user@mybox ~] ping www.some-nonexistent-domain-27489274c892748217cn2384.com
PING cdl-lb-1356093980.us-east-1.elb.amazonaws.com (126.96.36.199) 56(84) bytes of data.
--- cdl-lb-1356093980.us-east-1.elb.amazonaws.com ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 6083ms
How much do we want to bet that some domain swatter is partly to blame here?
Maybe someone scraped it off the source code, yeah. Probably more likely than a troll who’s reading tests for 13yo bugs and has a free extra domain in some plan, waiting to be claimed.