News for hackers. Stuff that matters.
Re:.name Grandfathered by toomuchtodo on Tuesday November 10, 2026 @11:38AM (#50442749)
Re:.name Grandfathered by derhuerst on Tuesday November 10, 2026 @11:54AM (#50442975)
previous discussion on the predecessor post, 69 days ago, 547 comments: https://news.ycombinator.com/item?id=49550772
Re:.name Grandfathered by Tepix on Tuesday November 10, 2026 @11:55AM (#50442990)
Vive la résistance!

Resistance is not futile.

Re:.name Grandfathered by cobbzilla on Tuesday November 10, 2026 @12:02PM (#50443089)
> to my lawyers Jan, Flip and Diégo who threw the book at ICANN

Resistance with a strong case and competent lawyers is not futile.

Re:.name Grandfathered by dataflow on Tuesday November 10, 2026 @12:08PM (#50443176)
[delayed]
Re:.name Grandfathered by doublepg23 on Tuesday November 10, 2026 @11:59AM (#50443059)
I've had a .name for almost a decade now and was not aware of it's history.

Shame I didn't register on my lastname .name , I had thought it was a much newer gTLD.

Re:.name Grandfathered by dist-epoch on Tuesday November 10, 2026 @12:08PM (#50443178)
So, turns out Verisign is not the Devil incarnate?
Re:.name Grandfathered by cobbzilla on Tuesday November 10, 2026 @12:31PM (#50443431)
The Devil is no match for a sufficiently talented attorney
Re:.name Grandfathered by mh- on Tuesday November 10, 2026 @01:06PM (#50443893)
In 1997, this was explored in a documentary featuring Keanu Reeves.
Re:.name Grandfathered by NateEag on Tuesday November 10, 2026 @01:07PM (#50443904)
Re:.name Grandfathered by brettermeier on Tuesday November 10, 2026 @12:58PM (#50443761)
Why do you think that???
Re:.name Grandfathered by a1o on Tuesday November 10, 2026 @12:09PM (#50443183)
How does one register a domain under .name ? I can’t find info through search because it discards the dot no matter what I try.
Re:.name Grandfathered by SahAssar on Tuesday November 10, 2026 @12:12PM (#50443223)
Available under standard registrars that offer many TLDs, like inwx.com: https://www.inwx.com/en/domain/check?domain=testtest123.name...
Re:.name Grandfathered by peesem on Tuesday November 10, 2026 @12:16PM (#50443272)
but which support the actual third-level domains? for example, my last name is already taken as a .name domain by verisign, what if i want my firstname.lastname.name domain?
Re:.name Grandfathered by mercurywells on Tuesday November 10, 2026 @12:31PM (#50443426)
You'd have to try to find the contact that owns lastname.name and work out a private deal - you won't get ICANN protections though.
Re:.name Grandfathered by xigoi on Tuesday November 10, 2026 @01:03PM (#50443852)
The third-level domains are still being discontinued, it’s just that people who already have one get to keep it.
Re:.name Grandfathered by zamadatix on Tuesday November 10, 2026 @01:13PM (#50443976)
One can't (officially) register such 3rd level domains anywhere anymore.

It's just a combination in the ambiguity of what "it discards the dot" should mean in GGP's message combined with the article already clarifying 3rd level domains are not available on .name anymore leading to a lot of confused comments.

Re:.name Grandfathered by delecti on Tuesday November 10, 2026 @12:13PM (#50443230)
Re:.name Grandfathered by toast0 on Tuesday November 10, 2026 @12:15PM (#50443254)
Same as any gTLD, pick your favorite registrar and they probably support it. Give your registrar money, they'll give the registry money and boom. (more or less)

When .name was new, you may have needed to contract with the registry directly, it was an early new gTLD and I don't remember if they started with the registry/registrar split or not.

Afaik, new registrants are not able to register a third level domain, but second level domains have been available for a long time.

Re:.name Grandfathered by lambda on Tuesday November 10, 2026 @12:32PM (#50443437)
Did you read the link?

"Although they will be closing new registrations for 3rd-level .name domains, all existing domains (including this website) and email redirects will remain indefinitely."

They were apparently planning on shutting down the whole TLD. They will be leaving it up for existing registrants, but not allowing new registrations.

Re:.name Grandfathered by ksala_ on Tuesday November 10, 2026 @12:37PM (#50443489)
No, they were not planning that. This is only about 3rd level domain as the paragraph you quoted says. Every other TLD don't sell those (afaik). Normally "someone.name" would be a domain, and they would own all the subdomains. .name allowed you to register "one.someone.name" and "two.someone.name" as completely separated domains with completely separated owners. I understand why they should grandfather in existing domains but this was just madness.
Re:.name Grandfathered by lambda on Tuesday November 10, 2026 @12:39PM (#50443510)
Ah, fair enough. I kind of thought that third level domain registration was the whole point of the .name TLD, so I was interpreting it as shutting it down.
Re:.name Grandfathered by ksala_ on Tuesday November 10, 2026 @12:45PM (#50443598)
Good question. Yeah no idea - the email linked in OP says they're going to send a new proposal, I'm assuming it will cover how they're planning to handle it. And I guess that yes blocking second level domains that have a third level already registered is the pragmatic choice.
Re:.name Grandfathered by duskwuff on Tuesday November 10, 2026 @01:31PM (#50444263)
> I kind of thought that third level domain registration was the whole point of the .name TLD

It was initially! But there was enough demand for second-level registrations that they opened that up too (and set the stage for this whole mess).

Re:.name Grandfathered by toast0 on Tuesday November 10, 2026 @01:52PM (#50444525)
> So the weird part then comes in: are all second level domains that have third level registrations now reserved? Do they stop being reserved if the last third level registration expires without being renewed?

Yes, second level domains that overlap with a registered third level domain have never been available. Under the original proposal, once all the third level domains were dropped, the overlapping second level domains would have been available (first come, first served). I believe current practice is the second level domain becomes available if all of the third level domains expire. Registrants in other threads indicated that there's no process to have an orderly transition from being the only the registrant of a third level domain under a specific second level name to registering that second level domain ... you would have to let your current name expire and hope to catch the second level name.

Re:.name Grandfathered by giancarlostoro on Tuesday November 10, 2026 @12:14PM (#50443236)
> After a long and expensive battle, news just dropped that Verisign is retracting its plan to terminate 22,000 domain names and email redirects. Although they will be closing new registrations for 3rd-level .name domains, all existing domains (including this website) and email redirects will remain indefinitely.

This was what I figured SHOULD happen when they did this. Allow existing customers to keep renewing, but nobody new allowed, if a tld frees up over time, reclaim it completely and sell it off.

What they were proposing should really be illegal.

Re:.name Grandfathered by Spivak on Tuesday November 10, 2026 @01:20PM (#50444082)
For it to be illegal I think we would have to have much stronger digital ownership laws. I would certainly support them. But for now a domain you "own" is just an entry in someone else's ledger and control is only enforced by contract for big players willing to pay.
Re:.name Grandfathered by mzajc on Tuesday November 10, 2026 @01:25PM (#50444165)
These domains wouldn't be worth a penny if they came with a disclaimer that they can be deregistered or even taken over at any point. With a bit of luck, somebody could snatch popular last name domains and set up a catch-all mailserver.
Re:.name Grandfathered by schoen on Tuesday November 10, 2026 @01:27PM (#50444203)
They do have such a limitation, because of things like UDRP. It's just that there are maybe some forms of restriction on the processes by which domain names can be involuntarily transferred or seized. But it's a real possibility!
Re:.name Grandfathered by not2b on Tuesday November 10, 2026 @03:03PM (#50445543)
People persist in "buying" digital movies e-books, and games despite the fact that they can disappear at any point, without warning, because the seller's license expired or they just feel like discontinuing the service.
Re:.name Grandfathered by schoen on Tuesday November 10, 2026 @01:26PM (#50444179)
There is a Ninth Circuit decision that domain names are a form of property

https://en.wikipedia.org/wiki/Kremen_v._Cohen

but it's tricky because the domain name registries and registrars have a kind of thicket of contracts nowadays that subordinates registrants' property interests to other rules and considerations. So I don't think a court would think that a modern-day domain name registrant has property rights in a domain name that supersede all of those contractual terms.

Edit: my recollection is that Kremen v. Cohen interpreted the legal defaults that applied because Kremen registered the domain name in an era when Network Solutions didn't require registrants to agree to a contract that limited Network Solutions's liability and gave it various explicit rights and powers.

I'm not a huge ICANN expert, but I think ICANN broadly thinks the status quo is preferable to one in which registrants had stronger, less equivocal property interests in names.

Re:.name Grandfathered by otterley on Tuesday November 10, 2026 @02:27PM (#50445046)
The Wikipedia summary of the case suggests that the ruling was much more than it was. Courts tend to rule on narrow issues, as it did here.

The question before the Court was not whether a domain name is a form of property. Both parties agreed that a domain name are a form of property; that wasn't in dispute. The Court did affirm their position in black letter law, though.

Rather, the question before the Court was whether, as intangible property, a tort of conversion claim could be made against it under California law. Previously, cases disagreed as to whether it could be recognized. The Court found that it could be.

Re:.name Grandfathered by falcor84 on Tuesday November 10, 2026 @02:06PM (#50444734)
Agreed, but I just wanted to say that essentially every single thing anyone owns is, and has been from the invention of tally marks on clay tablets, an entry in someone's ledger.
Re:.name Grandfathered by schoen on Tuesday November 10, 2026 @01:25PM (#50444171)
(meant to reply to the child post, moved there)
Re:.name Grandfathered by echelon on Tuesday November 10, 2026 @01:34PM (#50444287)
Now a ".name" will be really awesome to own.

This is essentially premium real estate now.

Re:.name Grandfathered by Macha on Tuesday November 10, 2026 @02:44PM (#50445312)
Well anyone can buy a second.name if second isn't already registered, and then set up their own first. subdomain, so most visitors aren't going to know the difference in between grandfathered in first.second.name sites and people who just bought second level domains and created their own subdomain.
Re:.name Grandfathered by jareklupinski on Tuesday November 10, 2026 @02:47PM (#50445353)
if you're lucky, you can do something like first.sec.ond

works for many polish people who own ski resorts :)

Re:.name Grandfathered by jayknight on Tuesday November 10, 2026 @03:01PM (#50445517)
I remember when delicious.com was just del.icio.us. I miss that site.
Re:.name Grandfathered by Jaxkr on Tuesday November 10, 2026 @02:00PM (#50444652)
Curious what they mean by “expensive”. Did they hire a lawyer? I thought this was just an Internet outrage campaign.
Re:.name Grandfathered by DANmode on Tuesday November 10, 2026 @02:08PM (#50444778)
> What they were proposing should really be illegal...

Where?

Re:.name Grandfathered by gsich on Tuesday November 10, 2026 @02:16PM (#50444885)
Everywhere.
Re:.name Grandfathered by DANmode on Tuesday November 10, 2026 @03:18PM (#50445740)
Super reasonable proposal.
Re:.name Grandfathered by kwanbix on Tuesday November 10, 2026 @12:18PM (#50443287)
[delayed]
Re:.name Grandfathered by clickety_clack on Tuesday November 10, 2026 @12:28PM (#50443402)
My thoughts also, but maybe they can make more from a few sites like baby.name than they can from personal domains.
Re:.name Grandfathered by lambda on Tuesday November 10, 2026 @12:48PM (#50443642)
It works differently than pretty much every other TLD, which means it's different code paths to support.

Many registrars don't support the unique 3rd level domain setup for .name, so it can be hard to find registrars that properly support it.

It's probably easier to support, and more valuable to sell second level .name domains.

Pretty terrible that they were considering just dropping tens of thousands of customer registrations however.

Re:.name Grandfathered by seattle_spring on Tuesday November 10, 2026 @02:51PM (#50445405)
> It works differently than pretty much every other TLD, which means it's different code paths to support.

but I was told that AI has made code obsolete and free

Re:.name Grandfathered by swiftcoder on Tuesday November 10, 2026 @01:30PM (#50444248)
It has weird interactions with some modern browser features. For example domain isolation doesn't apply between subdomains of the same TLD, so john.smith.name and drew.smith.name don't get isolation in naive implementations.
Re:.name Grandfathered by tylergetsay on Tuesday November 10, 2026 @01:33PM (#50444277)
wouldn't that be a problem with a lot of other domains? like locality domains
Re:.name Grandfathered by timeinput on Tuesday November 10, 2026 @01:47PM (#50444456)
It definitely is. <ingress>.k8s.<mydns>.com regularly confuses what password I want to use if I have different authentication per ingress. More commonly if I run something else at <name>.<mydns>.com firefox and chrome are both happy to offer up my password for <other service>.<mydns>.com.

Closed. Wont fix.

Re:.name Grandfathered by mixdup on Tuesday November 10, 2026 @02:36PM (#50445188)
yes, but other locality domains are fairly static and well-known

.co.uk wouldn't have the same problem because everyone knows that combo is a TLD in and of itself. with a seemingly infinite possible combinations of blah.name that could be a TLD itself, or, might just be a subdomain of .name, it gets really weird

Re:.name Grandfathered by OkayPhysicist on Tuesday November 10, 2026 @03:07PM (#50445598)
We solve that problem with the public suffix list. The problem is there's a lot of .name domains, each of which would need to be added to the list.
Re:.name Grandfathered by OkayPhysicist on Tuesday November 10, 2026 @03:06PM (#50445588)
The real problem is that we'd have to add a wildcard to the public suffix list. That's it.

The public suffix list is the big list of all the URL suffixes that should not imply shared ownership of all their subdomains. For example the line

com

says "XYZ.com" and "ABC.com" should not be assumed to be controlled by the same entity.

Problem is, all 1st level domains registered to the .name TLD should be added to the list, and that's a lot of domains. The correct answer, IMO, would be to add a wildcard

*.name

but that would involve updating all the code that relies on the public suffix list to support said wildcard.

Re:.name Grandfathered by eks391 on Tuesday November 10, 2026 @12:20PM (#50443312)
So glad this happened. When I first heard, I assumed that all the folks wronged would simply be disregarded even though Verisign was blatantly breaking consumer protection laws (I assume. If it wasn't, those laws are incomplete). The fact that Verisign even tried still makes me upset though. It's really annoying what several companies will do as long as their hand isn't forced due to legal or social repercussions
Re:.name Grandfathered by kinabalu76 on Tuesday November 10, 2026 @12:41PM (#50443541)
glad this got resolved, bummer it was thrown into question at all
Re:.name Grandfathered by charlieyu1 on Tuesday November 10, 2026 @12:51PM (#50443674)
Good for them. I just wish I could register a new .yu domain…
Re:.name Grandfathered by xydone on Tuesday November 10, 2026 @12:57PM (#50443742)
Certainly nice to know they would've almost certainly proceeded as normal if the concerns didn't blow up online
Re:.name Grandfathered by sparkling on Tuesday November 10, 2026 @01:01PM (#50443820)
If you are into stories about weird and obscure domain happenings: https://eualternative.eu/guides/bulgaria-bg-private-registry...
Re:.name Grandfathered by zamadatix on Tuesday November 10, 2026 @01:03PM (#50443848)
Congrats to those wanting to keep their domains! I'm surprised they went with perpetual (well, as much as anything is) support, i.e. allowing renewals and such rather than just letting it naturally expire (the initial proposal was to immediately cease these records at a given date with no clear communication on how they'd be protected or not from re-registering the upper level domains or not).
Re:.name Grandfathered by nticompass on Tuesday November 10, 2026 @01:13PM (#50443986)
WHAT‽ I let my "first.last.name" registration expire because of the impending shutdown!

I did notice that my domain kept working past the supposed shutdown date, but I let the domain registration expire.

I'm so mad now! I assume there is no way to get my domain/email forwarding back :(

I suppose I could try to ask the registrar, but I highly doubt they can do anything...

Re:.name Grandfathered by _blackhawk_ on Tuesday November 10, 2026 @01:18PM (#50444054)
Definitely email the registrar. Maybe it might work?
Re:.name Grandfathered by nticompass on Tuesday November 10, 2026 @01:28PM (#50444230)
Worth a shot.
Re:.name Grandfathered by BoxOfRain on Tuesday November 10, 2026 @01:19PM (#50444063)
While it won't lessen your frustration, I applaud your use of the interrobang. That punctuation mark needs wider use.
Re:.name Grandfathered by Spivak on Tuesday November 10, 2026 @01:23PM (#50444147)
It's a neat little mark but I don't think it has much of a chance being widespread because I think ?! has already won. I think it has a better chance of becoming an official grammatical digraph than the merged mark.
Re:.name Grandfathered by sillysaurusx on Tuesday November 10, 2026 @01:29PM (#50444239)
Is there an overlaid ?? and !! mark? (For Chess.)
Re:.name Grandfathered by adrian_b on Tuesday November 10, 2026 @02:08PM (#50444773)
Besides interrobang, Unicode includes all 4 possible sequences of 2 "?" and "!".

  203C;DOUBLE EXCLAMATION MARK;Po;0;ON;<compat> 0021 0021;;;;N;;;;;
  203D;INTERROBANG;Po;0;ON;;;;;N;;;;;
  2047;DOUBLE QUESTION MARK;Po;0;ON;<compat> 003F 003F;;;;N;;;;;
  2048;QUESTION EXCLAMATION MARK;Po;0;ON;<compat> 003F 0021;;;;N;;;;;
  2049;EXCLAMATION QUESTION MARK;Po;0;ON;<compat> 0021 003F;;;;N;;;;;
Re:.name Grandfathered by reaperducer on Tuesday November 10, 2026 @01:53PM (#50444545)
I don't think it has much of a chance being widespread

I first heard of it back when Usenet was still the hotness.

Apparently it's been around for close to a century, so if it hasn't caught on widely by now, you're probably right.

Re:.name Grandfathered by saalweachter on Tuesday November 10, 2026 @03:04PM (#50445568)
It lost when computers overtook typewriters.

On a typewriter, you could type one punctuation mark, backspace, and then type another.

Even once computers added the interrobang to Unicode (or older systems), you either need to type in a numeric code, use a secret bucky bit, or select it from a graphical UI, none of which is worth it for more than the odd weirdo with a whimsical streak.

Re:.name Grandfathered by nticompass on Tuesday November 10, 2026 @01:28PM (#50444226)
I'm not really frustrated, but it is annoying that I had to migrate accounts and stuff, but whatever.

And yes, I love the interrobang! Ever since I mapped scroll lock to "compose" on my keyboard, I've had fun typing all sorts of characters :)

Re:.name Grandfathered by lutoma on Tuesday November 10, 2026 @02:43PM (#50445300)
I have an auto substitution set up in iOS to automatically replace ?! with ‽ (Same for ellipsis, ... to …)
Re:.name Grandfathered by oneeyedpigeon on Tuesday November 10, 2026 @02:49PM (#50445377)
And, presumably, "!?"?
Re:.name Grandfathered by mzajc on Tuesday November 10, 2026 @01:20PM (#50444080)
I don't know about .name specifically, but some registries have a grace period (or multiple) after which you can still renew it. It's worth checking if you're within the time limit.
Re:.name Grandfathered by nticompass on Tuesday November 10, 2026 @01:27PM (#50444193)
That's my plan. If they can help then cool, otherwise it's not really a big deal.
Re:.name Grandfathered by edoceo on Tuesday November 10, 2026 @01:22PM (#50444128)
First time ive seen ! and ? overlaid. Neat.
Re:.name Grandfathered by BadBadJellyBean on Tuesday November 10, 2026 @01:24PM (#50444156)
It's called an interrobang. Never really took off but still available in unicode.
Re:.name Grandfathered by chch on Tuesday November 10, 2026 @01:27PM (#50444196)
For future reference, ‽ is called an interrobang!

And to show off another fun character, for languages like Spanish that start a question with an inverted question mark, there's also ⸘, the inverted interrobang.

Though I find the name some people call it, gnaborretni (interrobang backwards), much sillier.

Re:.name Grandfathered by serchinastico on Tuesday November 10, 2026 @01:47PM (#50444462)
Interesting! If we were to follow Spanish to name the inverted interrobang it'd be opening (and closing) interrobangs, not gnaborretni, just as we don't have nóicagorretni nor nóicamalcxe :)
Re:.name Grandfathered by murphyslaw on Tuesday November 10, 2026 @03:07PM (#50445597)
I assume you meant sgnaborretni?
Re:.name Grandfathered by mixdup on Tuesday November 10, 2026 @02:34PM (#50445165)
They haven't actually stopped taking third level registrations, so get in there before the revised proposal gets submitted approved and implemented
Re:.name Grandfathered by walthamstow on Tuesday November 10, 2026 @01:58PM (#50444615)
> thanks to ... Jim who flew to Bali to make the case to ICANN in person

What the heck is ICANN doing in Bali of all places?

Re:.name Grandfathered by erk__ on Tuesday November 10, 2026 @02:01PM (#50444661)
Its where their yearly general meeting was hosted: https://meetings.icann.org/en/meetings/icann87/

Last year it was in Spain and the year before it was in Mumbai.

Re:.name Grandfathered by wmf on Tuesday November 10, 2026 @03:03PM (#50445541)
It's NGO pork disguised as woke inclusion. Meetings in Africa or Asia Pacific are (theoretically) cheaper for historically disadvantaged people to attend.
Re:.name Grandfathered by bilalabdullahi on Tuesday November 10, 2026 @02:31PM (#50445104)
They shouldnt this easy to take away tbh
Re:.name Grandfathered by xyst on Tuesday November 10, 2026 @02:39PM (#50445232)
I wonder how much the midterm elections influenced Verisign in this decision to bend the knee in this "David v Goliath"-esque win.

I was expecting for Verisign to take this to court, drag it out, and bleed the opposing party out. I suppose the judges that Verisign lawyers depend on did not get favorable re-election.

Ofc it’s probably something less nefarious, and boring. Verisign probably did some basic math and determined that taking this to court with their army of overpaid lawyers was simply not cost effective compared to just supporting 3rd level domains.

Re:.name Grandfathered by asdfasdkljfhkah on Tuesday November 10, 2026 @02:45PM (#50445328)
Thousands of .name owners nearly became .gone owners. Nice to see Verisign choose the one migration plan every engineer secretly loves: don’t migrate anything.
Re:.name Grandfathered by not2b on Tuesday November 10, 2026 @03:08PM (#50445612)
I'm glad that the article writer got his domain back, but I wish we had a better term than "grandfathered". The origin of this term goes back to Jim Crow, when to stop Black people and newcomers from voting, many places in the American South imposed a near-impossible test you had to pass to register to vote, but also added a loophole: if your grandfather voted in your county (or sometimes your state), you could vote without taking the test. This was called the grandfather clause.
Re:.name Grandfathered by tln on Tuesday November 10, 2026 @03:19PM (#50445747)
"Legacied"
Re:.name Grandfathered by origini on Tuesday November 10, 2026 @03:11PM (#50445656)
I have bought my *.name domain a decade ago? Why was this ever a thing? Was there some limitation i'm to stupid to get or did one company just register some common last names?
Re:.name Grandfathered by ZeWaka on Tuesday November 10, 2026 @03:19PM (#50445748)
for specifically third level registrations