.ins
Is .ins a real TLD? Who’s applying to run it?
Nobody has applied for .ins in its own right, as of 7 October 2026. XYZ Registry named .ins as the backup string of its .point application.
A short insurance-flavored ending with domain-hack appeal, but ambiguous and unlikely to become insurers' default address.
insurance agencies, brokers and insurtech startups wanting a short industry-flavored address, plus domain-hack buyers for English words ending in "-ins" (plug.ins, log.ins, check.ins)
Nobody has applied for .ins in its own right.
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.
Identical bet: a generic name for a single regulated financial vertical whose worth depends on carriers, brokers and agents being willing to move their primary identity onto a category word they share with competitors.
Same vertical, same buyer pool, and the same wager that a short non-brand insurance word becomes the trusted address bar for policy sales and quote funnels.
The clipped-trade-shorthand version of the same bet: an abbreviation an industry already uses in speech, standing in for the full category word, which only works if the trade reads the short form as unambiguous.
What a .ins domain is
.ins is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our Commerce category. Nobody has applied for .ins in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .ins domain extension real yet?
.ins 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 .ins domain?
You can’t yet. A .ins 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 .ins was .insurance, delegated on 3 December 2015.
Is .ins a real TLD?
Not yet. .ins is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .ins as part of an application for another string. Every entry on this page links to its source.
- XYZ Registry · first recordedICANN
“XL2625T-T98505 · XYZ.COM LLC · replacement string of .point”ICANN
- Band chosen: 30-49 (usable but limited). The string reads two ways: as the common abbreviation for insurance, and as a word fragment that enables domain hacks for the many English words ending in -ins. Insurance is a large, high-spend category, so there is a real buyer group, but by analogy the existing insurance-themed endings (.insure, .insurance) have not become primary identities for mainstream insurers, who continue to anchor on legacy namespaces; this is an inference from analogy, with no figures asserted. The applicant on the record is XYZ.COM LLC, which operates a portfolio of generic TLDs with broad registrar distribution; that profile makes wide availability and volume registrations plausible, which supports uptake but not brand signal. It is not in the 50-69 band because adoption of an abbreviation TLD still needs explaining, the string is ambiguous outside the US-style 'ins.' shorthand, and there is no evidence by analogy of a sustained insurance aftermarket on the longer siblings. It is not in the 10-29 band because the three-letter length, a real commercial category behind it, and a genuine domain-hack demand pool (as seen qualitatively with endings like .ing, flagged as analogy) give it more than event-driven or joke demand. Main market uncertainty: whether insurers and insurtechs will treat .ins as a credible industry marker rather than an abbreviation they avoid, versus the TLD settling into a mostly novelty/domain-hack market. The record notes this application is a replacement string for .point; the lifecycle implication is tracked separately and not scored here.