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...
giancarlostoro 5 hours ago
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...
Spivak 4 hours ago
mzajc 4 hours ago
schoen 4 hours ago
not2b 2 hours ago
schoen 4 hours ago
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.
otterley 3 hours ago
The question before the Court was not whether a domain name is a form of property. Both parties agreed that a domain name is a form of property; that wasn't in dispute. The Court did affirm their shared position in black letter law, though.
Rather, the question before the Court was whether, as intangible property, a tort of conversion claim relating to the domain name could be made under California law. Previously, cases disagreed as to whether it could be recognized. The Court found that it could be.
trollbridge 11 minutes ago
falcor84 3 hours ago
stevage 40 minutes ago
Calazon 14 minutes ago
echelon 3 hours ago
This is essentially premium real estate now. For us nerds, anyway.
Great job Neil and gang!
Macha 2 hours ago
jareklupinski 2 hours ago
works for many polish people who own ski resorts :)
jayknight 2 hours ago
hackboyfly 43 minutes ago
DANmode 3 hours ago
Where?
gsich 3 hours ago
DANmode 2 hours ago
nticompass 4 hours ago
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...
(Edit: I'm not actually mad, but it was annoying to have to move accounts from my [email protected] email to another one)
_blackhawk_ 4 hours ago
nticompass 4 hours ago
BoxOfRain 4 hours ago
Spivak 4 hours ago
sillysaurusx 4 hours ago
adrian_b 3 hours ago
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;;;;;zimpenfish 15 minutes ago
[0] https://www.fileformat.info/info/unicode/char/203c/index.htm
[1] https://www.fileformat.info/info/unicode/char/2047/index.htm
reaperducer 3 hours ago
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.
ahnick 32 minutes ago
This is the first (and probably last) time that I will ever see the words "Usenet" and "hotness" in the same sentence.
Well done, sir.
saalweachter 2 hours ago
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.
nticompass 4 hours ago
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 :)
lutoma 2 hours ago
oneeyedpigeon 2 hours ago
mzajc 4 hours ago
nticompass 4 hours ago
edoceo 4 hours ago
BadBadJellyBean 4 hours ago
chch 4 hours ago
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.
serchinastico 3 hours ago
murphyslaw 2 hours ago
mixdup 2 hours ago
Panda4 an hour ago
troyrollo 22 minutes ago
soupbowl 2 hours ago
Unfortunately I am stuck in commitments on a few of these domains and just had to eat the cost increases, the rest I moved to .com/.net.
.consulting was the worst offender.
pmdr 39 minutes ago
Yes, I view most 'new' TLDs as scams. They lure you in with a low price, a rather pricey renewal and then price hike after price hike down the line. They also charge a premium for most dictionary words right from the start.
greyface- 10 minutes ago
mlefer an hour ago
For all the ones holding exclusive second level domains, just give them the second level domain. For all the ones holding shared second levels, offer a buyout and/or allow parties to negotiate with each other on a shared ownership structure of the second level.
toast0 43 minutes ago
However, I also suspect that for most of the third level domains, they're on a second level domain with multiple registrants. And several of those shared second level domains will have a lot of registrants. If the registrants are in different jurisdictions, it becomes a pretty nasty process to develop international consensus, vs just keeping the status quo going (which IMHO, can't be that hard).
Still, it makes sense to have a process to normalize the single registrant second level domains, because less work.
troyrollo 14 minutes ago
That leaves quite a few with lots of unrelated registrants, mostly in Japan (tanaka and suzuki being the biggest).
derhuerst 5 hours ago
slow_typist an hour ago
kwanbix 5 hours ago
clickety_clack 5 hours ago
lambda 4 hours ago
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.
There's also an associate email redirect service, which is unique to .name and probably costs money to run and maintain.
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.
seattle_spring 2 hours ago
but I was told that AI has made code obsolete and free
charcircuit an hour ago
lambda an hour ago
.name was something where you could register a two part domain, picking both the third and second level, to represent your first and last name.
swiftcoder 4 hours ago
tylergetsay 3 hours ago
timeinput 3 hours ago
Closed. Wont fix.
mixdup 2 hours ago
.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
toast0 30 minutes ago
Verisign claimed approximately 22,000 third level domains [1] in July 2026. I don't see an estimate of the number of shared second level domains, but it's finite. The current public suffix list includes 10414 names [2]; so at maximum, the list would approximately triple in size --- not ideal, but feasible.
[1] https://itp.cdn.icann.org/en/files/consensus-policies/fessen...
[2] including some with wildcards, re: your other post
OkayPhysicist 2 hours ago
OkayPhysicist 2 hours ago
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.
toast0 39 minutes ago
If you want to do it properly, you really do need to include all of the second level domains that have more than one third level registrant. And update that periodically as domains expire... there might be three registrants under .example.name today, but if they all (or all but one) stop paying, example.name is no longer a public suffix and it should be removed.
OkayPhysicist 29 minutes ago
troyrollo 11 minutes ago
nikanj an hour ago
damoe an hour ago
Tepix 5 hours ago
Resistance is not futile.
cobbzilla 5 hours ago
Resistance with a strong case and competent lawyers is not futile.
dataflow 5 hours ago
calebio 30 minutes ago
Xirdus 18 minutes ago
codexon 2 hours ago
origini 2 hours ago
ZeWaka 2 hours ago
zamadatix 4 hours ago
hoppp 18 minutes ago
a1o 5 hours ago
SahAssar 5 hours ago
peesem 5 hours ago
mercurywells 5 hours ago
xigoi 4 hours ago
zamadatix 4 hours ago
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.
scott00 an hour ago
delecti 5 hours ago
toast0 5 hours ago
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.
lambda 5 hours ago
"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.
ksala_ 4 hours ago
lambda 4 hours ago
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?
ksala_ 4 hours ago
duskwuff 4 hours ago
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).
toast0 3 hours ago
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.
eloto333 an hour ago
doublepg23 5 hours ago
Shame I didn't register on my lastname .name , I had thought it was a much newer gTLD.
xydone 4 hours ago
bilalabdullahi 3 hours ago
walthamstow 3 hours ago
What the heck is ICANN doing in Bali of all places?
erk__ 3 hours ago
Last year it was in Spain and the year before it was in Mumbai.
wmf 2 hours ago
charlieyu1 4 hours ago
asdfasdkljfhkah 2 hours ago
kinabalu76 4 hours ago
xyst 2 hours ago
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.