.fastly
Is .fastly a real TLD? Who’s applying to run it?
.fastly is not contested. One application for it is on ICANN’s Reveal Day list, as of 7 October 2026. It is Fastly, Inc..
A single-company brand domain: useful only to Fastly itself, with no open registrations or resale market expected.
the applicant company and its own products, services and customer-facing infrastructure; not open to third-party registrants
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 coined corporate trademark of a pure internet-infrastructure vendor, where the string is only as meaningful as the company's name is to the technical buyers it sells invisible plumbing to.
Also an invented, opaque vendor mark from the internet-infrastructure-services trade, betting that a B2B supplier of network machinery can anchor its entire corporate identity on its own name.
A coined compound owned by a B2B infrastructure operator selling capacity to other companies rather than to consumers; the same kind of bet, though the construction is semi-descriptive rather than a fully opaque startup mark.
What a .fastly domain is
.fastly 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 .fastly domain extension real yet?
.fastly 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 .fastly domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .fastly name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .fastly was .verisign, delegated on 25 November 2015.
Is .fastly a real TLD?
Not yet. .fastly is not in the DNS root, so nothing resolves under it. It’s here because .fastly is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Fastly, Inc. · first recordedICANN
- Band chosen: 10-29 (vanity/narrow). The string is a company name, and the record shows a single confirmed applicant, Fastly, Inc., with no contention, which is the standard shape of a closed dot-brand: addresses would be allocated by the operator to itself, so there is no open registration volume and no aftermarket. It is not in the 30-49 band because that band assumes registrations happening at volume or on price by outside buyers, which a dot-brand by construction does not offer. It is not in the 1-9 band because the operator is an edge/CDN company and, by analogy to other technology dot-brands from the earlier round (some of which were used for product and corporate hostnames while many stayed dormant; this is analogy, not a recorded fact), a namespace under its own name has plausible real end-use as an operational identity for products, documentation, or customer-facing edge hostnames, where a short, memorable, brand-controlled suffix carries some credibility. Main market uncertainty: whether the operator uses the namespace actively for customer-facing or product addresses, which would give it meaningful day-to-day utility, or treats it as a defensive or marketing-only asset like most dot-brands, which would leave it close to inert. Counts, prices and usage figures for comparable dot-brands: unknown.