3 ms·

> 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

> 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.

jawns 1mo ago
I have a .science domain and a .com domain. Even though .science was launched in 2014 (more than a decade ago), I still consider it a non-standard TLD and still deal regularly with difficulties around its use. (For instance, you wouldn't believe how many online services reject email addresses than end in .science because they use regexes that exclude TLDs with 7 letters.) Likewise, I've registered .lol and .fun domains but never would have assumed that just because they're available now, they will be available in perpetuity. In that sense, .name as a third-level TLD is even more non-standard, because the standard way domain registration works is by choosing a single "second level" domain name, then adding subdomains.
- angoragoats 1mo ago
  > Likewise, I've registered .lol and .fun domains but never would have assumed that just because they're available now, they will be available in perpetuity. Why wouldn't you assume this? > the standard way domain registration works is by choosing a single "second level" domain name, then adding subdomains The entire ccTLD systems of the UK, China, Germany, France, Japan, and many others would beg to differ.
  - jawns 1mo ago
    I don't think those are comparable, because when you register a .co.uk domain, you are selecting one name that precedes .co.uk, similar to how you register one name that precedes .com. Whereas with .name, you are choosing what appears to be a subdomain, followed by what appears to be a domain name. But under the hood, you do not own all subdomains for that domain name; you own only the combination of first_name.last_name.name.
    - angoragoats 1mo ago
      I'm not sure I understand. How is registering first.last.name not also selecting one name ("first") that precedes last.name, similar to how you register one name that precedes .com? (And yes, I am aware that you can also register last.name by itself, but only if there are no third-level domains using it, so for practical purposes it doesn't change my question above. Plus, when the OP originally purchased his domain, you could only buy third-level domains for .name.)
      - jawns 29d ago
        Present these two domain names to the average person: 1) benedict.cumberbatch.name 2) drstrange.co.uk I expect the average person would assume that for the domain 1, .name is the TLD, cumberbatch.name is registered by a private entity, and benedict (and any other subdomains associated with cumberbatch.name) is a subdomain fully controlled by that private entity. Whereas for domain 2, I think the average person will view ".co.uk" the same way they view ".com", even though technically it is both a ccTLD and a second-level domain.
        swiftcoder 29d ago
        Luckily the average person has no idea what a TLD or a subdomain are
        account42 29d ago
        They do if they are employed in a non-tiny company where they work at least partially on a computer and paid attention during security training.
        angoragoats 29d ago
        Even if I agree with you that the "average person" meets the 3 specific criteria you list (which I don't), I don't believe the claim that the typical security training includes specific instruction in how TLDs and domain registration work, at least not in enough detail for a person to be able to follow the discussion we're having here.
  - account42 29d ago
    > The entire ccTLD systems of the UK, China, Germany, France, Japan, and many others would beg to differ. .de doesn't use third level registrations.
    - angoragoats 29d ago
      Yes, you're right, thank you for the correction.
- efreak 29d ago
  My insurance will not send emails to my first@last.family domain. Neither will several other systems. A number of systems flat out refuse to acknowledge that such a tld exists. (Improper assumptions about valid email addresses)
avazhi 1mo ago
> What exactly is non-standard about an ICANN-approved TLD? Uh, 99% of people would assume a .name address is a scam. Hate to break it to you.
- swiftcoder 29d ago
  I mean, we could say much the same of any other non-country TLD, and probably half the country TLDs. That doesn’t mean one shouldn’t expect it to be administered responsibly
zamadatix 29d ago
Non-standard as in "it's not up to my usual standards" not "is not part of a technical standard". I.e. it's a gTLD rather than a "standard" (in the previous sense) TLD.

jawns 1mo ago

I have a .science domain and a .com domain. Even though .science was launched in 2014 (more than a decade ago), I still consider it a non-standard TLD and still deal regularly with difficulties around its use. (For instance, you wouldn't believe how many online services reject email addresses than end in .science because they use regexes that exclude TLDs with 7 letters.) Likewise, I've registered .lol and .fun domains but never would have assumed that just because they're available now, they will be available in perpetuity. In that sense, .name as a third-level TLD is even more non-standard, because the standard way domain registration works is by choosing a single "second level" domain name, then adding subdomains.

angoragoats 1mo ago
> Likewise, I've registered .lol and .fun domains but never would have assumed that just because they're available now, they will be available in perpetuity. Why wouldn't you assume this? > the standard way domain registration works is by choosing a single "second level" domain name, then adding subdomains The entire ccTLD systems of the UK, China, Germany, France, Japan, and many others would beg to differ.
- jawns 1mo ago
  I don't think those are comparable, because when you register a .co.uk domain, you are selecting one name that precedes .co.uk, similar to how you register one name that precedes .com. Whereas with .name, you are choosing what appears to be a subdomain, followed by what appears to be a domain name. But under the hood, you do not own all subdomains for that domain name; you own only the combination of first_name.last_name.name.
  - angoragoats 1mo ago
    I'm not sure I understand. How is registering first.last.name not also selecting one name ("first") that precedes last.name, similar to how you register one name that precedes .com? (And yes, I am aware that you can also register last.name by itself, but only if there are no third-level domains using it, so for practical purposes it doesn't change my question above. Plus, when the OP originally purchased his domain, you could only buy third-level domains for .name.)
    - jawns 29d ago
      Present these two domain names to the average person: 1) benedict.cumberbatch.name 2) drstrange.co.uk I expect the average person would assume that for the domain 1, .name is the TLD, cumberbatch.name is registered by a private entity, and benedict (and any other subdomains associated with cumberbatch.name) is a subdomain fully controlled by that private entity. Whereas for domain 2, I think the average person will view ".co.uk" the same way they view ".com", even though technically it is both a ccTLD and a second-level domain.
      - swiftcoder 29d ago
        Luckily the average person has no idea what a TLD or a subdomain are
        account42 29d ago
        They do if they are employed in a non-tiny company where they work at least partially on a computer and paid attention during security training.
        angoragoats 29d ago
        Even if I agree with you that the "average person" meets the 3 specific criteria you list (which I don't), I don't believe the claim that the typical security training includes specific instruction in how TLDs and domain registration work, at least not in enough detail for a person to be able to follow the discussion we're having here.
- account42 29d ago
  > The entire ccTLD systems of the UK, China, Germany, France, Japan, and many others would beg to differ. .de doesn't use third level registrations.
  - angoragoats 29d ago
    Yes, you're right, thank you for the correction.
efreak 29d ago
My insurance will not send emails to my first@last.family domain. Neither will several other systems. A number of systems flat out refuse to acknowledge that such a tld exists. (Improper assumptions about valid email addresses)

avazhi 1mo ago

> What exactly is non-standard about an ICANN-approved TLD? Uh, 99% of people would assume a .name address is a scam. Hate to break it to you.

swiftcoder 29d ago
I mean, we could say much the same of any other non-country TLD, and probably half the country TLDs. That doesn’t mean one shouldn’t expect it to be administered responsibly

zamadatix 29d ago

Non-standard as in "it's not up to my usual standards" not "is not part of a technical standard". I.e. it's a gTLD rather than a "standard" (in the previous sense) TLD.