February 25, 2026
TLD? More like TL-Don’t!
Never Buy A .online Domain
Google slaps a red warning, the registry pulls the plug, and the crowd yells “stick to .com”
TLDR: A free .online domain was flagged “unsafe” by Google and then suspended by the registry, creating a no‑win loop where verification was impossible and the site vanished. Commenters blame Google’s power, swear off non‑.com domains, and swap horror stories about pricey, risky niche domain endings.
A freebie .online domain sounded cute—until it triggered the dreaded full‑screen “unsafe site” warning and then got frozen by the registry. The author says Google’s Safe Browsing labeled the site dangerous, the registry (Radix) put it on “serverHold” (basically a registry-level shutdown), and now there’s a catch‑22: to clear the warning, Google needs domain verification via Search Console, but verification requires the domain to resolve… which it can’t, because it’s frozen. Oof.
Cue the comments: the top‑voted mood is “this is what happens when Google can nuke you without notice.” One user calls it the peak of “enshittification.” Another camp goes full .com or die, yelling that weird top‑level domains (TLDs—those endings like .online, .site) are spam magnets and pricing traps. Doubters push back: are we really saying only .com and maybe .org are safe? Meanwhile, confused onlookers ask what Search Console even is and whether they need to rush all their domains into it.
Then the war stories arrive. A domain owner claims a rare .icu renewal jumped from $20 to $220 overnight, fanning fears that “exotic” TLDs lure you in then gouge you later. The memes write themselves: “red page of doom,” “TL‑D’oh!” and lots of “just buy .com.” The final vibe: a messy internet bureaucracy meets automated bans, and small sites get caught in the crossfire.
Key Points
- •A .online domain was registered via a Namecheap promotion with a $0.20 ICANN fee and set up using Cloudflare and GitHub.
- •Weeks later, Google Safe Browsing flagged the site as unsafe, and the domain stopped resolving; WHOIS showed a serverHold status.
- •Namecheap confirmed the issue was registry-level, and Radix stated the domain was on Google Safe Browsing, requiring Google delisting before reactivation.
- •Google requires Search Console verification (via DNS records) to request Safe Browsing review, but verification was impossible due to the domain’s non-resolution.
- •The author filed multiple false-positive reports and requested a temporary release from the registry, and later reflected on not enabling Search Console early or uptime monitoring.