.defense
Is .defense a real TLD? Who’s applying to run it?
.defense is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is XYZ.
A descriptive but narrow string: credible for cyber-defense and defense-sector firms, rarely their main web address.
defense contractors, cybersecurity ("cyber defense") vendors and self-defense training or product businesses looking for a descriptive secondary address
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 as .defense: a single abstract sector noun that no one owns, sold to a diffuse protection industry whose credible registrants are institutions and vendors already carrying their own brands, so the string only works if a whole category adopts a category word.
Shares the armed-forces trust territory and the same dependence on perceived legitimacy of the registrant, but the bet differs in kind: it is a named institution's own word (with a commercial generic drag) rather than a sector category covering an industry plus its government buyers.
Structurally the same wager as .defense -- an abstract protective-function noun standing in for a compliance-and-assurance field with no natural owner -- just aimed at civilian occupational buyers instead of the military-industrial side.
What a .defense domain is
.defense is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under AI & tech. One application for it is on ICANN’s Reveal Day list.
Is the .defense domain extension real yet?
.defense 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 .defense domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .defense name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .defense was .security, delegated on 17 September 2015.
Is .defense a real TLD?
Not yet. .defense is not in the DNS root, so nothing resolves under it. It’s here because .defense is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- XYZ · first recordedICANN
- Band chosen: 30-49 (usable but limited), at the bottom of it. The string is a real English word with a clear meaning and three plausible buyer pools (defense industry, cybersecurity marketed as 'cyber defense', and consumer self-defense), so it is more than a joke or vanity string; a small number of cyber-defense startups and consultancies could plausibly use a short name on it as a primary identity. It is not in the 50-69 band because the defense industry is conservative and compliance-driven and tends to anchor on .com, .gov or .mil-style identities, so adoption would need explaining and the aftermarket would be thin. It is not in the 10-29 band because, by analogy (flagged as analogy), the comparable 2012-round strings .security and .protection found a modest but real premium-priced buyer pool in the infosec sector rather than purely event-driven demand, while .army/.navy/.airforce (analogy) showed that military-flavored strings attract little serious primary-identity use. The one recorded applicant is XYZ.COM LLC, status confirmed, with no contention; a registry already operating comparable descriptive strings is more likely to bring this to general availability at retail, which marginally raises adoption likelihood but does not change the demand ceiling. Main market uncertainty: whether cybersecurity vendors treat 'defense' as a core marketing term worth a primary address, or whether the government/military connotation chills commercial use and leaves it a defensive-registration string. Specific registration counts, prices and outcomes for the analog TLDs are unknown here and are not asserted.