.snowflake
Is .snowflake a real TLD? Who’s applying to run it?
.snowflake is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Snowflake Inc..
A single-company brand extension: useful to Snowflake itself for trusted addresses, but nobody else can buy in.
the applicant brand itself, Snowflake Inc., for its product, documentation and customer-account surfaces; no third-party buyer group exists for a closed brand string
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 enterprise data-platform company whose entire name is an ordinary English noun with a prior meaning, buying a single-registrant namespace that only works if the corporate brand outweighs the dictionary word for everyone who types it.
Same bet: a cloud software vendor putting its primary identity on a short, plain everyday noun with no descriptive link to the product, so the string carries zero category traffic value and succeeds only as a closed brand namespace.
Same bet in shape — a cloud data platform claiming a common word (here a colour) as a vendor-controlled namespace — but it is a product-line name sitting under a parent corporate brand rather than the company's own name, so the identity load on the string is lighter.
What a .snowflake domain is
.snowflake 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 .snowflake domain extension real yet?
.snowflake 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 .snowflake domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .snowflake name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .snowflake was .oracle, delegated on 3 March 2015.
Is .snowflake a real TLD?
Not yet. .snowflake is not in the DNS root, so nothing resolves under it. It’s here because .snowflake is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Snowflake Inc. · first recordedICANN
- Band chosen: vanity/joke/narrow (10-29), at its upper edge. The verified facts record a single confirmed application from Snowflake Inc. of ICANN application type brand, with no contention. A brand-type TLD is by design closed to the public: the only registrant is the applicant, so there is no aftermarket and resale strength is structurally absent. What remains is end-use utility to one organization. A data-cloud company could plausibly route customer accounts, documentation, or trust-critical surfaces under its own extension, which carries anti-spoofing and credibility benefits for that single owner. It is not in the band above (usable but limited, 30-49) because that band presumes registrations by many parties at volume or on price; a closed brand string has no registrations beyond the owner and cannot form even a thin market. It is not in the band below (no realistic market, 1-9) because one well-resourced buyer with a genuine, specific use exists and the string is a clean, memorable match to a widely recognized product name. By analogy (flagged as analogy, no figures): many brand TLDs from the 2012 round were held defensively or saw minimal public-facing use, while a minority of technology brands adopted theirs for real product or marketing addresses; which path .snowflake takes is unknown. The string is also a common dictionary word, but under a brand application that generic meaning does not open it to generic demand. Main market uncertainty over the next 5 years: whether Snowflake deploys the extension as a customer-facing primary identity (for example account or documentation addresses) or holds it defensively with its existing domains unchanged.