.jp SLA Compliance

TLD SLA Compliance Metrics

Spec 10

DNS

Period	Availability	RTT Compliance	RTT p50	RTT p95	Checks
24h	100%	100%	85ms	162ms	256
7d	100%	100%	90ms	174ms	1440
30d	100%	100%	94ms	273ms	4880

WHOIS

Period	Availability	RTT Compliance	RTT p50	RTT p95	Checks
24h	100%	100%	285ms	302ms	40
7d	100%	99.58%	286ms	443ms	240
30d	99.76%	99.39%	286ms	466ms	824

EPP *

Period	Availability	RTT Compliance	RTT p50	RTT p95	Checks
24h	100%	100%	44ms	50ms	10
7d	100%	100%	44ms	48ms	60
30d	100%	100%	44ms	48ms	204

DNSSEC Validation Metrics

Registry Agreement Spec 6

DNSSEC is required by the Registry Agreement (Specification 6) but is not part of the Spec 10 SLA. We monitor DNSSEC validation independently.

Period	Validation Rate	RTT p50	RTT p95	Checks
24h	No data available
7d	No data available
30d	100%	140ms	165ms	528

Unlike Spec 10 services, DNSSEC has no formal availability SLA. Thresholds shown are operational guidelines.

Current Check Status

Reported by Any53 Probes

Type	AF	RTT	Last Check	Source	Details	Status
`DNS`	v4	53ms	20 minutes ago	local	NSID: app12.lax1.hosts.meta.r…	OK
`DNS`	v6	122ms	147 days, 4 hours ago	local	NSID: a2402.tyo	OK
`DNSSEC`	v4	159ms	7 days, 11 hours ago	local	Key: 33631	OK
`DNSSEC`	v6	140ms	7 days, 11 hours ago	local	Key: 33631	OK
`EPP *`	v4	46ms	1 hour, 11 minutes ago	local	Tudor EPP (Mock) v2.0	OK
`EPP *`	v6	43ms	1 hour, 11 minutes ago	local	Tudor EPP (Mock) v2.0	OK
`WHOIS`	v4	301ms	2 hours, 1 minute ago	local	—	OK
`WHOIS`	v6	278ms	2 hours, 1 minute ago	local	—	OK

Nameservers

8 IPs tested

Hostname	IP Address	AF	ASN	RPKI
`a.dns.jp`	`203.119.1.1`	v4	—	—
`b.dns.jp`	`202.12.30.131`	v4	—	—
`c.dns.jp`	`156.154.100.5`	v4	—	—
`d.dns.jp`	`210.138.175.244`	v4	—	—
`e.dns.jp`	`192.50.43.53`	v4	—	—
`f.dns.jp`	`150.100.6.8`	v4	—	—
`g.dns.jp`	`203.119.40.1`	v4	—	—
`h.dns.jp`	`161.232.72.25`	v4	—	—

Per ICANN Spec 10, we test all delegated nameserver IPs independently.

Test With Your Computer

DNS

dig @a.dns.jp jp. SOA +dnssec +nsid Query SOA with DNSSEC validation and NSID

drill -D jp. SOA @a.dns.jp Alternative using drill with DNSSEC trace

WHOIS

whois -h whois.jprs.jp nic.jp Query WHOIS server directly

echo "nic.jp" | nc whois.jprs.jp 43 Raw TCP query (see exact response)

Registry Information

Active

TLD .jp

Operator Japan

WHOIS Server whois.jprs.jp

ICANN SLA Requirements

Per ICANN Registry Agreement Specification 10:

DNS SLA UDP RTT ≤ 500ms for 95% of queries. Availability: 99% (max 432 min/month downtime).

WHOIS SLA RTT ≤ 4000ms for 95% of queries. Availability: 98% (max 864 min/month downtime).

EPP SLA RTT ≤ 4000ms for 95% of commands (Spec 10 §5). Availability: 98% (max 864 min/month downtime). (Demo mode)

API Access

JSON API

Access .jp compliance metrics programmatically via our REST API.

Quick Start

GET /any53/api/v1/compliance/jp/

curl -H "X-API-Key: ${YOUR_API_KEY}" \
  "https://www.any53.com/any53/api/v1/compliance/jp/"

Example Response

{
  "tld": "jp",
  "display_name": ".jp",
  "operator": "Japan",
  "updated_at": "2026-01-31T12:00:00Z",
  "dns": {
    "availability_24h": 99.99,
    "rtt_p50_ms": 12,
    "rtt_p95_ms": 42,
    "sla_threshold_ms": 500
  },
  "rdds": {
    "protocol": "WHOIS",
    "availability_24h": 99.95,
    "rtt_p50_ms": 180,
    "rtt_p95_ms": 412,
    "sla_threshold_ms": 4000
  },
  "servers": {
    "whois_host": "whois.jprs.jp"
  },
  "spec10_compliant": true
}

Generate API Key

Get a free API key to start making requests. Provide an email to upgrade to the verified tier (600 requests/hour).

Endpoints

Endpoint	Description	Tier
`GET /compliance/`	List all monitored TLDs	All
`GET /compliance/{tld}/`	Current metrics for a TLD	All
`GET /compliance/{tld}/history/`	Historical time-series data	Organization
`GET /compliance/{tld}/probes/`	Per-probe breakdown	Organization
`POST /compliance/keys/`	Generate a new API key	No auth

Rate Limits

Tier	Rate Limit	Features
Anonymous	100/hour	Current snapshot, hourly aggregates
Verified	600/hour	Current snapshot, hourly aggregates
Organization	6000/hour	Historical data, per-minute resolution, per-probe breakdown