.recruit
Is .recruit a real TLD? Who’s applying to run it?
Nobody has applied for .recruit in its own right, as of 8 October 2026. XServer named .recruit as a backup string for its .get application. ICANN deactivated it, because another applicant applied for the same string or named it as a backup. XServer named .recruit as a backup string for its .株式会社 application. ICANN deactivated it, because another applicant applied for the same string or named it as a backup. EchoStar named .recruit as a backup string for its .agent application. ICANN deactivated it, because another applicant applied for the same string or named it as a backup.
A hiring-themed name that staffing firms might use for campaign pages, but few would make it their main web address.
staffing agencies, corporate talent-acquisition teams and HR-tech vendors wanting a hiring-specific web address for job campaigns and candidate landing pages
No applications recorded for this TLD yet.
Named on the ICANN gTLD application list, 7 October 2026 as a replacement (backup) string of the applicant's .agent 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 .xn--6oqv20b1zgzxr 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 .get 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.
It is the same bet in another script — a generic hiring-activity word owned as a vertical for staffing firms, job boards and employer hiring sites, winning only if the whole recruitment trade adopts a category suffix rather than a brand.
A plural generic noun for the same employment vertical and the same buyer set (employer hiring portals, recruiters, job marketplaces), betting that the hiring function is a big enough standalone category to pull primary identity off .com.
Same employment-category generic doing the same job, but the singular reads as an individual's own path, so its primary identity skews to candidate-side personal and coaching use rather than the employer/agency side .recruit addresses.
What a .recruit domain is
.recruit is not a TLD yet. It is a string on our record of the ICANN 2026 new gTLD round, filed under Commerce. Nobody has applied for .recruit in its own right. It is named on ICANN’s list as part of an application for another string.
Is the .recruit domain extension real yet?
.recruit 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 .recruit domain?
You can’t yet. ICANN publishes every applied-for string on Reveal Day, 7 October 2026 at 18:00 UTC. A .recruit name can only be registered after that, once the string is delegated and its registry opens. Last round's closest parallel to .recruit was .xn--otu796d, delegated on 24 January 2018.
Is .recruit a real TLD?
Not yet. .recruit is not in the DNS root, so nothing resolves under it. It’s here because ICANN’s list names .recruit as part of an application for another string. Every entry on this page links to its source.
“EDCL2689T-T94739 · ECHO Domain Co L.L.C. · replacement string of .agent · Deactivated XI2694T-T39173 · XRegistry Incorporated · replacement string of .xn--6oqv20b1zgzxr · Deactivated XI2694T-T41185 · XRegistry Incorporated · replacement string of .get · Deactivated”ICANN
“EDCL2689T-T18315 · ECHO Domain Co L.L.C. · primary · contention set 2026-29 VTL2632T-T80905 · Velvet Taupe, LLC · primary · contention set 2026-29”ICANN
- Band chosen: 30-49 (usable but limited). The string names a real, large vertical - recruiting and staffing - so there is a plausible pool of registrants: agencies, in-house talent teams and HR-software vendors buying a name for a careers portal or a hiring campaign. By analogy (flagged as analogy), the existing hiring-themed TLDs .jobs and .careers have found some use but have not become the primary identity of serious recruiting businesses; those firms stay on .com and treat the themed name as a redirect or campaign page. .recruit is also a verb, which makes it awkward as a brand suffix (a company is not 'acme.recruit'), and the word is associated with a well-known corporate name in the staffing industry (from my own knowledge, unverified here), which could blur who the TLD belongs to in buyers' minds. It is not in the 50-69 band because there is no evidence of genuine, sustained primary-identity demand in this vertical - the closest analogues did not produce one. It is not in the 10-29 band because the vertical is real and ongoing, not event-driven or a joke, and volume on price from agencies and HR-tech is plausible over the next 5 years. On the record, both applications for the string are deactivated and were replacement strings for other primaries; this is stated neutrally and is a lifecycle matter, not part of the score. Main market uncertainty: whether recruiting agencies and HR-tech vendors adopt a hiring-specific name for candidate-facing pages at any scale, or whether .jobs and .careers already absorb that thin demand.