Maybe they want to avoid the ambiguity between john.doe.name versus john-doe.name, and I assume they prefer the latter scheme because it probably sells better. Nevertheless, discontinuing existing domains is disgraceful.

I'm surprised they don't just do that, and maybe even to go a little further, disallow renewals so you can phase people out and reclaim domains you can sell.

That would be so cool and would make these limited hot commodities.

.name was one of the very first expansions of gTLDs back in the very early 2000s. It's a shame that it's being shut down as it was spearheaded by the ICANN itself rather than some registrar / investor like Donuts, Inc.

I suppose this is impractical as someone has to run the registry and there are costs associated with that. But don't the domain fees cover it?

There should be a conflict resolution to gracefully degrade the third level to 2nd level when there is no competing name on the second level.

But I didn't think about the 1st level competitors. There'd still need a mechanism to resolve that...

1. First come first serve? (e.g. whoever registered a y.name first, whether x is bob or sue is determined by the earliest registrant on record) 2. Lottery/random selection? 3. Bidding war?

I think the problem is 2nd level domains who have the same name will be a problem when they find out all these other 3rd level are now expiring and can run a route to spoof? Likely wouldn't happen, but with the fuckery in the DNS that can happen... This is such a rash and weird decision to push through so quickly just because engineers find it "easier" while ignoring the implications of the move, seemingly when it comes to larger scale security.

I assume there would have to be some method to prevent routing of third level domains to subdomains of two-levels... (or is that just me being a fool yet again, assuming we have competent administration of our systems).

.co.uk is run by the same people as .uk. There is no additional org that you trust when you register a .co.uk: https://en.wikipedia.org/wiki/.uk#Second-level_domains

> do browsers have a wildcard suffix list

Yes: https://publicsuffix.org/ and they have discussed this situation here: https://github.com/publicsuffix/list/issues/2306

Since neither smith.name nor the wildcard *.name appear in the Public Suffix List (https://publicsuffix.org/), browsers would likely allow any page on a *.smith.name domain to set cookies for .smith.name.

There was an effort to properly handle the .name 2LDs, but it was never resolved because there’s no easy way to tell a reserved 2LD (open for 3LD registrations only) apart from a normal 2LD on .name: https://github.com/publicsuffix/list/issues/2306

So yes, this TLD’s setup is in fact pretty insane.

Nobody owns the .co part of .co.uk. If you buy foo.co.uk, that is registered with Nominet, who are the registry for .uk.

About 20 year ago I registered {lastname}.name and have dozens third level domains below it. So there are "privately owned" second level domains under .name for quite some time...

Note that the posted link talks about .uk.co, which currently does not exist but I guess may have in the past. Where .co is the ccTLD of Colombia.

Different from .co.uk.

Surprisingly the public suffix list doesn't list `*.name`. So they're indeed not properly isolated from each other.

https://publicsuffix.org/

edit: apparently not all second level domains in .name are public suffixes anymore, so a wildcard addition wouldn't be correct.

So, this kind of thing happens all the time, and there's the Public Suffix List for exactly this problem.

There would be no issue at all if Verisign, or maybe Global Name Registry, decided to stick to the 3rd level registrations exclusively. Problem is, the chucklefucks over there decided it was a good idea to also hand out 2nd level registrations. Those 2nd level registrations outnumber the 3rd level registrations by an order of magnitude, so the PSL decided to just let joe.smith.name and john.smith.name share cookies. Which, IMO, was not a good decision, but it is what it is.

.uk.co (mentioned in the blog) isn't .co.uk

> I always thought .co.uk

What the hell are you talking about ?

1. The Nominet rules are crystal clear about which 2LDs are managed by Nominet[1] (co.uk, sch.uk, gov.uk etc. etc.). `co.uk` has been a Nominet managed 2LD since 1996 and it is not going anywhere.

2. FUN FACT ... Nominet introduced the ability to register directly under `.uk` much, much later, in 2014. Before 2014 your only option was to register under the auspices of a Nominet managed 2LD, e.g. `co.uk`. Ownership of a third-party 2LD is validated in 10 seconds via the usual WHOIS.

I suspect you meant 'uk.co' and other such shenanigans. Please correct your post accordingly.

[1]https://nominet.uk and https://www.nominet.uk/wp-content/uploads/2025/03/UK-rules-o...

It wasn't obviously wrong in 2001. .pro started with a similar structure around the same time.

Agree that the .name 3rd level domains are silly, disagree on .co.uk being a problem.

If .gov and .mil and .com make sense, then .gov.cc and .mil.cc and .com.cc make sense.

Of course, I think having more than one non-cc TLD was a mistake, but that's just me. If it makes sense to have topical TLDs for international and US institutions, it make sense to have national ones.

Never heard of DNTLS, thanks for sharing. I skimmed the Website Abd am a bit uncertain hat the ai angle is. Shouldnt naming be, well, just naming?

There is already ENS.

Well, nothing, but it does assume that Verisign doesn't have an unstated plan to do something else with .name. Domain registration is the real estate of the Internet and very little that has happened in the last 30 years of domain name policy has been for the benefit of anyone outside the the registrars.

For all we know, this is simply the first step in a series of moves for Verisign to better monetize the .name TLD in some novel fashion.

My evidence for this is that Verisign's own arguments for terminating the third-level domains are highly dubious. They claim that the third-level domains are too hard for them to manage. Bollocks: there are only 22,000 of them in use. That is a VERY small database that practically fits on a calculator and I refuse to believe that any manual labor around it is an outsized burden compared to pretty much any other semi-popular TLD. The second claim is that "the majority of those are not in use." Okay, if that's true, then where is the management burden coming from? That means tens of thousands of people are giving them money and getting nothing in return, isn't that the definition of an ideal business model?

It just doesn't pass the sniff test.

And finally, having read both of the linked documents, it sounds like people who have registered their .name for years in the future are not getting their money back. Are they likely to pay a second time, to a sub-registrar with no history?

Depends on how much one trusts whoever's running fraser.name. Is it more or less than Verisign?

"Well, it doesn't affect the lifecycle of domain names. The lifecycle is defined in some RFC somewhere, and this change doesn't modify that. Now, these particular domain name instances might be adversely affected, but you didn't ask about that." -- lawyers, probably.

No, we were in fact part of the very first batch of "new" TLDs

I think it was figure of speech. The domain is registered until 2036

> Registry Expiration: 2036-01-29 00:00:00 UTC Updated: 2026-09-03 08:12:27 UTC Created: 2002-01-23 14:41:45 UTC

it's probably a 10 year registration, plus a pre-paid renewal at the registrar

I'm sure Verisign would be thrilled to have a bidding war between the legitimate owners of fraser.name and a bunch of third parties they suddenly enabled.

This is silly question, but is your family managing trust in you as lone guy - cousin, father, brother - having potentially access to all their emails?

I feel that I more trust some corpo (Google, etc) that one particular person.

I don't imagine setup where you can effictevely guarantee them full privacy.

It was deemphasized pretty early because people didn't understand it.

It made sense to us because our starting point was an email service letting people share lastname.sometld, but we never got close to as many registrants on .name as we had users on the webmail service (we had a couple of million accounts on that when it was sold to one of Marc Cubans companies for a relative pittance in the aftmath of the dot com bubble bursting)

If aaa.bbb.name is registered, then bbb.name cannot be registered.

bbb.name can ONLY be registered if it is not already registered AND there are no 3rd levels registered on bbb.name currently.

https://manage.whois.com/kb/servlet/KBServlet/faq1485.html

> Or pick any TLD and register ˋ a 2nd-level domain (ˋfraser.tld`)?

How would that help? The problem is that he's losing access to all the accounts currently tied to fraser.name, if he is changing that he can just use any arbitrary domain anyways.

There will other people with the Fraser surname in the exact same position.

Because only one lucky person can own `fraser.name` at any one time in your model. And whilst that lucky person might be able to register their family members for free. There will be countless more (unrelated) Frasers who won't be able to register (even for money) their own `FIRST.fraser.name`.

So the argument goes, society as a whole gains more if we prevent anyone from owning `fraser.name`.

A legitimate alternative though, is to register `FIRST-fraser.name`

At the beginning of the existence of the .name TLD you couldn't do that, you were forced to register firstname.lastname.name and provide an ID to justify registering this specific domain.

With it you got an email redirection from firstname@lastname.name to the address of your choice. At some point this feature was discontinued (I assume when VeriSign took control of the .name TLD), a bit after it was decided (again by VeriSign) to allow registering first level .name domain. My main email address stopped working from one day to another without me being warned in any way.

When this happened I've emailed VeriSign and my registrar at the time, and tried several time since then, to be able to register the first level domain I'm the only one using, but they categorically refuse, despite recognizing that a single subdomain has ever been registered. They kept saying that I could just let the domain expire, wait for the grace period, and register it once it's liberated, hoping that no one does it before me, and without any solution for the downtime in the mean time…

And now this… fuck VeriSign -_-

Seriously.

  > 7.3. Provide any other relevant information to include with the request. If none, respond with “N/A.”
  > None.

I think the “not applicable” is to the elided second sentence of the question:

> 3.6. Have you communicated with any of the entities whose products or services might be affected by the introduction of your proposed service? [→ No.] If so, please describe the communications. [→ Not applicable.]

Gotta say that the entire form feels not applicable. The proposed service is the discontinuation of an existing service. I see from their website that other similar things do the same, but it feels broken when so many of the questions become nonsense.

This is how you fill out an application when you know it's going to be rubber-stamped.

The nerve.

The ability to register fraser.geek so a very small number of OpenNIC users can access that new URL doesn't really solve the OP's problem with his family's long-established URLs disappearing and their emails being directed to whichever scammer buys up the fraser.name domain.

Plenty of people and businesses have their own (DIY, etc) devices that need to use DNS. I mean it wouldn't really be the internet of things, if it didn't actually use the internet...

For instance, I own a .house domain that I use for a bunch of stuff that I've programmed. It would be a pain in the ass to go change that domain out. Now take that to next level and you're a business that's deployed a few thousand devices that need to call home.

I guess all this is to say - IoT doesn't just mean cheap botnet honeypot IP cameras. Take a look at https://www.balena.io/cloud for instance

He didn't say his IoT devices relied on 'cloud' accounts. He said there are IoT that use services on this domain.

Imagine he's set up some IoT devices at his parents' home, and those devices use services that he hosts somewhere on the internet. It would be silly to hard code the IP addresses in there, right (unless he operates his own ASN)? So he would use DNS to allow those devices to find his server(s). This would be the case whether the servers are at his home, at his office, or in a rack at a data centre.

It sounds to me like you understand the point perfectly well, you just cared to make a different point.

What does Paramount have to do with the last name Frazer?

What was the deal with .org?

EDIT: seems like Ethos Capital private equity firm wanted the .org registry, and Xavier Becerra (Attorney General of California at the time) wrote a letter that played major role in transaction being rejected

> Dear Messrs. Botterman and Marby:

>

> I urge ICANN to reject the transfer of control over the .ORG registry to Ethos Capital.

> The proposed transfer raises serious concerns that cannot be overlooked.

(from https://itp.cdn.icann.org/en/files/correspondence/becerra-to...)

I wonder which tech nonprofit would be best to champion this cause. Doesn't seem quite the EFF's domain.

Family of ESR or who is this?

.org almost got screwed in 2019 too:

> In April 2019, ICANN proposed an end to the price cap of .org domains and effectively removed it in July in spite of having received 3,252 opposing comments and only six in favor. A few months later, the owner of the domain, the Public Interest Registry, proposed to sell the domain to investment firm Ethos Capital. After intense criticism from nonprofit groups and significant figures in Internet history, the proposal was scrapped.

Surprisingly not by Verisign, who gave up .org in 2003.

Those are all controlled by companies in and subject to the demands of the USA, which has been proving for many years that they cannot be trusted.

Also, all common names with any of those prefixes have been registered a long time ago.

May I ask what is wrong with Verisign?

> So, where is our fully decentralized TLD alternative, free of ICANN or any central authority to handle how we grant names by conventions, without any money scheme in the game that attracts malevolent actors moving only through greed strings?

We can all edit our hosts file.

The problem with a lack of a central authority is domain names are most useful if they follow the highlander principle. There can only be one neil.fraser.name ... otherwise it's not usable for routing traffic if every webserver a Neil Fraser runs uses that address. (Yes, there are useful ways for one name to resolve to different webservers, but almost always those are webservers under at least loose control of a single entity or very exceptional cases)

Namecoin (.bit) was an attempt to create naming system without a central authority using a blockchain.

But from what I remember, they fucked up the pricing function and it got overrun by domain grabbers.

Don't want to get scooped by GoDaddy when they hear the good news.

Consider whether you'd be questioning this if the author had written that within minutes of his daughter being born, her photo was on Facebook. The only thing it suffers from is not being normalized and taking marginally more* effort, while being nowhere nearly as creepy.

* or arguably the same amount or less; for additional context: the author is an ex-Googler

Maybe they wanted the Created Date for the domain to match the birth date.

I even suspect that the name of the child was dependent on the domain name being free... but then, it shouldn't be too hard to set up the request in advance and just press the button once the child is born. Maybe there was some rule that names could only be registered for living (i.e., born) persons?

Pretty crazy to be focused on anything other than your immediate family in after a birth... but not exactly unprecedented when you look at social media posts!

To be faiiiir, when your partner is absolutely zonked out in the minutes post-delivery, what else is there to do when you're by their side and still half-asleep? Time to start announcing your pride and joy to the world, starting with a domain zone file.

I mean, you've already had 10 months to come up with some name ideas. It's not like it's a huge surprise when it happens. You could even register the names before they're born.

He didn’t say how many minutes.

It was more than one minute.

just a figure of speech

Priorities. /s

That's 22k people with third level domains like first.last.name. There are close to 100,000 second level last.name registrations, which are not going anywhere.

https://www.icann.org/resources/pages/name-2014-03-03-en

According to Wikipedia, "Verisign was the outsourced operator for .name since the .name launch in 2002". That makes the reasoning yet more puzzling.

> nonstandard TLD

What exactly is non-standard about an ICANN-approved TLD? Yes, the multi-level structure is a little odd, but given that ICANN approved it in the first place, one has a reasonable expectation that they would work as advertised.

.name is in no way a "nonstandard TLD." It has been in existence for a quarter of a century and was part of the first batch of new gTLDs approved after the dot-com boom had begun, in 2000.

For the first couple of years of .name's existence, it only allowed registration of third-level domains, and the ability to register second-level domains was added later (and only if no third-level domains existed for that second-level domain).

The author is in no way at fault here, and I don't think I would have assumed there was a heightened level of risk if I were him.