As Deadly as a DDoS: ICANN Unleashes the Whois Accuracy Program
blog.easydns.org
As Deadly as a DDoS: ICANN Unleashes the Whois Accuracy Program
1–10 of 71 posts
Re: As Deadly as a DDoS: ICANN Unleashes the Whois Accuracy Program
#2Re: As Deadly as a DDoS: ICANN Unleashes the Whois Accuracy Program
#3Can this be done via a "click here to confirm" email, or does this require phone conversations with the registrar? I don't like registering domains using my real name.
Re: As Deadly as a DDoS: ICANN Unleashes the Whois Accuracy Program
#4Can this be done via a "click here to confirm" email, or does this require phone conversations with the registrar? I don't like registering domains using my real name.
And unlike the intended trigger for verification ("changes to contact information"), I didn't make any changes to my domain. Either a WHOIS cloak expired, or some other action by Namecheap triggered the verification step.
Re: As Deadly as a DDoS: ICANN Unleashes the Whois Accuracy Program
#5Re: As Deadly as a DDoS: ICANN Unleashes the Whois Accuracy Program
#6If you change registrar-level things about your domain, they're now required to confirm your contact info with you. This isn't a "DDoS", or "deadly", or any of that nonsense: it's a new strategy to ensure whois data stays updated.
Whether or not it's an effective strategy for keeping whois data accurate is another debate (I don't think it is), but talking about it like some malicious act is pointless.
Re: As Deadly as a DDoS: ICANN Unleashes the Whois Accuracy Program
#7Can this be done via a "click here to confirm" email, or does this require phone conversations with the registrar? I don't like registering domains using my real name.
Re: As Deadly as a DDoS: ICANN Unleashes the Whois Accuracy Program
#8Can this be done via a "click here to confirm" email, or does this require phone conversations with the registrar? I don't like registering domains using my real name.
I got such an email from Namecheap yesterday, and confirmed it with one click. And unlike the intended trigger for verification ("changes to contact information"), I didn't make any changes to my domain. Either a WHOIS cloak expired, or some other action by Namecheap triggered the verification step.
Re: As Deadly as a DDoS: ICANN Unleashes the Whois Accuracy Program
#9Re: As Deadly as a DDoS: ICANN Unleashes the Whois Accuracy Program
#10The title is pretty much linkbait. If you change registrar-level things about your domain, they're now required to confirm your contact info with you. This isn't a "DDoS", or "deadly", or any of that nonsense: it's a new strategy to ensure whois data stays updated. Whether or not it's an effective strategy for keeping whois data accurate is another debate (I don't think it is), but talking about it like some maliciou…
I read about this originally when they made the rule and it seemed arcane and ridiculous, I dont know how it ever was passed. I believe everyone who some experience with whois info knows the information is either false or hidden behind privacy emails and contact information. If they are not, they are subject to annoying or even abusive misuse. (I remember someone back in the day calling me repeatedly because they found my website after I beat them in some video game, the internet is filled with nutters.)
If ICANN wants to know the details, I dont care, but if all the internet wants my phone number, they can take a long walk off of a short pier.