.reply
Is .reply a real TLD? Who’s applying to run it?
.reply is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Reply S.p.A..
A company-owned namespace: a strong everyday word, but only the applicant can use addresses on it, so there is no open market.
the applicant itself and its business units, products and regional offices, as a single-owner namespace for its own web and email identity; not open to outside registrants
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 communication verb/noun that no company can own as primary identity, sold on the premise that messaging and conversational services will hang a functional, self-describing address off it.
Same bet on a one-word interaction primitive whose value depends on being read as an instruction to the visitor rather than as a brand, so demand comes from feature-level and campaign-level uses, not corporate head offices.
Also a response-direction action word betting that organisations will stand up a dedicated address for inbound replies, but it is a longer abstract noun with a narrower, more procedural use case than a short everyday verb.
What a .reply domain is
.reply 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 .reply domain extension real yet?
.reply 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 .reply domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .reply name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .reply was .chat, delegated on 4 February 2015.
Is .reply a real TLD?
Not yet. .reply is not in the DNS root, so nothing resolves under it. It’s here because .reply is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Reply S.p.A. · first recordedICANN
- Band chosen: 10-29 (vanity/narrow). The verified facts show one confirmed application, from Reply S.p.A., filed as a brand type with no contention; a brand-type TLD is a closed namespace in which only the operator and its affiliates register names, so there is no third-party registration volume and no aftermarket, which rules out the 30-49 band (usable but limited, where registrations at least happen at volume or on price). It is not in the 1-9 band because the string is a short, globally understood everyday word with obvious fit for messaging, customer-service and email-style naming, and the operator could plausibly use it as a genuine primary identity for its own products and units, which is real if narrow utility. By analogy (flagged as analogy): brand TLDs from the earlier round split into a minority that migrated their main web presence and email onto the namespace and a majority that stayed lightly used or dormant behind their existing .com, and some were later retired; outcomes depended on internal commitment rather than the string's appeal. If a closed brand TLD is marked as 'in market', the right comparison is other single-owner namespaces, not open generics. Main market uncertainty: whether the operator actually moves its primary identity (main site, email, product names) onto .reply over the next 5 years or keeps it as a defensive holding, which is the difference between the low and high ends of this band.