.protocol
Is .protocol a real TLD? Who’s applying to run it?
.protocol is not contested. One application for it is on ICANN’s Reveal Day list, as of 8 October 2026. It is Link Freedom Group. Identity Digital named .protocol as a backup string for five of its applications: .quantum, .goat, .verified, .merch and .drop. ICANN deactivated those backups, because another applicant applied for the same string or named it as a backup. Radix named .protocol as a backup string for its .firm application. ICANN deactivated it, because another applicant applied for the same string or named it as a backup.
A natural fit for crypto and infrastructure projects that call themselves protocols, but most will likely keep shorter, established endings.
crypto and DeFi teams that brand as 'X Protocol', plus network/standards infrastructure projects and developer-tool startups wanting a technical-sounding identity.
In LFG's published list of 300+ strings submitted before the ICANN window closed on 2026-08-12. Their catalog tagline: “Order in the chaos.”
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .drop application, shown as deactivated: another applicant applied for the same string or named it as a backup
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .firm application, shown as deactivated: another applicant applied for the same string or named it as a backup
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .merch application, shown as deactivated: another applicant applied for the same string or named it as a backup
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .verified application, shown as deactivated: another applicant applied for the same string or named it as a backup
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .goat application, shown as deactivated: another applicant applied for the same string or named it as a backup
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .quantum application, shown as deactivated: another applicant applied for the same string or named it as a backup
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 generic infrastructure noun that technical entities already carry inside their own names ("X Network" / "X Protocol"), so the registry is selling a suffix that completes an identity rather than describing a topic.
Same bet: an abstract engineering-category noun bought by technical organizations as a self-description of what they are, wagering that builders prefer an architectural word over a commercial one.
Same bet on a computing term-of-art whose value depends on one technology movement keeping that word as its badge of identity, which makes it era-bound in the way a category noun like .systems is not.
What a .protocol domain is
.protocol is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, in our Crypto category. One application for it is on ICANN’s Reveal Day list.
Is the .protocol domain extension real yet?
.protocol 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 .protocol domain?
You can’t yet. A .protocol 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 .protocol was .network, delegated on 22 August 2014.
Is .protocol a real TLD?
Not yet. .protocol is not in the DNS root, so nothing resolves under it. It’s here because .protocol is on ICANN’s Reveal Day list of applied-for strings. Every entry on this page links to its source.
- Identity Digital · fact correctedICANN
- Identity Digital · first recordedICANN
- Identity Digital · first recordedICANN
- Identity Digital · first recordedICANN
- Identity Digital · first recordedICANN
- Radix · first recordedICANN
- Identity Digital · first recordedICANN
- Link Freedom Group · now confirmedICANN
- Link Freedom Group · first recordedLink Freedom Group
“BPL2623T-T12779 · Bird Pepper, LLC · replacement string of .drop · Deactivated BPL2623T-T20698 · Bird Pepper, LLC · replacement string of .merch · Deactivated BPL2623T-T25726 · Bird Pepper, LLC · replacement string of .verified · Deactivated BPL2623T-T36536 · Bird Pepper, LLC · replacement string of .goat · Deactivated BPL2623T-T84050 · Bird Pepper, LLC · replacement string of .quantum · Deactivated LFGL2683T-T69712 · Link Freedom Group Ltd · primary RTIS2674T-T42193 · Radix Technologies Inc SEZC · replacement string of .firm · Deactivated”ICANN
“LFGL2683T-T69712 · Link Freedom Group Ltd · primary”ICANN
“.protocol · AI & Tech · “Order in the chaos.””Link Freedom Group
- Band: 30-49, usable but limited. The string maps onto a real naming convention: many crypto, DeFi, and infrastructure projects style themselves as 'X Protocol', so name.protocol reads as a coherent primary identity rather than a gimmick. That keeps it out of the 10-29 vanity band: there is a plausible, identifiable buyer group with genuine end-use intent, not just event-driven registrations. It does not reach the 50-69 strong-niche band because, by analogy with other descriptive multi-syllable tech TLDs (analogy: strings like .network, .systems, .solutions have historically drawn volume registrations but thin aftermarkets and weak brand signal), an eight-letter suffix competes poorly against the short endings the crypto world already treats as defaults, and serious projects in that space tend to hold their identity on an incumbent ending even when they register descriptive alternatives defensively. Applicant context is neutral: the applicant, Link Freedom Group, filed more than 300 strings in the ICANN 2026 round (the largest applicant of the round, per its voluntarily published list, press-corroborated by Domain Name Wire, 2026-08-13) and catalogs this string under 'AI & Tech' with the tagline 'Order in the chaos.'; a large-portfolio applicant suggests broad marketing rather than a single-string bet, which neither raises nor lowers the string's intrinsic fit. Registration volume, pricing, and any comparable-TLD figures: unknown. My main market uncertainty is whether crypto-native teams, the best-fit buyers, will treat a long descriptive suffix as credible primary identity or as a defensive add-on; the answer swings this between the high 30s and mid 50s.