Experiences of sites created with '.online' domains becoming inoperable
While '.com' and '.net' are the dominant endings of domain names, known as '
Never Buy A .online Domain | Sid's Blog
https://www.0xsid.com/blog/online-tld-is-pain
Web developer Sid got a '.online' domain for just $0.20 (about 31 yen) because domain hosting service Namecheap was running a promotion that allowed each account to get one '.online' or '.site' domain for free. Sid thought that since '.online' was easy to set up with Cloudflare and GitHub, there would be no problems with operation.
However, a few weeks after purchasing the domain, the buyer was reviewing the domain's traffic data and noticed that the site had had zero visitors in the past 48 hours. When they accessed the site, they were greeted with a warning that the site was not secure. After clicking the disclaimer and attempting to load the site, they were presented with a 'site not found' error, rendering the site inaccessible.
Since Namecheap isn't exactly reliable, Sid contacted the registrar and found that the domain was listed correctly in his account, with the correct nameservers and expiration date. He also checked his email address and found no error messages from the registry, registrar, host, or Google.
Sid contacted Namecheap, who replied, 'Domains of this type are sometimes put on hold for being involved in fraudulent activity. We're sorry, but Namecheap did not suspend the domain, so this is not an issue Namecheap can resolve.' Namecheap then directed him to RADIX, the administrator of the '.online' TLD, which told him that the domain name 'getwisp.online' (Sid's domain) had been suspended by Google, who told him, 'The domain name 'getwisp.online' (Sid's domain) has been blacklisted by Google Safe Browsing and is currently suspended.'
If a site is found to be falsely blacklisted by Google, it can be removed, but the owner must verify the blacklist through Search Console in order to do so. In this case, the site could not be displayed because the domain itself was blacklisted, and it was not even possible to proceed with the necessary steps to verify rights or request a reconsideration.
He eventually shared the incident with the social news site Hacker News, and Google responded within 40 minutes, removing his site from the blacklist. While Sid's site was eventually brought back online, he cited his key mistakes as choosing a new TLD like '.online' instead of the more reliable '.com,' not registering with Search Console early on, and not implementing monitoring tools or access monitoring.
Sid said, 'I don't know if this problem was caused by a strange TLD or if it was a concentrated attack due to some kind of report,' but concluded, 'I will never buy any other TLD again. The TLD should be '.com'.'
Related Posts:
in Web Service, Posted by log1e_dh