A developer got a free .online domain on Namecheap for a simple web app. The site was super simple: just a few screenshots and a link to the App Store
Everything was fine until, a few weeks later, traffic hit zero. Instead of his site, he saw the dreaded "This site is unsafe" red screen. Google had blacklisted the domain, even though there was absolutely nothing wrong with the content
The worst part wasn't the ban itself — it was the recovery process. Google asked for DNS verification to prove ownership, but Radix (the domain registry) had put the domain on "serverHold", meaning it wouldn't resolve at all. He couldn't prove he owned the site because the registry wouldn't let the site exist. It's a loop
In the end, it took a stroke of luck. After posting the story on Hacker News, the post got enough attention that an "unknown Google hero" manually cleared the blacklist. Only after the flag was removed did the registry finally release the domain and let the site back online
The Lesson
- Stick to .com domains
- Always set up Google Search Console from the start so you have a way to talk to Google if things go wrong
- Use uptime monitoring so you don't find out about a ban too late
Top comments (0)