DNS issue at Amazon takes out major apps and sites

Amazon’s AWS cloud platform has been suffering major outages for the last few hours, taking huge chunks of the internet with it, and DNS resolution is being blamed.

Affected products and services reportedly include Snapchat, Roblox, Fortnite, Delta Air Lines, Duolingo, Signal, Reddit, Amazon’s own Ring doorbell cam service, as well as the UK tax authority and various UK banks.

Amazon first reported problems on its status page at 0711 UTC this morning. By 0901 UTC, the company had narrowed the problem down, saying it “appears to be related to DNS resolution of the DynamoDB API endpoint in US-EAST-1.”

DynamoDB is a cloud-based database service Amazon offers on AWS. US-EAST-1 is an Amazon regional data center cluster.

Twenty minutes later, Amazon began to report “early signs of recovery for some impacted AWS Services”. Not long after, it said the recovery signs were “significant”.

At 1035 UTC Amazon said: “The underlying DNS issue has been fully mitigated, and most AWS Service operations are succeeding normally now. Some requests may be throttled while we work toward full resolution.”

AWS underpins hundreds of top-level domains — notably, Identity Digital built its registry platform there — but there’s no word yet on any DNS or EPP issues from any registries.

Amazon delays book and fashion gTLDs

Two gTLD launches pencilled in for next month seem to have been delayed a year.

Amazon Registry has filed updated launch dates for two Japanese-language TLDs: .書籍 (.xn--rovu88b), meaning “book”, and .ファッション (.xn--bck1b9a5dre4c), meaning “fashion”.

Both had been previously scheduled to go to general availability in early November, but new dates published by ICANN have pushed both back to the same dates in 2026.

Both have already completed their mandatory sunrise periods, back in late 2016. If they do go GA next year, it will have been a full decade between trademark protection and free-for-all.

Amazon has been slowly releasing its long-dormant stockpile of gTLDs recently. Three — .you, .talk and .fast — went GA earlier this month. Three others — .free, .hot and .spot — launched in the first half of the year.

love.you sold in apparent five-figure deal

The domain name love.you has been sold by Amazon Registry for what was probably more than $30,000, during what so far has been a bit of a disappointing launch for the .you gTLD.

love.you is the only domain currently showing up in .you’s zone file that has a creation date after 1300 UTC on September 25, the moment Amazon opened its latest Early Access Periods.

It was registered about half an hour after the EAP opened last Thursday.

The first-day EAP application fee was $10,000. If love.you was listed as a top-tier premium domain, which seems likely, that would have added an extra $20,000 to the sale price, and that’s before registrar 101domain applied its retail markup.

It’s the only EAP registration in .you so far, judging by the zone. Amazon is currently also running EAPs for .talk and .fast, but zone files suggest it hasn’t made any sales in those gTLDs yet.

The three TLDs are having unusually long EAPs — 11 days versus the usual five — with wholesale prices ranging from $10,000 on day one to $100 on day 11, before premium fees are applied.

Full general availability at standard pricing will begin October 6, with prices likely to be about $20 to $30 a year.

So who’s registering sunrise domains these days?

Amazon went into sunrise with three gTLDs this week, and I thought it might be interesting to pore over the latest zone files to see which companies are the most motivated to protect their brands nowadays.

First, because sometimes the results are just weird. Second, because countless new gTLD consultants are trawling the business world for prospects right now, and sunrise participation data might be useful as lead generation.

Amazon launched .you, .talk and .fast on Tuesday, so these results are for the first two days of sunrise, a period that lasts for a month. As such, there are only a few dozen registered domains in each TLD, at most.

Let’s start with the weird: dog food companies seem to fear cybersquatting more than you might imagine. Mars brands Orijen, Champion Pet Foods and Acana are all protected (though no more of Mars’ dozens of consumer brands), as is independent retailer PetSmart.

An AI company have a presence on the list, which is a relatively new phenomenon for sunrise periods. Anthropic has registered both “anthropic” and “claude”, for its chatbot, in all three TLDs.

Financial companies have a strong presence on the lists, with Freddie Mac, Bank of America, Intesa Sanpaolo, Merrill and Astorg all registering names. Energy brands Iberdrola and Avangrid are registered.

Conscious Capital, a Swiss investment company that doesn’t even have a Wikipedia page, has defended its brand. That’s notable because the company uses a .us domain for its web site and the .com is listed for sale by a domainer for $2 million.

1-800-Flowers.com, which has somehow managed to get a Trademark Clearinghouse listing for “flowers” — the product it sells — participated in the sunrises as usual. The gTLD .flowers belongs to XYZ.com.

Hotel chain Hilton, podcasters Wondery, construction company VINCI Concessions (vinci-concessions.you???) and tech firms Broadcom and AT&T have all also got in quick to grab their matching domains.

The sunrise periods run until September 25, with general availability following hot on their heels.

GoDaddy loses last Amazon business to Identity Digital

GoDaddy appears to have lost the last remnants of its Amazon back-end registry services deal.

IANA records show that GoDaddy was recently replaced by Identity Digital as the technical contact for all of the remaining 12 gTLDs it was serving.

The gTLDs in question are: .coupon, .song, .zero and the IDNs .ストア, .セール, .家電, .クラウド, .食品, .ファッション, .書籍, .ポイント and .通販, which are generic terms for things like “fashion” and “books”.

Five of the IDNs have actually launched and have been generally available for years, but they’re been phenomenally unsuccessful — the largest zone has just 146 domains in it. The remaining seven are dormant, unlaunched.

Amazon originally used GoDaddy (then Neustar) for all 54 of the gTLDs it successfully applied for back in the 2012 gTLD application round, but it switched all but 12 of them to Nominet back in 2019, where they remain today.

Third Amazon gTLD launch dates revealed

Amazon is set to launch not two but at least three of its dormant new gTLDs in the next few months, according to ICANN documentation.

As reported earlier this week, .talk and .fast are set to go to sunrise in August and general availability in September, and now they’ll be joined by a third: .you.

.you will enter a one-month sunrise period for trademark owners August 25, to be immediately followed by GA. There’ll likely also be a five-day Early Access Period.

The releases follow the launch of .free, .hot and .spot last month.

Launch dates for two more Amazon gTLDs revealed

Fresh from the launch of .free, .hot and .spot, Amazon has pencilled in launch dates for two more of its backlog of dormant gTLDs.

The company has told ICANN it plans to launch .talk and .fast later this year, with sunrise coming in August.

It also seems to be planning to start using .audible, one of its dot-brands, but that would not be available for public registration.

.fast and .talk are set to enter their sunrise periods from August 26 to September 25 this year, according to ICANN documentation. General availability would follow immediately.

If Amazon follows the same playbook as it did with the three gTLDs it launched last month, there would also be a five-day Early Access Period, with premium prices for early adopters.

The May launches have yet to set the world alight, perhaps in part due to their pricing (ranging from $30 to $60 retail), with best-performer .free’s zone file containing just 1,150 domains so far.

Some people paid premiums for .hot domain hacks

Amazon Registry’s launch of three gTLDs last week saw some registrants pay premium prices for .hot domain hacks.

Zone file data shows domains such as moons.hot and slings.hot were registered towards to the end of the five-day Early Access Period, with the registrant likely paying close to a thousand bucks for each.

cums.hot, longs.hot, moneys.hot, mugs.hot, pots.hot and ups.hot have all been registered, seeming by a broad range of registrants, at regular general availability prices since EAP closed May 17.

The EAP was lightly subscribed, if the zones are a guide. There were a handful of defensive registrations towards the end of the week, along with a few context-appropriate keywords like piping.hot.

.hot launched at the same time as .free and .spot, which don’t seem to have the same domain hack opportunities. Most EAP regs there were either defensives or keywords. Names like speak.free and live.free were registered.

As of today, .free is doing the best of the three, with 931 names in its zone, followed by .spot with 373 and .hot with 309.

.hot is for hookers? Amazon’s first premium regs revealed

Amazon Registry made three new gTLDs available to non-trademark-holders on Monday, and so far a handful registrants have taken up the offer of premium Early Access Period pricing.

The five-day EAPs for .free, .hot and .spot see prices start high and decrease each day until May 17, when they’ll settle at standard general availability pricing.

While the wholesale prices have not been published by Amazon, the registrar 101domain was retailing them for $6,299 on day one, $3,299 on day two, $1,399 on day three, $799 on day four, and $199 on day five.

GA pricing for .hot at 101domain will be $59.99, while .free will be $44.99 and .spot will be $29.99.

The early adopter(s) in .hot seem to be viewing it as a sex-related TLD along the lines of .xxx, .sex or .sexy. All the day-one registrations (in multiple languages) look set to be used for escort services.

The domains that popped up for the first time in the May 13 zone files were:

be.free
bible.free
sql.free

acompanhantes.hot
escort.hot
escorts.hot
incontri.hot
prepagos.hot
trans.hot

high.spot
hub.spot

The only new domain in the May 14 zones appears to be live.free. They’re not exactly flying off the shelves so far.

Because the zone files are generated at midnight UTC and Amazon’s EAP daily price-increase cut-off is 1259 UTC, it’s not possible to say for sure how much each registrant paid for their domain names.

Registries have started shutting down Whois

Nominet seems to have become the first major registry services provider to start to retire Whois across its portfolio, already cutting off service for about 70 top-level domains.

Queries over port 43 to most of Nominet’s former Whois servers are no longer returning responses, and their URLs have been removed from the respective TLDs’ records on the IANA web site.

The move follows the expiration last month of ICANN’s contractual requirements to provide Whois in all gTLDs. Now, registries must use the successor protocol RDAP instead, with Whois optional.

A Nominet spokesperson tells us the shut-off, which affects large dot-brand clients including Amazon, happened after consultation with ICANN and clients on January 29.

TLDs Nominet was supporting under ICANN’s Emergency Back-End Registry Operator program are also affected.

The registry spokesperson said that the gTLDs .broadway, .cymru, .gop, .pharmacy, and .wales are still offering Whois, due to an interoperability issue:

“The sole reason for the retention of these gTLD WHOIS services is for interoperability with the Brand Safety Alliance (BSA) service integration, which does not yet support RDAP,” she said.

The BSA is the GoDaddy-backed project that offers the multi-TLD GlobalBlock trademark-blocking service.

Nominet’s flagship .uk is also still offering Whois, because Nominet discovered that some of its registrars were still using it, rather than EPP, to do domain availability checks.

The fact that a GoDaddy service and some .uk registrars still don’t support RDAP, even after a years-long ICANN transition plan, is perhaps revelatory.

I’ll admit the only reason I noticed Nominet’s Whois coverage was patchy was that I’d neglected to update one of my scripts and it started failing. Apparently I was not alone.

While RDAP can be fairly simple to implement (if I can do it…), actually finding each registry’s RDAP server is a bit more complicated than under the Whois regime.

All gTLD registries were obliged to offer Whois at whois.nic.[tld], and IANA would publish the URLs on its web site, but RDAP URLs are not standardized.

It’s not super obvious, but it seems instead you have to head over to IANA’s “Bootstrap Service” and download a JSON file containing a list of TLDs and their associated base RDAP URLs.