Either Namecheap or INRegistry is wrong
twitter.com
Either Namecheap or INRegistry is wrong
1–5 of 5 posts
Re: Either Namecheap or INRegistry is wrong
#2Update:- Looks like INRegistry and Namecheap will communicate directly.
Re: Either Namecheap or INRegistry is wrong
#3I had a long email discussion with Namecheap and they said that INRegistry is the one to blame. Now INRegitry said opposite of what Namecheap said. I am seriously confused which of these two are wrong. One is wrong for sure. Update:- Looks like INRegistry and Namecheap will communicate directly.
Re: Either Namecheap or INRegistry is wrong
#4I had a long email discussion with Namecheap and they said that INRegistry is the one to blame. Now INRegitry said opposite of what Namecheap said. I am seriously confused which of these two are wrong. One is wrong for sure. Update:- Looks like INRegistry and Namecheap will communicate directly.
.in has forbidden whois privacy for literally years, since its formation. India is also not exactly.. subject to GDPR
Re: Either Namecheap or INRegistry is wrong
#5I had a long email discussion with Namecheap and they said that INRegistry is the one to blame. Now INRegitry said opposite of what Namecheap said. I am seriously confused which of these two are wrong. One is wrong for sure. Update:- Looks like INRegistry and Namecheap will communicate directly.
.in has forbidden whois privacy for literally years, since its formation. India is also not exactly.. subject to GDPR