Is .whatsapp a real TLD? Who’s applying to run it?
.whatsapp is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Meta.
A closed brand namespace: only the brand owner can hold addresses here, so there is no market for anyone else to buy into.
the brand owner itself, for its own product links and infrastructure; no outside registrant group
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 exactly: a coined, meaningless-until-used product name belonging to one company's consumer messaging/calling app, where the TLD exists to carry the app's own identity to its own users rather than to sell names to anyone.
A single company's branded consumer messaging product put forward as its primary identity string, with the same requirement for it to work — the product's user base has to be large enough that the word means the app and not its dictionary sense.
Also a standalone coined brand for one company's mass-market consumer social-messaging platform used as its own namespace, but it is a platform identity with public profile pages rather than a private-messaging client's closed app identity.
What a .whatsapp domain is
.whatsapp is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Brand. One application for it is on ICANN’s Reveal Day list.
Is the .whatsapp domain extension real yet?
.whatsapp 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 .whatsapp domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .whatsapp name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .whatsapp was .skype, delegated on 23 June 2015.
Is .whatsapp a real TLD?
Not yet. .whatsapp is not in the DNS root, so nothing resolves under it. It’s here because .whatsapp is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Meta · first recordedICANN
“MRHL2653T-T50358 · Meta Registry Holdings LLC · primary”ICANN
- Band chosen: 1-9, no realistic market. The verified-facts block records one application, by Meta Registry Holdings LLC, with ICANN application type 'brand' (ICANN Reveal Day list, 7 October 2026). A brand-type application, by its nature, restricts registrations to the applicant and its affiliates, so the 'best-fit buyer' of an address here is the brand owner alone; there is no third-party registration channel and therefore no aftermarket, which is what the rubric's higher bands measure. Why not the 10-29 band: even a vanity or joke TLD has some outside registrants and event-driven demand; a closed brand string has none by design, and the brand already carries its identity on existing domains, so the TLD adds credibility only to its owner. Why not lower than 8: by analogy with other closed brand TLDs from the 2012 round (flagged as analogy), a large consumer-messaging brand can plausibly put a brand TLD to real use for short, phishing-resistant links, app deep links, or verified business endpoints, which is genuine end-use utility even if the only user is the applicant; the number of 2012-round brand TLDs that stayed dormant versus those used as primary identity is unknown to me as a figure, and the pattern that most stayed dormant is stated as analogy only. Main market uncertainty: whether the owner uses the string as an outward-facing identity for user-visible links (which would raise end-use utility within this band) or leaves it as a defensive registration, which is the more common outcome by analogy.