My primary domain (captnemo.in, where you’re reading this) was suspended by my registry (.in) for 3 hours last night (4th May 2026). I discovered the issue roughly 30 minutes after it happened, at around 22:45 CET and managed to get on chat with a Namecheap representative in the next 30 minutes, and both domains unsuspended in another 90 minutes or so. It took a lot of waiting for support to “unlock” the domain so I could go and edit the whois records. The reason for suspension, as mentioned in the namecheap dashboard was “invalid whois”. For context, the .IN TLD does not support whois privacy. I was aware of this limitation, and had never enabled WhoisGuard on these domains. In fact, Namecheap does not let you enable or purchase WhoisGuard for .in domains. The only WHOIS information I’d ever submitted to namecheap was my actual address in India. However, a namecheap bug (as confirmed below) led to an issue where domains that were transferred into namecheap (and not purchased on…
No comments yet. Log in to reply on the Fediverse. Comments will appear here.