.jobs domains are generally available through current registrar checkout pages, including to individuals and organizations. That is not the whole rule. .jobs remains a sponsored top-level domain for employment content, company-name registrations retain special contract language, and registrants agree to registry and professional-use policies.
The safe answer is therefore: a buyer can usually search and register an available .jobs label today, but must confirm that the exact name is released, the registrant has permission to use it, the planned site is genuinely employment-related, and the selected registrar accepts the application.
| Check | Current evidence |
|---|---|
| General availability | Registry site says general availability is live; Porkbun says names are generally available |
| Registrant types | 101domain says individuals and businesses can register |
| Company-name labels | ICANN contract ties these to the employer's legal or commonly known name and registrant entity |
| Other labels | Contract permits occupational and certain geographic names through defined allocation routes |
| Use | Registry presents .jobs for organizational employment content |
1) Read “generally available” carefully
The current Porkbun %%EDITORIAL_0%% page says .jobs names are generally available and that registrants agree to the SHRM Code of Professional Ethics. The official registry FAQ says general availability is live and lets buyers search through the registry site or participating registrars. 101domain's current technical page says both individuals and businesses can register and that no additional documents are ordinarily required.
Those pages are stronger evidence of the present retail path than an old summary that says every applicant must be an internal HR manager. However, “generally available” does not mean every label, use, or ownership claim is permitted. A name may be reserved, allocated under a special program, blocked by rights, already registered, or rejected by the registry or registrar.
Before checkout, capture the live availability result, provider rules, registrant identity, planned use, ordinary renewal, and any warning shown for the exact label. Do not infer permission from a third-party availability widget alone.
2) Account for the sponsored namespace
IANA's %%EDITORIAL_0%% record classifies the extension as a sponsored TLD and identifies Employ Media LLC as the sponsoring organization. It records registration on 8 September 2005 and a last update on 28 January 2025.
A sponsored TLD is organized around a defined community or purpose. The current registry site describes .jobs as the space for organizational employment content, employer brands, career sites, and recruiting campaigns. That context should shape the site even when checkout is open.
A personal project, unrelated product, general company homepage, investment page, parked advertising page, or resale-only registration may be a poor fit. Ask the registrar or registry for a written answer when the planned use sits outside recruiting, employment information, employer branding, job listings, or candidate navigation.
Registration does not verify an employer, vacancy, recruiter, or job offer. Candidates still need to confirm the organization and application destination independently.
3) Fix the registrant
The registrant is the domain holder. For an employer career site, the employer entity should normally control the name through an institutional account, even when an agency, recruiter, registrar, or HR technology provider helps with implementation.
Record:
- the exact employer or operating entity;
- its legal and commonly known names;
- the employee authorized to approve the domain;
- registrar account administrators;
- legal, HR, security, and web owners;
- renewal and recovery contacts; and
- the approved role of every vendor.
Do not let an agency register the employer's core label in the agency's own identity without an explicit, reviewed ownership structure. Vendor contracts should cover access, transfer, termination, recovery, data, and continuity.
An independent job board can also register a generally available name, subject to the exact label and policies. It should identify the operator clearly and avoid looking like the official career site of an employer it does not represent.
4) Classify the label
The current ICANN amendment distinguishes “company name” registrations from other names.
For a company-name registration, the contract describes labels based on the employer's legal name, a name or abbreviation by which it is commonly known, or a name that includes one of those forms. It also says the application must come from a qualified applicant and the registrant must be the entity identified by that trade or commonly known name.
The same amendment permits other types of names, including occupational and certain geographic identifiers, through allocation processes controlled by the registry. A later general-availability release can make an acronym, keyword, or dictionary label searchable without turning it into the buyer's employer identity.
Classify the candidate before buying:
| Label type | Main question |
|---|---|
| Employer name | Does the registrant own or commonly use this identity? |
| Employer plus market | Does the combined label still identify the employer accurately? |
| Occupation | Has the registry released it, and will the site represent jobs without misleading ownership claims? |
| Geography | Is it released, and will the operator explain coverage and listing sources? |
| Generic campaign | Is the purpose genuinely employment-related and free of rights conflicts? |
Use bulk search to compare complete candidates, then verify each shortlisted label with the chosen .jobs registrar.
5) Screen rights and impersonation risk
Availability does not grant trademark rights or permission to impersonate an employer. Search company records, trademark databases, established domains, app stores, recruiting profiles, and social accounts before purchase.
For an employer-name label, confirm that the registrant entity owns or is authorized to use the brand. For a generic or occupational label, check whether the presentation could falsely imply that the site is an official industry body, public service, regulator, or employer.
Candidate trust requires visible evidence:
- operator legal name and contact details;
- relationship to any named employer;
- vacancy source and update time;
- application destination before the user submits data;
- privacy and data-use information;
- fee and recruitment-scam warnings; and
- a clear reporting route.
A .jobs suffix is not an identity check. Do not write “verified employer” unless a separate, current process supports that exact claim.
Use the WHOIS lookup to inspect registrar and registry data, but confirm the employer through its own official records and established channels.
6) Define the employment use
The strongest uses are focused career destinations: an employer's vacancies, a hiring campaign, a regional recruiting portal, an occupational job board, or a protected redirect to an official applicant-tracking system.
Write a one-sentence purpose before implementation. For example: “brand.jobs is the canonical index of roles offered by Brand Group and routes each application to the group's named applicant system.”
Then decide what the site must contain:
- current openings and honest availability states;
- employer identity and locations;
- role requirements, compensation disclosures where required, and application steps;
- accessibility and accommodation information;
- candidate privacy notice;
- scam and fee warnings;
- application-system ownership; and
- contact and complaint paths.
Do not fill a thin domain with copied job descriptions, stale vacancies, or generic employment advice merely to justify the ending. A redirect can be better than a neglected standalone site when the canonical career experience already works elsewhere.
7) Compare a separate domain with a subdomain
A .jobs domain creates a concise employment-specific address. A route such as example.com/careers or a subdomain such as careers.example.com keeps recruiting visibly under the established corporate domain.
| Architecture | Strongest case | Main cost |
|---|---|---|
brand.jobs primary | A distinct, maintained employer career experience | Separate domain operations and candidate education |
brand.jobs redirect | Memorable campaign or defensive route | Redirect governance and continued renewal |
careers.brand.com | Trust transfer from the main corporate identity | Longer address and shared platform constraints |
brand.com/careers | Simple consolidation under one site | Less separation for recruiting operations |
Do not choose based on an assumed SEO boost. Google's search FAQ says the TLD does not determine search performance. Content quality, crawlability, stable URLs, links, implementation, and reputation still do the work.
Read domain basics before assigning separate registrar, DNS, certificate, web, and email owners.
8) Price the full term
On 16 August 2026, two official registrar pages displayed materially different standard .jobs prices in USD:
| Registrar | Register | Renew | Transfer | Three-year path |
|---|---|---|---|---|
| Porkbun | $101.64 | $101.64 | $99.19 | $304.92 |
| 101domain | $188.99 | $220.99 | $188.99 | $630.97 calculated |
Porkbun's three-year path is 3 × $101.64 = $304.92. The 101domain path is $188.99 + (2 × $220.99) = $630.97. 101domain also displayed a $0.18 annual ICANN fee and no private-registration service.
These observations do not establish a universal price. Taxes, currency, premium or reserved labels, registry programs, checkout terms, provider services, and future prices can change. Verify the exact label and ordinary renewal immediately before approval.
Budget for domain operations, DNS, certificates, redirects, applicant tracking, privacy review, accessibility, monitoring, vendor work, defensive names, and renewal ownership. The lowest registration price can be irrelevant if the application journey is unreliable.
9) Build a safe candidate journey
Job scams often imitate known employers, move candidates to unrelated forms, or request money and sensitive documents. A legitimate .jobs project should reduce ambiguity.
Use HTTPS, protected registrar access, strong authentication, controlled DNS, monitored certificates, and an inventory of every subdomain. Publish the employer or operator identity in text. Show the destination domain before sending a candidate to a third-party applicant system, and explain the vendor relationship.
State what the organization will never request. Provide a reporting address. Monitor lookalike domains and advertisements. Keep job feeds current and close expired roles accurately rather than leaving broken application buttons.
If the domain sends email, configure SPF, DKIM, and DMARC and protect high-risk mailboxes. A short extension does not compensate for weak email authentication or unclear recruitment practices.
10) Register and launch in stages
Use this sequence:
- identify the registrant and authorized buyer;
- classify the proposed label;
- check current registry and registrar rules;
- screen rights and impersonation risk;
- compare the exact registration and renewal path;
- decide primary site, redirect, or campaign role;
- register through a participating provider;
- secure the account, DNS, certificates, and recovery;
- test every listing and application destination; and
- publish identity, privacy, scam, and support information.
For a migration, map every old careers URL to its closest new destination. Keep the old domain controlled, update canonical signals and sitemaps, preserve candidate bookmarks where practical, and monitor crawl and conversion errors.
Use the name generator for wording exploration, not for eligibility, rights, or employer verification.
11) Make the registration decision
Proceed when the exact label is released, the registrant is the correct organization or operator, the use is genuinely employment-related, rights checks are clear, and the team can maintain listings, security, privacy, redirects, applicant handoffs, and renewals.
Pause when a generic or geographic label has unclear allocation status, an agency would own an employer name, the site could be confused with an official employer or public service, or the provider's terms conflict with another source. Ask the registry and registrar about the exact label in writing.
Do not proceed when the goal is impersonation, unrelated content, parking, or a misleading vacancy funnel. General checkout availability does not cure a deceptive use.
.jobs can make the purpose of a career destination immediately legible. Its value comes from accurate ownership, a permitted label, current roles, safe application handoffs, and disciplined operations.