Sedo’s cunning GDPR workaround

With full Whois records set to disappear from public view for most domain names this Friday, auction house Sedo has had to resort to some technical trickery to enable its users to prove they own the domains they list for sale.
Until now, when listing a domain at Sedo, the company has checked whether the Whois record matches the data it has on file for the customer.
With that no longer possible in many cases, Sedo told users yesterday it instead wants them make updates to their DNS records, which will obviously remain public data post-GDPR.
Sedo will give each customer a personal identification number, which they will have to add to the all-purpose TXT field of their domain’s DNS record.
That’s a fairly straightforward process at most registrars, though volume domainers had better hope their registrar of choice allows DNS changes to be made in bulk.
Sedo’s calling the process “Owner Self-Verification”.
Customers who do not use the system will have to wait three business days before their names are verified. Sedo said it will manually spot-check domains and may ask for other forms of proof of ownership.
UPDATE: Many thanks to all the people on Twitter telling me this system has been in place for years. You’re all very clever. Your cookies/cigars are in the mail.

5 Comments Tagged: auctions, gdpr, privacy, sedo, whois

ICANN board talking GDPR “litigation”

ICANN’s board of directors is meeting today to discuss its “litigation strategy” concerning the General Data Protection Regulation, the EU privacy legislation due to make Whois unrecognizable come Friday.
Those two words are basically the only item on its agenda for a special board meeting today.
I’ve been unable to squeeze any further information out of ICANN, but I can speculate about a few different things it could mean.
The first thing that springs to mind is a blog post by CEO Goran Marby dated April 12, in which he wrote:

Without a moratorium on enforcement, WHOIS will become fragmented and we must take steps to mitigate this issue. As such, we are studying all available remedies, including legal action in Europe to clarify our ability to continue to properly coordinate this important global information resource. We will provide more information in the coming days.

To my knowledge, no additional information on this “legal action in Europe” has ever been released.
Could ICANN be ready to take a data protection authority to court preemptively, as a test case to insulate the industry against enforcement action from DPAs? Your guess is as good as mine at this stage.
Another possibility, still in speculative territory, is that the board will be discussing the many calls from the industry for some kind of legal or financial indemnification against GDPR-related regulatory actions. I’d assign a relatively low probability to that idea.
A third notion that springs to mind, slightly more realistically, is that the board could simply be discussing how ICANN would defend itself from incoming litigation related to its GDPR response.
It usually takes ICANN a few days to post the results of its board meetings, but on important hot topics it’s not hugely unusual to see same-day publication.

2 Comments Tagged: article 29 working party, dpas, gdpr, ICANN, privacy, whois

Failure to launch: 10 years-old gTLDs that are still dormant

Over six years after the last new gTLD application window closed, more than one in 10 new gTLDs have yet to launch, even though some have been delegated for over four years.
Once you filter out duplicates, withdrawals and terminations from the original 1,930 applications, there were a maximum of roughly 1,300 potential new gTLDs from the 2012 round.
But, by my calculations, 144 of those have yet to even get around to their sunrise period. Most of those haven’t even filed their launch plans with ICANN yet.
Here’s 10 from that list I’ve picked based on how interesting they appear to me, in no particular order.
Yes, DI is doing listicles now. Hate-mail to the usual address.
.forum
This one’s owned by Jay Westerdal’s Top Level Spectrum, the same company behind .feedback, .realty and others. I quite like the potential of this string — the internet is chock-full of forums due to the easy availability of open-source forum software — but so far nobody’s gotten to register one. It was delegated back in June 2015 and doesn’t have a published launch plan as yet. An FAQ reading just saying “Jay was here !!!!! Test deploy..delete me later…” has been up on its site since at least last September. TLS is also sitting on .contact and .pid (for “personal ID”) with no launch dates in sight.
.scholarships
Owned by Scholarships.com, there’s a whiff of the defensive about this one. It’s been in the root since March 2015 but its site states the registry “is still finishing launch plans and will provide updates as they become available”. Scholarships.com is a site that connects would-be higher education students to potential sources of funding. It’s difficult to imagine many ways the matching gTLD could possibly help in that mission.
.giving
JustGiving, the UK-based charity campaign aggregator, won this gTLD and had it delegated in August 2015, but seemingly still hasn’t figured out what it wants to do with it. It’s not a dot-brand, so it’s presumably mulling over ways to give .giving domains to fundraisers in a way that does not compromise credibility. Whatever its plans, it’s taking its sweet time over them.
.cancerresearch
This is a weird one. Delegated four years ago, the Australian Cancer Research Foundation rather quickly went live with a bunch of interlinked .cancerresearch web sites, using its contractually permitted allotment of promotional domains. Contractually, it’s not a dot-brand, but it’s basically acting like one, having never actually given ICANN any info about sunrise, eligibility, trademark claims, general availability, etc. Technically, it’s still pre-launch, and I can’t see any reason why it would want to budge from that status. Huge loophole in the ICANN rules?
.beauty
Another whiff of gaming here. International woman-shaming powerhouse L’Oreal still has no announced plans to launch .beauty, .skin or .hair, which it had originally wanted to run as so-called “closed generics” (presumably to keep the keywords out of the hands of competitors). Of its small portfolio of generic gTLDs, delegated in 2016, it has actually launched .makeup already, with a $6,000 retail price and a strategy seemingly based on registry-owned domains matching the names of makeup-focused social media influencers. At least it’s actually selling names, even if nobody’s bought one yet.
.budapest
One of three city TLDs that were delegated back in 2014 but have yet to start selling domains. MMX is to run it in partnership with the local government of the Hungarian city, if it ever gets off the ground. Madrid (.madrid) and Zurich (.zuerich) have both also yet to roll out, although Zurich has settled on early 2019 for its launch.
.fan
Regular DI readers won’t be surprised to see this one on the list. In what may turn out to be a shocking waste of money, .fans registry Asiamix Digital acquired the singular .fan from Donuts back in 2015 and promptly let it sit idle for the next three years. Currently, with .fans turning out to be a flop, Asiamix has money troubles and I wouldn’t be surprised to see it under new ownership before too long. It’s not a terrible string, so there’s some potential there.
.ком, etc
.ком is one of 11 internationalized domain name transliterations of .com — .कॉम, .ком, .点看, .คอม, .नेट, .닷컴, .大拿, .닷넷, .コム, .كوم and .קוֹם — that Verisign had delegated back in 2015. To date, only the Japanese .コム has launched, and the registry reportedly arsed it up quite badly. Records show .コム peaked at over 28,000 names and sits at fewer than 7,000 today. None of the remaining IDNs have launch dates attached.
Anything owned by Google or Amazon
When it comes to sitting on dormant gTLDs, you can’t top Google and Amazon for sheer numbers. Google has 19 strings in pre-launch states right now, while Amazon has a whopping 34. Amazon is letting the likes of .free, .wow, .now, .deal, .save and .secure sit idle, while Google is still stroking its chin on the likes of .eat, .meme, .fly and .channel. At the snail’s pace these companies roll out gTLDs, I wouldn’t be surprised if some of these strings never hit the market.
.bom
Portuguese for “.good”, .bom was delegated to local ccTLD registry Nic.br in 2015 but has no published launch dates and no content on its nic.bom registry web site. I’d say more, but I expect a certain prolific DI commenter could do a better job of it, so I’ll turn it over to him…

5 Comments Tagged: .beauty, .bom, .cancerresearch, .fan, .giving, .scholarships, .ком, amazon, budapest, forum, google, ICANN, launch, new gTLDs, sunrise

EnCirca partners with PandoraBots to push .bot names to brands

Specialist registrar EnCirca has partnered with bot development framework vendor PandoraBots to market .bot domains at big brands.
The two companies are pushing their wares jointly at this week’s International Trademark Association annual meeting in Seattle.
In a press release, the companies said that PandoraBots is offering bot-creation “starter kits” for brand owners that tie in with .bot registration via EnCirca.
Bots are rudimentary artificial intelligences that can be tailored to answer customer support questions over social media. Because who wants to pay a human to answer the phones?
Amazon Registry’s .bot gTLD is a tightly restricted space with strict preregistration verification rules.
Basically, you have to have a live, functioning bot before you can even request a domain there.
Only bots created using Amazon Lex, Botkit Studio, Dialogflow, Gupshup, Microsoft Bot Framework, and Pandorabots are currently eligible, though Amazon occasionally updates its list of approved frameworks.
The .bot space has been in a limited registration period all year, but on May 31 it will enter a six-month sunrise period.
Despite not hitting general availability until November, it already has about close to 1,800 domains in its zone — most of which were registered via EnCirca — and hundreds of live sites.
EnCirca currently offers a $200 registration service for brand owners, in which the registrar handles eligibility for $125 and the first year reg for $75.

3 Comments Tagged: .bot, ai, amazon, amazon registry, bots, encirca, inta, new gTLDs, pandorabots, sunrise, trademarks

Donuts freezes .place gTLD ahead of new geofencing rules

Donuts has taken its .place gTLD temporarily off the market as it repurposes the space as a restricted zone for “geofencing” related uses.
That’s right, the biggest gTLD portfolio play and historically staunch advocate of open gTLDs is actually planning to introduce eligibility requirements into a currently unrestricted TLD.
Details are light ahead of a formal announcement, but I’m told all new .place registrants will have to agree to use their domains for geofencing purposes.
This looks a bit like it could be a taste of the “innovation” we were all promised from the new gTLD program.
Geofencing refers to systems that divide the world up into fenced-off virtual parcels of land based on GPS coordinates, enabling location-based services.
It’s an area Donuts has been looking at for a while, having invested in early-stage geofencing company GeoFrenzy, since rebranded as Geo.Network, two years ago.
While Donuts puts its new .place model in place — ICANN and registrars have been given the heads-up — it should not be possible to register any new .place domains.
Major registrars such as GoDaddy, Namecheap, Uniregistry and Donuts-owned Name.com were not returning results for .place domains on their storefronts when I checked over the weekend.
Other registrars did still appear to be offering the names, but I did not attempt to register one to check whether the sale would complete.
I gather that the new eligibility requirements will not apply retroactively, so anyone who currently owns a .place name will get to keep it on an unrestricted basis.
There are around 7,000 active .place domains currently.

1 Comment Tagged: .place, donuts, eligibility, geofencing, geofrenzy, geonetwork, ICANN, new gtds, restricted

Registrars want six-month stay on new Whois policy

Registrars representing the majority of the gTLD industry want ICANN to withhold the ban hammer for six months on its new temporary Whois policy.
As I reported earlier today, ICANN has formally approved an unprecedented Temporary Policy that seeks to bring the Whois provisions of its contracts into compliance with the EU’s General Data Protection Regulation.
It comes into effect next Friday, May 25, but it contains a fair few items that will likely take longer for registrars to implement.
While ICANN’s top lawyer has indicated that ICANN Compliance will act as reasonably as possible about enforcing the new policy, registrars want a moratorium of at least six months.
In a letter (pdf) dated May 16 (before the policy was voted through, but while its contents were broadly known), Registrar Stakeholder Group chair Graeme Bunton wrote:

Any temporary specification adopted now that significantly deviates from previously held expectations and models will be far too late for us to accommodate for a May 25, 2018 implementation date.
For this reason, we ask that any temporary specification include a formal ICANN compliance moratorium, not shorter than six (6) months, providing us an opportunity to conform, to the extent possible, our GDPR implementation with the GDPR-compliant aspects of any ICANN temporary specification

He added that some registrars may need even more time, so they should have the right ask for an extension if necessary.
The letter is signed by Endurance, GoDaddy, Tucows, Blacknight, 1&1, United Domains, NetEarth One and Cloudflare, which together account for most gTLD domains.

1 Comment Tagged: gdpr, ICANN, prviacy, rrsg, temporary policy, whois

Lauded domainer arrested over $2.4 million “extortion”

Noted domain investor Sahar Sarid is among four men charged in California yesterday with an alleged extortion scam related to the web site Mugshots.com.
He was reportedly arrested in Florida alongside Thomas Keesee, while in California Kishore Vidya Bhavnanie and David Usdan have also been charged.
The four are alleged to be the owners of Mugshots.com, which republishes the mugshots and arrest records, copied from public documents, of people arrested in various parts of the US.
They have been charged with extortion, money laundering, and identity theft.
According to California Attorney General Xavier Becerra, the site was funded by charging the subjects of the mugshots a $399 fee to have their photos and records “unpublished”.
Many of the people affected were innocent of any crime and had been arrested by mistake, Becerra said.
The site collected over $2.4 million in removal fees from 5,307 people over three years, according to Becerra. In a statement, he said:

This pay-for-removal scheme attempts to profit off of someone else’s humiliation. Those who can’t afford to pay into this scheme to have their information removed pay the price when they look for a job, housing, or try to build relationships with others. This is exploitation, plain and simple.

According to court documents — which make a fairly horrific read — Sarid is a hidden beneficiary of Mugshots.com.
He told TheDomains back in 2012 that he’d sold Mugshots in 2011, but prosecutors now allege that the sale was fictitious and that he continued to collect money from the alleged scam.
Sarid gained fame during the domain speculation heyday of the mid-2000s, profiled in a DN Journal cover story in 2007, around the same time he was inducted into the now-defunct TRAFFIC Hall of Fame.
DN Journal publisher Ron Jackson today noted that Sarid has since been the subject of rumors of “questionable business practices”.

1 Comment Tagged: extortion, mugshots.com

Domainers not welcome in this Whois database

Inquiries from domain investors are specifically barred under one registry’s take on GDPR compliance.
The Austrian ccTLD registry, nic.at, yesterday stopped publishing the personal information of human registrants in its public Whois database, unless the registrant has opted to have their data public.
The company said it will provide thick Whois records only to “people who provide proof of identity and are able to prove a legitimate interest for finding out who the domain holder is”.
But this specifically excludes people who are trying to buy the domain in question.
“A buying interest or the wish to contact the domain holder is definitely no legitimate interest,” the company said in a statement.
It quotes its head of legal, Barbara Schlossbauer, saying: “I am also not able to investigate a car driver’s address over his license number just because I like his car and want to buy it.”
She said that those able to access records include “law enforcement agencies, lawyers or people who contact nic.at following domain disputes and who can prove that their rights have been infringed”.
While nic.at is bound by GDPR, as a ccTLD registry it is not bound by the new GDPR-compliant Whois policy announced by ICANN overnight, where who will be able to request thick Whois records is still an open question.

2 Comments Tagged: .at, cctlds, domainers, gdpr, nic.at, privacy, whois

ICANN approves messy, unfinished Whois policy

With a week left on the GDPR compliance clock, ICANN has formally approved a new Whois policy that will hit all gTLD registries and registrars next Friday.
The Temporary Specification for gTLD Registration Data represents the first time in its history ICANN has invoked contractual clauses that allow it to create binding policy in a top-down fashion, eschewing the usual community processes.
The policy, ICANN acknowledges, is not finished and needs some work. I would argue that it’s also still sufficiently vague that implementation in the wild is likely to be patchy.
What’s in public Whois?
The policy is clearest, and mostly unchanged compared to previous drafts, when it comes to describing which data may be published in public Whois and which data must be redacted.
If you do a Whois query on a gTLD domain from next week, you will no longer see the name, address, phone/fax number or email address of the registrant, admin or tech contacts.
You will continue to see the registrant’s organization, if there is one, and the country in which they are based, as well as some information about the registrar and name servers.
In future, public RDAP-based Whois databases will have to output “REDACTED FOR PRIVACY” in these fields, but for now they can just be blank.
While the GDPR is only designed to protect the privacy of humans, rather than companies, and only those connected to the European Union, the ICANN policy generally assumes that all registrants will be treated the same.
It will be possible for any registrant to opt out of having their data redacted, if being contactable is more important to them than their privacy.
What about privacy services?
Since the May 14 draft policy, ICANN has added a carve-out for domains that are already registered using commercial privacy/proxy services.
Whois records for those domains are NOT going to change under the new policy, which now has the text:

in the case of a domain name registration where a privacy/proxy service used (e.g. where data associated with a natural person is masked), Registrar MUST return in response to any query full WHOIS data, including the existing proxy/proxy pseudonymized email.

In the near term, this will presumably require registries/registrars to keep track of known privacy services. ICANN is working on a privacy/proxy accreditation program, but it’s not yet live.
So how do you contact registrants?
The policy begins to get more complicated when it addresses the ability to actually contact registrants.
In place of the registrant’s email address in public Whois, registries/registrars will now have to publish an anonymized email address or link to a web-based contact form.
Neither one of these options should be especially complex to implement — mail forwarding is a staple service at most registrars — but they will take time and effort to put in place.
ICANN indicated earlier this week that it may give contracted parties some breathing room to get this part of the policy done.
Who gets to see the private data?
The policy begins to fall apart when it describes granting access to full, unexpurgated, thick Whois records to third parties.
It seems to do a fairly good job of specifying that known quantities such as URS/UDRP providers, escrow providers, law enforcement, and ICANN itself continue to get access.
But it’s fuzzier when it comes to entities that really would like to continue to access Whois data, such as trademark lawyers, security service providers and consumer protection concerns.
While ICANN is adamant that third parties with “legitimate interests” should get access, the new policy does not enumerate with any specificity who these third parties are and the mechanism(s) contracted parties must use to grant such access.
This is what the policy says:

Registrar and Registry Operator MUST provide reasonable access to Personal Data in Registration Data to third parties on the basis of a legitimate interests pursued by the third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the Registered Name Holder or data subject

This appears to give contracted parties the responsibility to make legal judgment calls — balancing the GDPR-based privacy rights of the registrant against the “legitimate interests” of the requester — every time they get a thick Whois request.
The policy goes on to say that when European privacy regulators, the courts, or other legislation or regulation has specifically approved a certain class of requester, ICANN will relay this news to the industry and it will have 90 days to make sure that class gets full Whois access.
But the policy does not specify any formal mechanism by which anyone goes about requesting a thick record.
Do they just phone up the registrar and ask? Does the registrar have to publish a contact address for this purpose? How does the registrar go about confirming the requester is who they say they are? Should they keep white-lists of approved requesters, or approve each request on a domain-by-domain basis? When does the right of a trademark owner outweigh the privacy right of an individual?
None of these questions are answered by the policy, but in a non-binding annex ICANN points to ongoing community work to create an “accreditation and access model”.
That work appears to be progressing at a fair rapid clip, but I suspect that’s largely because the trademarks lawyers are holding the pens and discussions are not following ICANN’s usual consensus-building policy development rules.
When the work is absorbed into the ICANN process, we could be looking at a year or more before something gets finalized.
How will transfers work?
Because Whois is used during the inter-registrar transfer process, ICANN has also had to tweak its Inter-Registrar Transfer Policy to take account of instances where registrars can’t access each other’s databases.
Basically, it’s scrapping the requirement for gaining registrars to obtain a Form of Authorization from the Whois-listed registrant before they start an inbound transfer.
This will remove one hoop registrants have to jump through when they switch registrars (though losing registrars still have to obtain an FOA from them) at the cost of making it marginally easier for domain theft to occur.
What happens next?
ICANN acknowledges, in seven bullet points appended to the policy, that the community has more work to do, mainly on the access/accreditation program.
Its board resolution “acknowledges that there are other implementation items that require further community conversation and that the Board encourages the community to resolve as quickly as possible”.
The board has also asked ICANN staff to produce more explanatory materials covering the policy.
It also temporarily called off its Governmental Advisory Committee consultation, which I wrote about here, after receiving a letter from the GAC.
But the big next step is turning this Temporary Policy into an actual Consensus Policy.
The Temporary Policy mechanism, which has never been used before, is set up such that it has to be renewed by the board every 90 days, up to a maximum of one year.
This gives the GNSO until May 25 next year to complete a formal Policy Development Process. In fact, it will be a so-called “Expedited” PDP or EPDP, that cuts out some of the usual community outreach in order to provide a speedier result.
This, too, will be an unprecedented test of an ICANN policy-making mechanism.
The GNSO will have the Temporary Policy baseline to work from, but the Temporary Policy is also subject to board-level changes so the goalposts may move while the game is being played.
It’s going to be a big old challenge, and no mistake.

4 Comments Tagged: .eu, article 29 working party, gdpr, gtlds, ICANN, privacy, rdap, whois, wp29

Three reasons ICANN could swing the GDPR ban hammer on day one

While ICANN reckons it will act “reasonably” when it comes to enforcing compliance with its incoming GDPR emergency policy, there are some things it simply will not tolerate.
The policy expected to be approved tomorrow and immediately incorporated by reference into registry and registrar contracts, is a little light on expected implementation timetables, so this week ICANN has been pressured for clarity.
Will Compliance start firing off breach notices on May 26, the day after GDPR comes into effect, if the industry has not immediately implemented every aspect of the new policy?
Attendees at the Global Domains Division Summit in Vancouver managed to get some answers out of general counsel John Jeffrey at a session yesterday.
First off, if you’re a registrar planning to stop collecting registrants’ personal information for Whois, ICANN will not be happy, and you could be looking at a Compliance ticket.
Jeffrey said:

We don’t want any of the contracted parties to stop collecting the data. ICANN is confident that you can continue to collect the data. We will stand in front of you on it, if we can. Do not stop collecting the data. We believe we have a very strong, important point. We hear from the governments that were involved in passing this legislation that it’s important it continues to be collected.

Second, you have to have a mechanism in place for people with “legitimate purposes” to access thick Whois records that contain all the juicy personal information.
Jeffrey said:

We also believe it’s important there’s a need to continue to display information that will be behind that second tier. And we can demonstrate the need to do that as well. This is really important.

And if there was any doubt remaining, he added:

We will enforce on the temporary spec, if it’s approved, if you stop collecting data, or if you don’t provide any mechanism to allow access to it. It’s a very serious concern.

The problem right now is that the Temporary Policy (pdf), still in draft, doesn’t have a whole heck of lot of detail about who should be allowed such access and the mechanisms to enable it.
It says:

Personal Data included in Registration Data may be Processed on the basis of a legitimate interest not overridden by the fundamental rights and freedoms of individuals whose Personal Data is included in Registration Data

It goes on to list circumstances where access may be given and types of parties that may need access, but it seems to me to still give registries and registrars quite a lot of responsibility to decide how to balance privacy rights and the “legitimate” data requests.
Those two scenarios — not collecting data and not making it available to those who need it — seem to be the big two zero tolerance areas for ICANN.
Other issues, such as replacing the registrant’s email address in the thin Whois output, also appear to be a pressing concern.
Jeffrey said, noting that providing a way to contact registrants is important for myriad reasons, including UDRP:

Creating the anonymized emails or web forms is another really important aspect but we understand some won’t be able to have that in place immediately.

How long after GDPR Day ICANN starts swinging the ban hammer over the email issue seems to be something ICANN is still thinking about.
That said, Jeffrey said that the organization intends to act “as reasonably as possible”.

1 Comment Tagged: compliance, gdpr, ICANN, privacy, whois