.private
Is .private a real TLD? Who’s applying to run it?
.private is contested: 3 applicants have said publicly that they applied to run it, as of 1 September 2026. They are Registered Agents Inc, Endpoint Domains, Inc. and Link Freedom Group.
A niche label for privacy-themed products, but the word cuts both ways: a public address that says 'private' can read as keep-out.
privacy-focused software and service vendors (VPNs, encrypted messaging and email, secure storage), plus discreet-commerce and personal-data products wanting a keyword suffix
In LFG's published list of 300+ strings submitted before the ICANN window closed on 2026-08-12. Their catalog tagline: “Private by design.”
One of eight strings Endpoint Domains, Inc. disclosed as primary applications in the ICANN 2026 round (fully paid, per trade press); the company says more applications will be disclosed later.
One of six 2026-round applications Registered Agents Inc announced in its own press release. Third known applicant on .private, joining two earlier announcements.
The 2012 applications making the most similar bet. Chosen by AI from every string in that round, without being told what happened to any of them.
Same bet: a bare English trust adjective where the string itself is the promise, so the namespace is only worth anything if the registry actually polices the claim rather than selling it to anyone.
Identical structure and buyer — an assurance adjective that no single company owns, sold to security/identity vendors who want the attribute, not a category, as their address.
Also an abstract virtue word whose value depends entirely on enforced eligibility or verification at registration, though it reads as an institutional noun rather than a property of the thing being named.
What a .private domain is
.private is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under AI & tech. 3 applicants have said publicly that they applied for .private.
Is the .private domain extension real yet?
.private is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. It is a string applicants have put forward in the ICANN 2026 new gTLD round, the process that decides whether it becomes one.
When can you buy a .private domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .private name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .private was .secure, delegated on .
Is .private a real TLD?
Not yet. .private is not in the DNS root, so nothing resolves under it. It’s here because an applicant said publicly that it applied for .private in the ICANN 2026 new gTLD round. Every claim on this page links to its source.
- Registered Agents Inc · first recordedRegistered Agents Inc
- Endpoint Domains, Inc. · first recordedDomain Name Wire (Andrew Allemann)
- Link Freedom Group · first recordedLink Freedom Group
“The company has also applied for six new generic top-level domains through ICANN's 2026 New gTLD Program”Registered Agents Inc
“The company says the applications are fully paid.”Domain Name Wire (Andrew Allemann)
“.private · Commerce · “Private by design.””Link Freedom Group
“Each of these is a primary application. Plus additional applications to be revealed.”Endpoint Domains, Inc.
“LFG voluntarily published its full list of submissions ahead of ICANN’s official Reveal Day.”PR Newswire (Link Freedom Group)
“Top level domain registry Link Freedom Group (LFG) has disclosed more than 300 strings submitted as part of the ICANN new top level domain name program.”Domain Name Wire (Andrew Allemann)
- Band chosen: usable but limited (30-49). The privacy market is a real, growing commercial category over the next 5 years, and 'private' is a strong English keyword, so descriptive registrations like vpn.private or mail.private are plausible at volume; that keeps it out of the 10-29 vanity band. It stays below the 50-69 strong-niche band because the string carries a semantic contradiction as a public web identity: an address ending in .private can signal that the destination is closed, internal, or not for the visitor, which undermines primary-identity use for consumer-facing brands. By analogy (flagged as such), adjective and security-adjacent descriptor TLDs have tended to see thin primary-identity adoption and weak aftermarkets, with most value concentrated in a handful of exact-keyword pairings. A further qualitative caution, reasoned by analogy rather than asserted as fact: the word 'private' resembles labels plausibly used inside internal or non-public network naming, and strings with that character can face resolver blocking or enterprise-collision friction that dampens serious adoption, even with delegation assumed. Applicant context, stated neutrally: the applicant is Link Freedom Group, which filed more than 300 strings in the ICANN 2026 round and published its list ahead of Reveal Day (press-corroborated by Domain Name Wire, 2026-08-13); a large-portfolio applicant suggests a volume/registrar-channel strategy rather than a single-string flagship push, which tempers expectations of heavy category marketing. Its catalog files this string under Commerce with the tagline 'Private by design.' Main market uncertainty: whether privacy-sector brands treat the descriptor as a trust-enhancing badge or as a usability liability that confuses mainstream visitors; adoption by even a few visible privacy brands as primary identities would move this string toward the strong-niche band, while their absence leaves it a price-driven keyword registry.