.sure
Is .sure a real TLD? Who’s applying to run it?
Nobody has applied for .sure in its own right, as of 7 October 2026. Link Freedom Group named .sure as the backup string of its .add application.
A catchy word for slogans and domain hacks like in.sure, but few serious projects would make it their main address.
brand-forward marketers and insurtech startups chasing the in.sure / make.sure style hack, plus lifestyle brands built around confidence and reliability messaging
Nobody has applied for .sure in its own right.
In LFG's published list of 300+ strings submitted before the ICANN window closed on 2026-08-12. Their catalog tagline: “Count on it, every time.”
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 one-syllable everyday adjective whose whole value is the reassurance it asserts, sold to anyone wanting a confidence claim right of the dot rather than to a defined industry.
Another assurance adjective monetized as a promise rather than a category, resting on the same premise that an adjective TLD confers credibility instead of merely describing it.
Same trust-as-inventory wager with the same unresolved question of who is entitled to vouch for whom, though it is a noun with a heavier fiduciary/financial pull than the looser adjectival read of the target.
What a .sure domain is
.sure is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our Brand category. Nobody has applied for .sure in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .sure domain extension real yet?
.sure is not yet a domain extension you can register: nothing resolves under it, and no registrar sells names in it. Nobody has applied for it on the public record; the ICANN 2026 new gTLD round is the process that would decide whether it becomes one.
When can you buy a .sure domain?
You can’t yet. A .sure name can only be registered once the string is delegated (added to the DNS root) and its registry opens. Last round's closest parallel to .sure was .safe, delegated on 5 December 2015.
Is .sure a real TLD?
Not yet. .sure is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .sure as part of an application for another string. Every entry on this page links to its source.
- Link Freedom Group · now replacementICANN
- Link Freedom Group · first recordedLink Freedom Group
“LFGL2683T-T26597 · Link Freedom Group Ltd · replacement string of .add”ICANN
“.sure · Lifestyle · “Count on it, every time.””Link Freedom Group
- Band 10-29 (vanity/narrow). The string is a common English adverb of affirmation, which makes it fun in slogans (make.sure, for.sure) and gives it one genuinely interesting angle: verb-suffix domain hacks aimed at the insurance vertical (in.sure, en.sure, as.sure). By analogy, adverb/affirmation TLDs in earlier rounds (.now, .plus, .best, .win) tended to sell on price and novelty rather than becoming primary identities, and the insurance-specific strings from the 2012 round reportedly saw thin serious adoption relative to the size of the vertical; both are analogies, not verified facts about this string, and specific figures are unknown. It is not in the 30-49 band because there is no obvious volume-registration engine: the word is not a product category, a profession, or a geography, so demand beyond hacks and wordplay looks event-driven and shallow, and the brand signal a .sure address sends to a non-expert is closer to a pun than to credibility. It is not in the 1-9 band because the insurance hack, affirmation-slogan marketing pages, and confidence-themed lifestyle brands form a small but real buyer pool over the next 5 years, and the applicant facts are neutral context: LFG filed more than 300 strings and lists this one under Lifestyle with the tagline 'Count on it, every time.', suggesting a broad-portfolio play rather than a vertical push, which slightly lowers the odds of concentrated category marketing. The main market uncertainty is whether any meaningful slice of insurance and assurance marketing embraces second-level hacks on .sure as primary brands rather than as redirect vanity URLs; primary-brand adoption there could pull the string toward the low 30s, while pure-redirect usage keeps it a novelty namespace.