Is .pdf a real TLD? Who’s applying to run it?
Nobody has applied for .pdf in its own right, as of 7 October 2026. Intercap named .pdf as the replacement string of its .backup application.
A file-extension name: eye-catching for PDF tools and novelty links, but confusing in links and email and rarely a serious main address.
makers of PDF editing, signing and conversion tools wanting a hack like merge.pdf, plus security researchers and novelty registrants
No applications recorded for this TLD yet.
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 exactly: a three-letter file-extension string for a document interchange format stewarded by one software vendor but used as a universal noun by everyone who handles those files, so the value rests on owning the filetype word rather than a brand or a category.
Also a filetype-extension string that reads as a plain technical verb/format to the whole market, where the registry is betting that anyone whose product touches that format wants the namespace — the difference being no vendor steward behind it.
A file-extension string whose format belongs to a single vendor's ecosystem, so the bet is similar in kind, but it reads more as one company's player format than as a neutral document standard a whole industry would put its identity on.
What a .pdf domain is
.pdf is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under AI & tech. Nobody has applied for .pdf in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .pdf domain extension real yet?
.pdf 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 .pdf domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .pdf name can only be registered after that, once the string is delegated and its registry opens.
Is .pdf a real TLD?
Not yet. .pdf is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .pdf as part of an application for another string. Every entry on this page links to its source.
- Intercap · first recordedICANN
“IRI2679T-T81655 · Intercap Registry Inc. · replacement string of .backup”ICANN
“EDI2665T-T28371 · Endpoint Domains, Inc. · primary IRI2679T-T96997 · Intercap Registry Inc. · replacement string of .wiz · Deactivated NA2626T-T63059 · ShortDot (Ireland) Limited · replacement string of .ask · Deactivated XL2625T-T48604 · XYZ.COM LLC · replacement string of .con · Deactivated”ICANN
- Band chosen: 10-29 (vanity/narrow), at its upper edge. The string is a universally recognised file extension for a document format, so it is memorable and reads naturally in a few hacks (edit.pdf, sign.pdf). But that same recognition is the problem: a bare hostname like invoice.pdf is indistinguishable from a filename in email, chat and auto-linking contexts, which (by analogy to the file-extension TLDs .zip and .mov) triggers phishing concern, filtering by some mail and security products, and advice from security teams to avoid it. By analogy, those file-extension TLDs saw a launch burst of defensive, novelty and research registrations rather than sustained primary-identity use, and their aftermarket stayed thin. It is not in the 30-49 band because demand is likely event-driven around launch rather than steady volume, and the brand signal is negative for anyone outside the PDF-tool niche. It is not in the 1-9 band because a real, sizeable category of PDF-tool vendors exists and a handful of them could plausibly adopt a .pdf address as a marketing front door, and novelty demand is genuine. Applicant facts (neutral, from the record): Intercap Registry Inc. holds the application as a replacement string for .backup, standard type, with no contention recorded. Main market uncertainty: whether a meaningful number of PDF-tool and document-workflow companies treat .pdf as a primary identity rather than a redirect, versus the string being confined to curiosity and defensive registrations.