.shield
Is .shield a real TLD? Who’s applying to run it?
.shield is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Identity Digital. XYZ named .shield as a backup string for its .nut application. ICANN deactivated it, because another applicant applied for the same string or named it as a backup.
A protective-sounding word for security and insurance products, but most buyers will still prefer .com for the main brand.
cybersecurity vendors, antivirus and VPN products, insurance and warranty brands, and privacy-protection services wanting a defensive word in the address
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .nut application, shown as deactivated: another applicant applied for the same string or named it as a backup
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: an ownerless English noun for being kept from harm, open to any security, insurance or safety operator willing to put its promise rather than its company name at the top of its address.
Same bet in the same register - one short everyday word that reads as a reassurance rather than an industry label, so it only pays off if buyers will build a primary identity on a claim instead of a category.
Also a protection-promise word aimed at the same trust-selling buyer, but it is a state rather than a concrete object, so it pulls toward being a suffix on someone else's brand instead of a standalone identity.
What a .shield domain is
.shield 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 .shield domain extension real yet?
.shield 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 .shield domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .shield name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .shield was .protection, delegated on 13 September 2015.
Is .shield a real TLD?
Not yet. .shield is not in the DNS root, so nothing resolves under it. It’s here because .shield is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Band chosen: usable but limited (30-49). The string is a plain English noun with a clear protective meaning, which gives it genuine use in cybersecurity, antivirus, VPN, fraud-prevention, insurance and warranty branding, and as a suffix hack (data.shield, cyber.shield, email.shield). It is not in the strong-niche band (50-69) because, reasoning by analogy, protection-themed generics such as .security, .protection and .insure have in my judgement produced modest registration bases and thin resale markets, with security companies continuing to anchor their primary identity on .com and treating these strings as defensive or campaign names; .shield seems likely to follow that pattern over the next 5 years rather than become the default home of a category. It is not in the vanity band (10-29) because the word is a real product noun with ongoing commercial demand across more than one industry (tech, insurance, consumer protection), so registrations should be steady rather than event-driven, and some operators would plausibly run a product landing page on it. The record shows a single confirmed standard application from Identity Digital (legal name Mythic Link, LLC) and a deactivated application from XYZ (XYZ.COM LLC), which suggests an operator with an existing generic-TLD portfolio would run it; that informs adoption likelihood neutrally — a portfolio operator can place it widely at registrars, but it also means the string will compete for attention with sibling protection-themed TLDs. Main market uncertainty: whether security and insurance brands adopt a themed TLD as a primary identity at all, or whether, as with the analogous strings above, uptake stays at the defensive-registration and side-project level. Exact registration counts and pricing for any analogous TLD are unknown to me under the rules here.