.cloudflare
Is .cloudflare a real TLD? Who’s applying to run it?
.cloudflare is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Cloudflare, Inc..
A company-name TLD: useful to Cloudflare for its own web addresses, with no market for anyone else to buy into.
the applicant company itself and its product teams, for first-party addresses such as dashboards, docs and service endpoints; not an open namespace for outside buyers
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: the corporate name of an internet-infrastructure company that sells plumbing (DNS, routing, resolution) to other businesses rather than to consumers, betting that its own brand is the credible identity for that layer of the network.
Same bet: a coined corporate name belonging to a B2B network/DNS-services vendor whose buyers are technical operators, so the string only works as the company's own identity and carries no meaning to anyone else.
Same shape of bet — a networking-infrastructure vendor's corporate name as its primary identity — but Cisco is a hardware incumbent with mass brand recognition, where Cloudflare's string leans on developer-channel recognition instead.
What a .cloudflare domain is
.cloudflare 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 .cloudflare domain extension real yet?
.cloudflare 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 .cloudflare domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .cloudflare name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .cloudflare was .verisign, delegated on 25 November 2015.
Is .cloudflare a real TLD?
Not yet. .cloudflare is not in the DNS root, so nothing resolves under it. It’s here because .cloudflare is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Cloudflare, Inc. · first recordedICANN
- Band chosen: 1-9 (no realistic market), at its top. The string is a company name, and the verified facts record one confirmed application from Cloudflare, Inc. with no contention, so this is a dot-brand pattern: addresses would be allocated by the brand for its own use rather than sold. By analogy (flagged as analogy) with earlier-round dot-brands, outcomes split between brands that put the TLD to visible use for official properties and brands that held the string without publicly using it, and in neither case did an aftermarket or third-party demand develop, because outside buyers cannot register. It is not in the 10-29 band because that band assumes some open, if shallow, demand from outside buyers, which a closed brand namespace lacks by design. It is not below the top of its band because the applicant operates DNS, CDN and registrar infrastructure, which makes meaningful first-party use (service endpoints, product subdomains, trust-anchored official addresses) more plausible than for a non-technical brand (analogy, unverified). Main market uncertainty: whether the operator uses the TLD as a public-facing identity for its products or keeps it as a defensive or internal namespace; the score reflects buyer value as an address market, which is effectively one buyer either way.