What Is the .jp Domain? Japan's Country-Code TLD Explained
The .jp domain is Japan's ccTLD, run by JPRS. Learn the difference between general-use .jp and .co.jp, the local-presence rule, and who should register.
- tld
The .jp domain is the official country-code top-level domain (ccTLD) for Japan, administered by Japan Registry Services Co., Ltd. (JPRS). What sets .jp apart from many marketed ccTLDs is that it is not one namespace but a small family of them: a flexible general-use tier open to anyone with a Japan address, and a set of tightly restricted attribute-type domains — most famously .co.jp — reserved for entities that can prove Japanese corporate registration. This page walks through both tiers, the local-presence rule that governs all of them, and who genuinely benefits from a .jp name.
.jp at a glance
| Fact | Detail |
|---|---|
| TLD type | Country-code TLD (ccTLD) for Japan |
| Registry operator | Japan Registry Services Co., Ltd. (JPRS) |
| Year delegated | 1986 |
| IDN support | Yes — Japanese-script (Kanji/Hiragana/Katakana) JP domain names are supported alongside ASCII |
| DNSSEC | Supported |
| Registration restrictions | Local-presence required for every JP domain type; .co.jp and other attribute-type domains add category-specific corporate eligibility |
| Best for | Japan-registered businesses (especially via .co.jp as a trust signal), Japan-based individuals and organizations |
What is .jp?
.jp is the ccTLD assigned to Japan under ISO 3166-1 (country code JP), delegated through the IANA root-zone database, which lists JPRS as both registry operator and sponsoring organization. As with any ccTLD, .jp sits under Japanese domain-name policy rather than a standard ICANN registry agreement.
Google does not classify .jp among the small set of ccTLDs it treats as generic (that list — .ad, .ai, .as, .bz, .cc, .cd, .co, .dj, .fm, .io, .la, .me, .ms, .nu, .sc, .sr, .su, .tv, .tk, .ws — is published in Google Search Central's guidance on managing multi-regional sites). .jp is absent from that list, so it functions as a genuine geo-targeting signal for Japan.
History of .jp
.jp was proposed for delegation in 1986, one of the earlier ccTLDs in the DNS root. Its most consequential structural feature has been in place from early on: JPRS (and its predecessor administrators) split the namespace into general-use JP domains and attribute-type / organizational-type JP domains, rather than opening the flat second level to everyone the way many ccTLDs do.
- General-use JP domains (
example.jp) let any eligible registrant — individual, group, or organization with a permanent Japan postal address — register, with no limit on how many names one registrant can hold. - Attribute-type domains — .co.jp (companies), .or.jp (nonprofits), .ne.jp (network service providers), .ac.jp (educational institutions), .go.jp (government agencies), and .lg.jp (local authorities) — each carry category-specific eligibility and, for most categories, a one-domain-per-entity limit. That cap is deliberate: JPRS's own .JP Q&A and Guide to JP Domain Name frame it as preventing any single company from cornering multiple .co.jp names.
- .co.jp eligibility explicitly extends to qualifying foreign companies — a non-Japanese corporation registered in Japan as a Gaikoku Kaisha (foreign company) may apply for a .co.jp name, per JPRS's published guide.
How people use .jp
- Japanese corporations, via .co.jp, where the domain type itself functions as a public proof-of-registration signal — you cannot get one without a real Japanese company behind it.
- Japan-based individuals, groups, and organizations, via general-use .jp, for a flexible, multi-name-capable option.
- Nonprofits, ISPs, schools, and government bodies, via their respective attribute-type domains (.or.jp, .ne.jp, .ac.jp, .go.jp, .lg.jp).
- Brands wanting a native Japanese-script address, since JP domains support Japanese-script registrations alongside ASCII.
Who it's not ideal for: anyone without a permanent Japan postal address — every JP domain type requires local presence — and companies chasing multiple co.jp-style names under one entity, since the one-per-registrant cap blocks that.
Notable sites using .jp
- sony.co.jp — Sony Corporation's official corporate site, using the .co.jp attribute-type domain as its primary Japanese-market address.
- toyota.co.jp — Toyota Motor Corporation's Japan domain, which forwards visitors to Toyota's global corporate site, illustrating how legacy .co.jp registrations remain live entry points even as global brand sites consolidate elsewhere.
.jp vs other domains
| Factor | .jp | .com | .co.jp (JP attribute type) |
|---|---|---|---|
| Type | ccTLD, general-use tier | Legacy gTLD | ccTLD, restricted attribute type |
| Eligibility | Japan postal address required | Open, no restriction | Japan-registered corporation only, one per company |
| Geo signal to Google | Japan-targeted | Generic | Japan-targeted |
| Names per registrant | Unlimited | Unlimited | One |
Choose .com for a globally neutral default with no eligibility hurdles. Choose general-use .jp when you have a genuine Japan presence and want flexibility across multiple names. Choose .co.jp specifically when you want the strongest possible "this is a real, registered Japanese company" signal and only need one name.
Why choose .jp?
- Strong trust signal via .co.jp. Because eligibility is verified against actual corporate registration, a .co.jp address tells Japanese customers your company is legally real.
- Flexible general-use tier. Anyone with a Japan address can register multiple general-use .jp names without the attribute-type restrictions.
- Native-script support. Japanese-script JP domains let brands run an address in Kanji, Hiragana, or Katakana alongside the ASCII form.
- Long-established namespace. Delegated in 1986 and structured deliberately for decades, .jp carries institutional legitimacy in the Japanese market.
Things to consider
- Local presence is required for every JP domain type. There is no anywhere-in-the-world registration path — a permanent Japan postal address (or, for .co.jp, Japanese corporate registration) is mandatory.
- One .co.jp per company. If you need multiple Japan-facing brand names, general-use .jp — not .co.jp — is the option that scales.
- Geo-targeted, not global. Search engines read .jp as Japan-specific, which is a constraint for sites chasing an international audience.
- Documentation-heavy for .co.jp. Proving eligibility typically requires a Japanese certificate of incorporation (tokibotohon) with details like incorporation date, address, and representative director.
Who can register a .jp domain?
Registration restrictions: local presence required. Per JPRS's own .JP Q&A and Guide to JP Domain Name, any individual, group, or organization with a permanent postal address in Japan is eligible for general-use .jp domains, with no cap on how many names one registrant can hold. Attribute-type domains layer on category-specific rules — .co.jp requires a corporation registered under the laws of Japan (including qualifying Gaikoku Kaisha foreign companies), limited to one .co.jp name per company, while .or.jp, .ne.jp, .ac.jp, .go.jp, and .lg.jp each serve their own defined category of registrant.
DNSSEC is supported, and JPRS's registrar network handles the identity and eligibility checks at the point of registration. Because .jp is a nationally governed ccTLD, JPRS's own policy pages are the authoritative source for current eligibility — there is no ICANN registry agreement to consult, as ccTLDs sit outside that system.
.jp pricing and value
.jp pricing follows general-ccTLD dynamics rather than a fixed number: first-year and renewal pricing commonly differ, and attribute-type domains such as .co.jp typically carry different (often higher) pricing than general-use .jp, reflecting the extra eligibility verification involved. Short, dictionary-word, or high-demand general-use .jp names may also carry premium pricing. This page intentionally quotes no specific figures — check current rates at the point of registration.
Reputation and email deliverability
.jp carries a solid, institutionally credible reputation, reinforced by its local-presence and corporate-verification rules — the eligibility bar itself limits the throwaway-registration abuse pattern seen on some unrestricted new gTLDs. For email deliverability, the extension itself is rarely the deciding factor; proper SPF, DKIM, and DMARC configuration matters far more than the TLD. The main practical consideration is audience fit: a .jp or .co.jp address reads as distinctly Japan-facing, which is reassuring to Japanese recipients but may read as narrower to an international correspondent.
Branding and naming tips
- Match the domain type to your entity. A registered company aiming for maximum local trust should use .co.jp; anyone without corporate registration should use general-use .jp instead.
- Confirm eligibility before you fall in love with a name. Local-presence and corporate-registration checks happen at registration time — verify you qualify first.
- Consider a native-script name. Japanese-script JP domains can strengthen recall and trust with a Japan-based audience.
- Plan for one .co.jp only. If your company operates multiple Japan-facing brands, general-use .jp is the workaround for names beyond the single .co.jp slot.
How to register a .jp domain
- Confirm eligibility — a permanent Japan postal address for general-use .jp, or Japanese corporate registration for .co.jp.
- Search for your desired name across the JP domain type that fits your entity.
- Register and complete JPRS's eligibility verification.
- Configure DNS to point your site or email.
Frequently asked questions
Can anyone register a .jp domain?
No. All .jp domain types, including general-use .jp, require the registrant to have a permanent postal address in Japan. Attribute-type domains such as .co.jp add a further requirement — the registrant must be a corporation legally registered in Japan, including a foreign company registered there as a Gaikoku Kaisha.
What is the difference between general-use .jp and .co.jp?
General-use .jp (e.g. example.jp) is open to any individual, group, or organization with a permanent postal address in Japan, and one registrant can hold multiple names. Attribute-type domains like .co.jp are restricted by category — .co.jp requires a Japan-registered corporation and limits each company to one .co.jp name.
Does a .jp domain affect SEO?
Google treats .jp as a country-targeted ccTLD for Japan, not a generic extension, so it signals to search engines that a site is meant for a Japanese audience. That helps Japan-focused sites rank locally but works against sites built for a global audience.
Who runs the .jp domain?
Japan Registry Services Co., Ltd. (JPRS) is the registry operator for .jp, listed in the IANA root-zone database as both the registry operator and sponsoring organization, and it sets the eligibility and registration rules for every JP domain type.
Related resources
- What is a TLD?
- ccTLD market share by registration volume
- Domain terminology guide
- Domain hacks explained
- Glossary: ccTLD, IDN, registrar, ICANN, DNSSEC
- Compare TLDs: .com, .cn, .kr, .in
Sources and further reading
- IANA — Japan Registry Services Co., Ltd. (JPRS)
- Google Search Central — Google Search Central's guidance on managing multi-regional sites
- jprs.co.jp — .JP Q&A
- jprs.co.jp — Guide to JP Domain Name
- sony.co.jp — sony.co.jp
- toyota.co.jp — toyota.co.jp
Related keywords
- JPRS registry
- .co.jp company requirement
- general-use .jp vs .co.jp
- Japan local presence domain
- attribute-type JP domain
- what is .jp
- .jp domain
- .jp TLD
Contributors
Aileen Wright is a student in her twenties living in New York City, where the distance between a museum wall and a library reading room is a short walk and a long afternoon. She came to name writing through art and history — the way a single portrait, coin, or manuscript margin can carry a name across centuries and change its meaning on the way.
Most weeks you can find her in Central Park with a paperback, or in the quiet of a public reading room chasing down where a name actually comes from rather than what a name-list says it means. She is also teaching herself to code, which has made her oddly precise about spelling, sorting, and the small details that decide whether a name ages well.
For Namefi she writes about the history and culture behind domain names, the stories brands carry as they rename, and the difference between a good story and a verified source.
Victor Zhou is a technology founder and standards editor focused on digital identity and trust. He founded Namefi, edits Ethereum Improvement Proposals, and previously led smart-contract architecture work at Google Labs.
His work sits at the intersection of naming, ownership, and the systems people use to establish identity online. That perspective makes him especially interested in the way names move between personal meaning, public recognition, and digital infrastructure.
For Namefi, Victor edits and writes about domains as durable digital identity: how names become ownable onchain assets, how tokenization changes custody and trust, and what naming can learn from the systems people use to establish identity online.