- Home
- TLD Knowledge Base
- .NE.JP
.NE.JP
Japan
JPRS · SubTLD · Updated 2026-04-09
ConditionalIDN
Specifications
- Zone
- ne.jp
- Registration
- Manual
- Registration period
- 1 year
- Character length
- 3 - 63
- IDN
- Yes
- IPv6
- Yes
- Nameservers
- 2 - 8
- Transfer time
- 2-step
- Auth code format
- Standard EPP
- Redemption period
- Standard
- Handle updates
- Yes
- Trustee service
- Yes
- WHOIS privacy
- Partial
- WHOIS update
- Standard
- WHOIS server
- whois.jprs.jp
- Connection
- Direct
- Data set
- ccTLD
Eligibility & Restrictions
Generic .JP: open to anyone; non-Japanese registrants may use local presence service. .CO.JP: Japanese registered companies only (toukibotouhon required; only 1 domain per company). .NE.JP/.GR.JP: local presence required. All contacts must have Japanese address.
.CO.JP: only 1 domain per company. Toukibotouhon (government-issued company registration document) required.
Registration
1-2 years. Local presence service widely used by non-Japanese registrants.
Transfer Procedure
Two-step auth: (1) registrant authorization email from registry; (2) registry sends second request to current registrar. Registrant must notify current registrar before transfer. If local presence service used: must update owner to Japanese address at new registrar BEFORE transfer-out.
Transfer blocked if local presence service active. Must update owner to Japanese address first.
📘 ICANN Transfer Policy (IRTP) — See ICANN Transfer Policy for the full IRTP framework, auth code rules, 60-day lock periods, and TEAC.
Registrant Change
If updated owner address in Japan: name and address updated at registry. If outside Japan: only name, organisation, email updated; address uses local presence service address.
📘 ICANN OwnerChange (COR) — See ICANN OwnerChange for COR triggers, FOA/DA modes, 60-day lock, and opt-out.
Renewal & Deletion
Standard.
📘 ICANN ERRP — See ICANN ERRP for the standard gTLD expiry lifecycle (Auto-Renew Grace → RGP → Pending Delete → Released).
Restore / Redemption Grace Period
Grace period exists. Drop-catching services available for expired .JP domains.
📘 ICANN ERRP — See ICANN ERRP for RGP details and standard restore fees.
WHOIS / Privacy
Owner address not displayed in public WHOIS. IDN supported (Japanese characters).
📘 ICANN Registration Data Policy — See Registration Data Policy for RDP 2025, RDAP, redaction defaults, and privacy/proxy rules.
NIS2 Compliance
N/A. Japan not subject to EU NIS2.
📘 NIS2 Compliance — See NIS2 Compliance for Article 28 requirements, registry implementation status, and operational impact.
Known Error Codes & Notes
- Local presence block: Transfer blocked if local presence service active. Must update owner address first.
- .CO.JP limit: 1 domain per company. Toukibotouhon required within 6 months.
- .NE.JP/.GR.JP: Inkanshoumeisho required; transfers-out require Japan residence + $40 JPRS fee.
API
Domain Create
POST https://api.autodns.com/v1/domain
{ "name": "example.ne.jp", "ownerc": { "id": 23142212 }, "adminc": { "id": 23142212 }, "techc": { "id": 23142212 }, "nameServers": [ { "name": "ns1.example.com" }, { "name": "ns2.example.com" } ], "confirmOrder": false }
⚠ All contacts must have Japanese address. Local presence service widely used.
Domain Transfer
POST https://api.autodns.com/v1/domain/_transfer
{ "name": "example.ne.jp", "auth": "(AUTH_CODE)" }
⚠ Two-step: registrant email + registrar approval. Blocked if local presence active.
Create AuthInfo1
POST https://api.autodns.com/v1/domain/example.ne.jp/_authinfo1
Standard EPP. Two-stage process.
Domain Restore
POST https://api.autodns.com/v1/domain/example.ne.jp/_restore