Amazon planning new push into registrar market?

Amazon has kept a pretty low profile to date both as a registry and registrar, but there are reasons to believe it’s on the verge of becoming a more visible player in the market.

The e-commerce and web services giant has secured a second ICANN registrar accreditation and appears to be readying a new domain-focused web site.

The subsidiary Amazon Domain Registrar US LLC picked up its accreditation this week, and its official web site domain is domains.amazon, which was registered November 29.

The domain does not currently resolve from where I’m sitting.

Amazon already uses the dot-brand domain registry.amazon for its 50-odd new gTLDs, almost all of which remain unlaunched.

In the registrar market, Amazon’s subsidiary Amazon Registrar Inc has been accredited for well over a decade and has been taking registrations since 2015 as part of its Route 53 managed DNS service.

It’s not a conventional registrar storefront by any stretch — registrations seem to be available only via the management console used by existing Route 53 customers — but it has amassed over 1.3 million gTLD registrations so far.

So could domains.amazon become the newest player in the retail registrar market? Smaller registrars that cheered the exit of the Google brand from the registrar space may soon have a new big boy to contend with.

Registries and registrars vote ‘Yes’ to new DNS abuse rules

ICANN’s contracted registries and registrars have voted to accept new rules requiring them to take action on DNS abuse.

The new rules come after a vote lasting a few months with some quite high thresholds for success.

The current Registrar Accreditation Agreement merely requires registrars to “take reasonable and prompt steps to investigate and respond appropriately to any reports of abuse”, which is pretty vague and barely enforceable.

The amendments, which still need to be rubber-stamped by the ICANN board, make it much clearer what registrars are expected to do in which circumstances. A new paragraph is added that reads:

3.18.2 When Registrar has actionable evidence that a Registered Name sponsored by Registrar is being used for DNS Abuse, Registrar must promptly take the appropriate mitigation action(s) that are reasonably necessary to stop, or otherwise disrupt, the Registered Name from being used for DNS Abuse. Action(s) may vary depending on the circumstances, taking into account the cause and severity of the harm from the DNS Abuse and the possibility of associated collateral damage.

For registries, the new text for the base gTLD Registry Agreement is similar, but with a little more wiggle-room:

Where a Registry Operator reasonably determines, based on actionable evidence, that a registered domain name in the TLD is being used for DNS Abuse, Registry Operator must promptly take the appropriate mitigation action(s) that are reasonably necessary to contribute to stopping, or otherwise disrupting, the domain name from being used for DNS Abuse. Such action(s) shall, at a minimum, include: (i)the referral of the domains being used for the DNS Abuse, along with relevant evidence, to the sponsoring registrar; or (ii) the taking of direct action, by the Registry Operator, where the Registry Operator deems appropriate. Action(s) may vary depending on the circumstances of each case, taking into account the severity of the harm from the DNS Abuse and the possibility of associated collateral damage.

In both cases, DNS abuse is defined by the now industry standard line: “malware, botnets, phishing, pharming, and spam (when spam serves as a delivery mechanism for the other forms of DNS Abuse listed in this Section)”.

There are a few other quality of life updates, such as the requirement for registrars to acknowledge receipt of abuse reports and to have their abuse reporting mechanism “conspicuously and readily accessible from” their home pages.

ICANN needed registrars representing over 90% of registered gTLD domains (adjusted slightly to make GoDaddy’s voice less powerful). That threshold was passed last week, with 94% of domains voting in favor of the amendments.

For registries, ICANN required a simple majority of registries (counted by contract rather than company) and for all registries voting in favor to have been responsible for two thirds of all registry fees paid last year.

Judging by the financial thresholds, .com and .net, which are not on the base RA, were not involved.

Fast-growing Gname buys another 150 registrars

Gname, the fast-growing Singaporean registrar, has added 150 ICANN registrar accreditations to its drop-catching army.

The companies are named Gname 151 through Gname 300. The companies Gname 2 through Gname 150 were accredited in June 2021.

Gname’s primary accreditation has grown massively since it became a drop-catcher in the last two years, going from under 10,000 names under management at the start of 2021 to 3.9 million at the end of August this year. About 3.2 million of its names were in .com.

Its first 150 secondary accreditations had almost a million names between them.

In August, it was the fastest-growing registrar of gTLD names, growing by over 156,000 domains and becoming the 12th-largest registrar accreditation overall.

Drop-catchers use large numbers of accreditations because registries rate-limit their connections. More accreditations means more connections and a better chance to register a valuable domain when it drops.

The primary accreditation was originally Chinese, in the name of Beijing Huaqi Weiye Technology Co and doing business at iwanshang.cn, before it moved to a Singaporean company called Gname.com.

ICANN’s current budget predicts an increase of five accrediations in fiscal 2024, which ends next June. Its high estimate was an increase of 60. So it’s now getting about half a million bucks more than it was expecting.

ICANN’s private Whois data request service goes live

ICANN has this evening gone live with its service that enables anyone to request private Whois data on any gTLD domain.

The Registration Data Request Service lets people request contact information on registrants that would otherwise be redacted in the public Whois due to laws such as the GDPR.

The press release announcing the launch seems to have come out an hour or two before the service actually became accessible, but it’s definitely live now and I’ve tried it out.

The system is defined largely by what it isn’t. It isn’t an automated way to get access to private data. It isn’t guaranteed to result in private data being released. It isn’t an easy workaround to post-GDPR privacy restrictions.

It is a way to request an unredacted Whois record knowing only the domain and not having to faff around figuring out who the registrar is and what their mechanisms and policies are for requesting the data.

After scaling back the extremely complex and expensive original community recommendations for a post-GDPR Whois service, ICANN based the RDRS on its now decade-old Centralized Zone Data Service, which acts as an intermediary between registries and people like myself who enjoy sniffing around in zone files.

The RDRS merely connects Whois data requestors — the default settings in the interface suggest that ICANN thinks they’ll mostly be people with court orders — with the registrars in charge of the domains they are interested in.

Anyone who has used CZDS will recognize the interface, but the requesting process is longer, more complex, and requires accepting more disclaimers and Ts&Cs. That said, it’s not particularly confusing.

At first glance, it looks fine. Slick, even. I’ve used it to submit a test request with GoDaddy for my own Whois data, specifying that whoever deals with the request is free to ignore it. Let’s see what happens.

A registrar is getting blamed for an Israeli war propaganda site

Israel-based registrar Wix is being blamed for a gory anti-Hamas web site being promoted by Israeli government officials.

A number of recent media reports — notably including this one by usually reliable news wire UPI — have said that Wix is behind the incredibly NSFW web site at hamas.com.

The site is a dark parody of a Hamas fund-raising page, containing disturbing footage of the group’s October 7 atrocities — dead bodies, terrorists taking hostages, shooting dogs and burning homes.

So I imagine Wix would be disturbed to learn it is being credited as the creator of the site, apparently purely because the domain was registered via its registrar and hosted on its hosting service.

“The Israeli software company Wix has created a website to spread anti-Hamas propaganda amid the war in Gaza,” UPI reported, sourcing a GoDaddy Whois lookup that lists Wix as the registrar but shows no registrant information.

A Whois lookup on Wix itself, which should contain information beyond the registry record supplied by GoDaddy, does not reveal any additional information — not even redacted fields — about the registrant.

Hamas usually uses hamas.ps for its web site, but it’s currently down reportedly due to cyber-attacks by pro-Israel hacktivists.

hamas.com has been parked for years by what UPI uncharitably refers to as “cybersquatters”.

ICANN cans Freenom

Controversial free-domains company Freenom has lost its ICANN accreditation, signalling the end of its life as a gTLD registrar.

Org said that as of November 25, Freenom (aka OpenTLD) will no longer be able to sell or renew any domains.

The termination follows the company’s failure to resolve or respond to three separate breach notices, covering dozens of infractions, that Compliance sent between September and October.

Real damage to registrants was caused — many could not rescue their expired domains or transfer names to another registrar.

The company has 16,521 gTLD domains under management at the end of July, according to the most-recent registry transaction reports. They will now be moved to a more-reliable registrar under ICANN’s De-Accredited Registrar Transition Procedure.

Freenom may have been a small fish in the gTLD space, but it gave away tens of millions of free domains in five ccTLDs it controlled, mostly to spammers and other ne’er-do-wells.

It was recently reported that it has lost or is losing its deals with these ccTLDs, notably .tk, after their governments became aghast at how badly they were being abused.

GoDaddy domains revenue crosses half a billion

GoDaddy sold more than half a billion dollars of domain names in the third quarter even as volumes slightly decreased, according to its latest earnings release.

The company had domains revenue of $508.2 million in Q3, compared to $494 million a year ago and $492.7 in the second quarter, according to regulatory filings. The aftermarket revenue component was down 2% at $107 million.

It had 84 million domains under management at the end of the quarter, compared to 84.2 million at the end of June. About three quarters of GoDaddy’s DUM are in gTLDs and about 60% are in .com, according to registry reports.

Overall, GoDaddy’s revenue was up 3.5% compared to a year ago at $1.07 billion. Net income was $131 million compared to $100 million a year ago.

Freenom spanked for holding Olympics domain hostage

Freenom has been hit by its third ICANN contract-breach notice in under a month, this time because the organizers of the 2024 Paris Olympics could not transfer a domain out to another registrar.

The registrar, formally OpenTLD, failed to take off the ClientTransferProhibited status from the domain club2024.tickets, preventing the registrant from transferring it, ICANN claims.

Digging through my database and Whois records, it looks like the organizing committee of Paris 2024 used Freenom to defensively register 10 .tickets domain names related to its Le Club Paris 2024 marketing initiative in July 2020.

They were the only .tickets domains Freenon has ever sold.

When they came up for renewal last year, the Paris committee instead transferred nine of them out to local registrar Gandi, where they remain. The 10th domain was not transferred for some reason.

ICANN says Freenom is in violation of the Transfer Policy by failing to unlock the domain without a good reason. Additionally, the domain doesn’t show up in Whois queries on Freenom’s web site, despite still being in the zone file.

Compliance has given the registrar until November 7 to come back into compliance or risk losing its accreditation.

Freenom is already working under two active breach notices, which ICANN said it has not yet responded to. The deadline on the earlier, September 20 notice has already passed, so ICANN could escalate any day.

Freenom gets yet another ICANN breach notice

ICANN Compliance is really up in Freenom’s face now, filing yet another contract-breach notice against its registrar arm barely a week after the last one.

The September 29 notice adds three new tickets to the 12 in the September 20 notice I wrote about last month. It’s the sixth notice OpenTLD has received since 2015.

The cases are similar to those in the previous missive. ICANN wants proof that the registrar has been complying with the Transfer Policy and the Expired Registration Recovery Policy.

It seems some Freenom customers have had difficulty transferring their names out of the company’s control, and have been unable to restore their domains after accidentally allowing them to expire.

It still also owes ICANN past-due fees, the notice reiterates.

The notice covers complaints from June and July. The company has until October 20 to comply or risk losing its accreditation. The claims in the earlier notice give it until October 11.

Freenom is the company that runs a dwindling collection of free-to-register ccTLDs, notably .tk. It has not allowed registrations on its site all year, blaming technical issues. It’s also being sued by Facebook owner Meta over alleged cybersquatting.

Epik drops another 50,000 domains after scandal

Epik lost almost 50,000 domains under management in June, dropping below half a million domains for the first time since 2019, according to just-published registry transaction reports.

The registrar ended the month with 461,822 DUM, down from 511,028 in May and an August 2022 peak of 808,160.

The transfer exodus continued in the month, which was the first month Epik was operating under new management, having paid off most of its debts following its financial scandal.

The company saw a net transfer figure of -24,789 domains, with only 667 inbound transfers.

Newly registered domains recovered slightly, moving back into four figures after a couple of months, ending June at 3,391, still a long way off pre-scandal levels.