.resume
Is .resume a real TLD? Who’s applying to run it?
Nobody has applied for .resume in its own right, as of 7 October 2026. Identity Digital named .resume as the replacement string of its .beta application.
A clear but narrow personal-page address for job seekers; most people keep their resume on LinkedIn or a PDF, so demand stays shallow.
job seekers, freelancers and consultants who want a firstname-lastname.resume personal page, plus resume-builder services and career coaches selling to them
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 on a generic employment-market noun as a destination word, but the registrant skews employer-side (a company's hiring page) rather than the individual job-seeker putting their own credential on it.
Same structural bet as .resume: a mass-market common noun where the site IS the named artifact, sold one-per-person to individuals who want their name plus a word describing the document, with volume rather than a niche as the business case.
Shares the credential-signalling bet — a word an individual attaches to their name to assert hireability — but it is an earned-qualification token with a gated eligible population, not an open document noun anyone can claim.
What a .resume domain is
.resume is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Other. Nobody has applied for .resume in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .resume domain extension real yet?
.resume 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 .resume domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .resume name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .resume was .careers, delegated on 17 December 2013.
Is .resume a real TLD?
Not yet. .resume is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .resume as part of an application for another string. Every entry on this page links to its source.
- Identity Digital · first recordedICANN
“A2619T-T45080 · Berth Order, LLC · replacement string of .beta”ICANN
“A2619T-T60918 · Berth Order, LLC · replacement string of .era · Deactivated A2619T-T68837 · Berth Order, LLC · replacement string of .fest · Deactivated A2619T-T76756 · Berth Order, LLC · replacement string of .get · Deactivated A2619T-T84675 · Berth Order, LLC · replacement string of .list · Deactivated NSL2674T-T61555 · NAME SPACE LLC · primary XL2625T-T87066 · XYZ.COM LLC · replacement string of .cosmetics · Deactivated”ICANN
- Band chosen: 10-29 (vanity/narrow), at its upper edge. The string is an unambiguous English noun with one obvious use: a personal page where someone's CV lives. That use is real but structurally small — the person's primary identity is usually their name on a general-purpose TLD, a LinkedIn profile or a PDF attachment, and a .resume address is a secondary pointer that is cheap to drop once a job is found, which makes demand event-driven and churn-prone. By analogy (flagged as analogy), personal-identity strings such as .name and .bio have tended to settle into modest, promotion-driven registration patterns rather than sustained primary-identity use, while the one personal string that has done better, .me, benefits from being short and flexible rather than tied to a single document type; .resume has the opposite shape — longer and single-purpose. Businesses in the resume space (builders, writers, career coaches) are the natural keyword buyers, but by analogy with other descriptive-noun TLDs they tend to keep their primary identity on a mainstream extension and hold the niche string defensively at best, so the aftermarket is thin. Not the band above (30-49): that band requires registrations at volume or on price with a weak-but-present brand signal; absent a bundle or platform push, there is no evident mechanism by which .resume reaches volume, and a personal CV page rarely earns a serious primary identity. Not the band below (1-9): a realistic, if small, market does exist — the string is memorable, self-explanatory and fits a recurring consumer need. On the record, the single application is from Identity Digital (Berth Order, LLC), filed as a replacement string for its primary .beta application; contention count is 0; that is stated neutrally and bears only on adoption likelihood, which is assumed here. Main market uncertainty: whether personal CV pages become a mainstream habit over the next 5 years (which would lift the string toward usable-but-limited) or stay a fringe of the LinkedIn-and-PDF norm.