Google says its ccTLDs “are no longer necessary”

Google is going to stop using country-code TLDs for its web sites around the world.

The company said today that “country-level domains are no longer necessary” because it’s become so good at localization that it doesn’t need to have search users visit their local ccTLD domain to figure out where they are.

All of its ccTLD sites will start redirecting to google.com over the coming months, Google said in a blog post. The only impact users will see is having to re-enter search preferences, it said.

The move is a bit of a blow, albeit a bearable one, to ccTLD registries, which will no longer have their brand associated with the internet’s most-popular web service. Google.com is already the most-visited domain in the world.

Google readying its next batch of gTLD launches?

Three more of Google’s stockpile of long-dormant gTLDs showed signs of activity recently, strongly suggesting the company may be preparing to launch them.

The domains get.eat, get.fly and get.here were all registered February 20, according to zone files and Whois records. While none yet resolve, Google typically uses “get” domains for its customer-facing registry web sites.

Other than nic.[tld] and domaintest.[tld], none of the three had previous registrations apart from .here, which had on.here registered back in 2016. That domain resolves for me, but to an infinitely reloading blank page.

Google is currently fresh from the launch of .channel, which went into general availability February 11 and currently has 1,451 names in its zone file.

Google scuppers Team Internet acquisition after profit warning

A Norwegian private equity company has dropped its plans to acquire Team Internet after Google changed the way it handles advertising on parked domains, a key source of revenue for the company.

Oslo-based Verdane had a deadline of today to announce a formal offer for the company, but instead said it “does not intend to make an offer” because “there has been a material change of circumstances”.

While Verdane did not elaborate, there was a simultaneous announcement from Team Internet that Google’s recently announced changes to AdSense for Domains present a “challenge” that will harm its business faster than it can adapt.

Google said last week that as of March 19 it will start opting its advertisers out of AFD, the service domainers and registrars use to monetize many parked domain names. Advertisers will be able to opt back in, but are not expected to do so en masse.

Team Internet’s Search reporting unit made $72 million of its $91 million net revenue from AFD last year, which it expects to decline following the changes.

The company said it plans to instead monetize its domains using Google’s newer Related Search On Content product, which shows Google search results including paid results on the publishers’ own sites, based on the content of the page.

That presumably means Team Internet is going to have to populate its domains with spammy, low-quality and presumably AI-generated content, in order to trigger the RSOC contextual algorithm. Thanks, Google!

“The market development has been long-anticipated, though the announced acceleration is a challenge,” Team Internet told investors.

“It is anticipated that, during this transition period, contributions from AFD will decline faster than contributions from RSOC appreciate, meaning that the financial performance of Team Internet’s Search segment will see a trough in 2025 before it recovers from 2026 onwards and returns to the long-term pattern,” it added.

It expects adjusted EBITDA to more than halve for the year in its Search segment, from $57 million last year to between $20 million and $25 million this year. The company said its domains business, which includes its registry and registrars, should be unaffected.

But that domains business seems to be still up for sale. Team Internet said it has received “repeated approaches” for the domains unit and is carrying out a “comprehensive review of its asset ownership”.

Amazon and Google among .internal TLD ban backers

Google and Amazon have publicly backed ICANN’s plan to reserve the top-level domain .internal for private behind-the-firewall uses.

ICANN picked the string “internal” as the one that it will promise to never delegate to the DNS root, allowing network administrators and software developers to confidently use it with a lower risk of data leakage should the TLD come under a registry’s control in future.

The public comment period over its choice is coming to a close tomorrow, with a generally supportive vibe coming from the 30-odd comments submitted so far.

Notably, tech giants Amazon and Google have both filed comments backing .internal, with both companies saying that they already use the TLD extensively for internal purposes (Google in its Cloud services) and that to allow it to be delegated in future would cause big problems.

Some commenters niggled that .internal is too long, and that something like .local or .lan, both already reserved, might be better. Others wondered why strings such as .corp or .home, which are already effectively banned due to the high risk of name collisions, were not chosen instead.

.ing doing way better than .meme

Google Registry launched two new gTLDs in December, and just over a month later one is doing way better than the other.

As of the latest zone files, .ing has over 16,000 domains, while .meme has just 2,700. Both went to general availability on December 5.

This might seem surprising, given that .ing is intended purely for domain hacks, but memes are of course ephemeral things where registering a matching domain might not be a sound long-term investment strategy.

Both Google launches pale in comparison to the registry’s most successful gTLD, .app, which sold over 250,000 names in its first month, May 2018.

Google sells five-figure AI domain and six-figure .ing hack

A single-letter domain, an AI-related name, and a category-killer domain hack appear to have been sold by Google Registry during the latest week of its ongoing Early Access Period for the new .ing gTLD.

Judging by the .ing zone file, at least three domains have been registered in .ing since I last posted about the apparent seven-figure sale of host.ing a couple weeks ago.

The new names are w.ing, shipp.ing and tur.ing. I assume tur.ing refers to war hero Alan Turing, one of the fathers of computing and namesake of the Turing Test, used to judge AI intelligence.

w.ing was registered first, on November 13, when it would have incurred a six-figure price tag, according to published registrar retail prices. The registrant is listed as Google via the registrar Markmonitor.

Unlike w.ing and host.ing, the other two were registered via GoDaddy (albeit with redacted registrant names) so we can be more confident they are actually sales to third-party registrants.

Both shipp.ing and tur.ing were registered shortly after Google’s EAP rolled over into week three pricing ($35,000 at 101Domain‘s low-end prices, as a guide) on November 21 at 1600 UTC.

If Whois can be relied upon, the shipp.ing registrant is based in Texas and the tur.ing registrant in Arizona.

tur.ing is the only one trying to resolve currently, from where I’m sitting, but it fails due to a cert error.

Google’s EAP enters week four tomorrow at 1600 UTC, at which point prices fall daily until they settle at general availability pricing on December 5.

Did somebody spend a million bucks on a Google domain hack?

There’s evidence that Google Registry may have sold a .ing domain name for seven figures during its pre-launch period.

Google is well into its Early Access Period for the new gTLD, which runs for five weeks with premium prices decreasing every week or day until December 5, when they go to general availability pricing.

The EAP was notable for just how premium the first-week prices were — if you really wanted a quality domain hack for your business, it would cost you well north of $1 million.

But as far as I can tell from zone files, just one domain was added during that first week — host.ing, which has a Whois creation date of November 6, well within the cut-off for the seven-figure price tag.

The domain does not resolve and Whois currently shows Google itself as the registrant and Google’s go-to registrar, Markmonitor, as the registrar.

So it may be a self-reg, but waiting until EAP to grab a name in-house when Google has had literally years to do so does seem unusual.

Google to launch two fun new gTLDs next month

Google Registry is continuing its piecemeal rollout of new gTLDs with the launch of .ing and .meme this September.

Both TLDs will go to sunrise for a month from September 20, with general availability from December 5.

While both will have more-expensive Early Access Period phases, .meme is also getting a Limited Registration Period where “only content creation platforms specializing in the creation and distribution of internet memes may apply”.

While .meme is a pretty self-explanatory regular TLD with standard amount of long-tail potential, I think .ing might be the first TLD ever to launch with domain hacks as the primary envisaged use case.

Google gave “design.ing or writ.ing, ink.ing or row.ing” as potential domains.

There are a finite number of English verbs that would work well with a .ing suffix, potentially limiting registrations. I doubt the TLD will pass the 50,000 name threshold at which ICANN starts charging transaction fees, unless some other use cases are found.

Newly launched .zip already looks dodgy

A trawl through the latest zone file for Google’s newly launched .zip gTLD reveals that it is likely to be used in malware and phishing attacks.

.zip is of course also a filename extension used by the ZIP archive format, often used to compress and email multiple files at once, and many domains registered in the .zip gTLD in the last few days seem ready to capitalize on that potential for confusion.

I counted 3,286 domains in the May 14 zone file, and a great many of them appear to relate to email attachments, financial documents, software updates and employment information.

I found 133 instances of the word “update”, with sub-strings such as “attach”, “statement”, “download” and “install” also quite common.

Some domains are named after US tax and SEC forms, and some appear to be targeting employees at their first day of work.

I don’t know the intent of any of these registrants, of course. It’s perfectly possible some of their domains could be put to benign use or have been registered defensively by those with security concerns. But my gut says at least some of these names are dodgy.

Google went into general availability with eight new TLDs last Wednesday, and as of yesterday .zip was the only one to rack up more than a thousand names in its zone file.

The others were .dad (913 domains), .prof (264), .phd (605), .mov (463), .esq (979), .foo (665) and .nexus (330).

Google to drop EIGHT new gTLDs

Google Registry has announced launch details for eight new gTLDs that it has been sitting on for almost a decade.

It plans to launch .foo, .zip, .mov, .nexus, .dad, .phd, .prof and .esq over the coming couple of months, with all eight following the same launch schedule.

Sunrise will begin this weekend, April 2, and run for a month. The Early Access Periods will run for a week up until May 10, when they’re all go into general availability.

The .zip and .mov spaces will be worth keeping an eye on, especially for those in the security space.

Both gTLDs match popular file extensions — for compressed data and video respectively — which could present opportunities for innovation among the internet’s more nefarious players, such as phishers and malware distributors.

.zip is for “tying things together or moving really fast”, Google said, while .mov is “for moving pictures and other things that move”.

All of the new spaces appear to be marketed at general audiences, with no registration restrictions.