.OR.JP

Name: .OR.JP — TLD-Wissensdatenbank
Creator: JPRS

Japan

JPRS · SubTLD · Aktualisiert 2026-04-09

ConditionalIDN

Technische Daten

Zone: or.jp
Registrierung: Manual
Laufzeit: 1 year
Zeichenlänge: 3 - 63
IDN: Ja
IPv6: Ja
Nameserver: 2 - 8
Transferdauer: 2-step
AuthInfo-Format: Standard EPP
Redemption-Phase: Standard
Handle-Aktualisierung: Ja
Treuhandservice: Ja
WHOIS-Datenschutz: Teilweise
WHOIS-Aktualisierung: Standard
WHOIS-Server: whois.jprs.jp
Anbindung: Direct
Datensatz: ccTLD

Berechtigung & Einschränkungen

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.

Registrierung

1-2 years. Local presence service widely used by non-Japanese registrants.

Transferverfahren

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.

Inhaberwechsel

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.

Verlängerung & Löschung

Standard.

📘 ICANN ERRP — See ICANN ERRP for the standard gTLD expiry lifecycle (Auto-Renew Grace → RGP → Pending Delete → Released).

Wiederherstellung / RGP

Grace period exists. Drop-catching services available for expired .JP domains.

📘 ICANN ERRP — See ICANN ERRP for RGP details and standard restore fees.

WHOIS / Datenschutz

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-Konformität

N/A. Japan not subject to EU NIS2.

📘 NIS2 Compliance — See NIS2 Compliance for Article 28 requirements, registry implementation status, and operational impact.

Bekannte Fehlercodes & Hinweise

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.or.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.or.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.or.jp/_authinfo1

Standard EPP. Two-stage process.

Domain Restore

POST https://api.autodns.com/v1/domain/example.or.jp/_restore