There were slightly fewer complaints about domain name registrars in 2016, compared to 2015, according to newly published ICANN data, but complaints still run into the tens of thousands.
There were 43,156 complaints about registrars to ICANN Compliance in 2016, compared to 45,926 in 2015, according to the data (pdf). That’s a dip of about 6%.
The overall volume of complaints, and the dip, can be attributed to Whois.
About three quarters of the complaints directed at registrars in 2016 were for Whois inaccuracy — 32,292 complaints in total, down from 34,740 in 2015.
The number of complaints about gTLD registries was pretty much flat at 2,230, despite hundreds of new gTLDs being delegated during the year.
The vast majority of those gTLDs were dot-brands, however, with nowhere near the same kind of potential for abuse as generally available gTLDs.
The biggest cause for complaint against registries, representing about half the total, was the Zone File Access program. I’ve filed a few of these myself, against dot-brands that decide the ZFA policy doesn’t apply to them.
Formal, published breach notices were also down on the year, with 25 breaches, four suspensions and four terminations, compared to 32 breaches, six suspensions and eight terminations in 2015.
That’s the second consecutive year the number of breach notices was down.
The domain name industry is kicking off one of its most fundamental shifts in its plumbing this week.
Over the next two years, Verisign and every registrar that sells .com domains will have to rejigger their systems to convert .com from a “thin” to “thick” Whois.
This means that by February 1, 2019, Verisign will for the first time control the master database of all Whois records for .com domains, rather than it being spread piecemeal across all registrars.
The switch comes as a result of a years-in-the-making ICANN policy that officially came into force yesterday. It also applies to .com stablemates .net and .jobs.
The first big change will come August 1 this year, the deadline by which Verisign has to give all of its registrars the ability to submit thick Whois records both live (for new regs) and in bulk (for existing ones).
May 1, 2018 is the deadline for all registrars to start submitting thick Whois for new regs to Verisign, but they can start doing so as early as August this year if they want to.
Registrars have until February 1, 2019 to supply Verisign with thick Whois for all their existing registrations.
There’s a process for registrars who believe they would be violating local privacy laws by transferring this data to US-based Verisign to request an exemption, which may prevent the transition going perfectly uniformly.
Some say that the implementation of this policy may allow Verisign to ask for the ability to ask a for an increase in .com registry fees — currently frozen at the command of the US government — due to its inevitably increased costs.
Personally, I think the added costs will likely be chickenfeed compared to the cash-printing machine that is .com, so I think it’s far from a slam-dunk that such fee increases would be approved.
Domain name registrars have been assured that ICANN Compliance will not pursue them for failing to implement the new Transfer Policy on privacy-protected names.
As we reported late November, the new policy requires registrars to send out “change of registrant” confirmation emails whenever certain fields in the Whois are changed, regardless of whether the registrant has actually changed.
The GNSO Council pointed out to ICANN a number of unforeseen flaws in the policy, saying that vulnerable registrants privacy could be at risk in certain edge cases.
They also pointed out that the confirmation emails could be triggered, with not action by the registrant, when privacy services automatically cycle proxy email addresses in the Whois.
This appears to have already happened with at least one registrar that wasn’t paying attention.
But ICANN chair Steve Crocker told the GNSO Council chair last week that ICANN staff have been instructed to ignore violations of the new policy, which came into effect December 1, in cases involving privacy-protected domains (pdf).
It’s a temporary measure until the ICANN board decides whether or not to defer the issue to the GNSO working group currently looking at policies specifically for privacy and proxy services.
Ninety-seven percent of Whois records contain working email addresses and/or phone numbers, according to the results of an ongoing ICANN survey.
The organization yesterday published the second of its now-biannual WHOIS Accuracy Reporting System reports, a weighty document stuffed with facts and figures about the reliability of Whois records.
It found, not for the first time, that the vast majority of Whois records are not overtly fake.
Email addresses and phone numbers found there almost always work, the survey found, and postal addresses for the most part appear to be real postal addresses.
The survey used a sample of 12,000 domains over 664 gTLDs. It tested for two types of accuracy: “syntactical” and “operability”.
Syntactical testing just checks, for example, whether the email address has an @ symbol in it and whether phone numbers have the correct number of digits.
Operability testing goes further, actually phoning and emailing the Whois contacts to see if the calls connect and emails don’t bounce back.
For postal addresses, the survey uses third-party software to see whether the address actually exists. No letters are sent.
The latest survey found that 97% of Whois records contain at least one working phone number or email address, “which implies that nearly all records contain information that can be used to establish immediate contact.”
If you’re being more strict about how accurate you want your records, the number plummets dramatically.
Only 65% of records had operable phone, email and postal contact info in each of the registrant, administrative and technical contact fields.
Regionally, fully accurate Whois was up to 77% in North America but as low as 49.5% in Africa.
So it’s not great news if Whois accuracy is your bugbear.
Also, the survey does not purport to verify that the owners of the contact information are in fact the true registrants, only that the information is not missing, fake or terminally out-of-date.
A Whois record containing somebody else’s address and phone number and a throwaway webmail address would be considered “accurate” for the survey’s purposes.
The 54-page survey can be found over here.
Verisign could be running a “thick” Whois database for .com, .net and .jobs by mid-2017, under a new ICANN proposal.
A timetable published this week would see the final three hold-out gTLDs fully move over to the standard thick Whois model by February 2019, with the system live by next August.
Some people believe that Verisign might use the move as an excuse to increase .com prices.
Thick Whois is where the registry stores the full Whois record, containing all registrant contact data, for every domain in their TLD.
The three Verisign TLDs currently have “thin” Whois databases, which only store information about domain creation dates, the sponsoring registrar and name servers.
The model dates back to when the registry and registrar businesses of Verisign’s predecessor, Network Solutions, were broken up at the end of the last century.
But it’s been ICANN consensus policy for about three years for Verisign to eventually switch to a thick model.
Finally, ICANN has published for public comment its anticipated schedule (pdf) for this to happen.
Under the proposal, Verisign would have to start offering registrars the ability to put domains in its thick Whois by August 1 2017, both live via EPP and in bulk.
It would not become obligatory for registrars to submit thick Whois for all newly registered domains until May 1, 2018.
They’d have until February 1, 2019 to bulk-migrate all existing Whois records over to the new system.
Thick Whois in .com has been controversial for a number of reasons.
Some registrars have expressed dissatisfaction with the idea of migrating part of their customer relationship to Verisign. Others have had concerns that local data protection laws may prevent them moving data in bulk overseas.
The new proposal includes a carve-out that would let registrars request an exemption from the requirements if they can show it would conflict with local laws, which holds the potential to make a mockery out of the entire endeavor.
Some observers also believe that Verisign may use the expense of building and operating the new Whois system as an excuse to trigger talks with ICANN about increasing the price of .com from its current, frozen level.
Under its .com contract, Verisign can ICANN ask for a fee increase “due to the imposition of any new Consensus Policy”, which is exactly what the move to thick Whois is.
Whether it would choose to exercise this right is another question — .com is a staggeringly profitable cash-printing machine and this Whois is not likely to be that expensive, relatively speaking.
The proposed implementation timetable is open for public comment until December 15.