.person
Is .person a real TLD? Who’s applying to run it?
.person is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is ULTRAVIEW AG.
A personal-identity address that reads flat; people wanting a personal domain already have better-sounding options.
individuals wanting a personal homepage or profile address, and identity or people-directory services that could bundle one
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.
Both are bare, ungated words for the human individual sold as a place to put a personal identity, so the bet rides entirely on ordinary people adopting a namespace of their own rather than on an industry, community, or company.
A first-person identity declaration aimed at individuals naming themselves - the same self-as-registrant bet as a generic noun for a human, differing only in that it addresses one language's speakers rather than everyone.
Also a plain noun denoting a kind of person, bought by individuals to carry their own identity, but it narrows the buyer to one life role instead of betting that every person wants a personal domain.
What a .person domain is
.person is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Culture. One application for it is on ICANN’s Reveal Day list.
Is the .person domain extension real yet?
.person 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 .person domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .person name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .person was .you, delegated on 25 March 2016.
Is .person a real TLD?
Not yet. .person is not in the DNS root, so nothing resolves under it. It’s here because .person is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- ULTRAVIEW AG · first recordedICANN
- Band chosen: 10-29 (vanity/narrow), at its upper edge. The personal-identity TLD category has a long track record of underperforming its apparent breadth: .name (an early personal-name TLD) saw modest uptake and a thin aftermarket by analogy with how personal-site demand has been served, while .me succeeded largely on word-play that lets the string read as part of a phrase. .person has none of that phrasing advantage: 'firstname.person' or 'jane.person' reads like a label, not a sentence, and the string describes the registrant rather than what they do, which gives it weak brand signal and little category pull (inference from analogy, flagged). It is not in the 30-49 band because I do not expect volume or price-driven registrations at the scale descriptive-noun TLDs like .guru or .ninja briefly achieved; the word is generic enough to mean nothing specific and odd enough to say aloud that serious individuals are unlikely to adopt it as primary identity over .com, .me, .io or a ccTLD. It is not in the 1-9 band because a real, if small, use case exists: personal profile pages, link-in-bio style identity, and possible bundling by a profile or identity service, which could sustain some registrations. On the record, one applicant (ULTRAVIEW AG) holds a confirmed standard application with no contention, and a related .profile application by the same applicant is recorded as deactivated, which suggests a consolidated identity-product angle; a bundled distribution model is the main upside path, but adoption likelihood from that alone is unknown. Main market uncertainty: whether a profile or identity product with real distribution adopts .person as its default address space, which is the one dynamic that could move it into the usable-but-limited band.