TLD SLA Compliance Metrics
Spec 10DNS
| Period | Availability | RTT Compliance | RTT p50 | RTT p95 | Checks | TSLAC |
|---|---|---|---|---|---|---|
| 24h | 100% | 100% | 84ms | 162ms | 165 | |
| 7d | 100% | 100% | 83ms | 253ms | 2010 | |
| 30d | 94.71% | 94.71% | 84ms | 253ms | 2704 |
WHOIS
| Period | Availability | RTT Compliance | RTT p50 | RTT p95 | Checks | TSLAC |
|---|---|---|---|---|---|---|
| 24h | 100% | 100% | 290ms | 645ms | 12 | |
| 7d | 100% | 99.52% | 289ms | 710ms | 208 | |
| 30d | 99.65% | 99.31% | 292ms | 779ms | 288 |
EPP *
| Period | Availability | RTT Compliance | RTT p50 | RTT p95 | Checks | TSLAC |
|---|---|---|---|---|---|---|
| 24h | 100% | 100% | 49ms | 49ms | 2 | |
| 7d | 100% | 100% | 44ms | 47ms | 78 | |
| 30d | 100% | 100% | 37ms | 41ms | 98 |
DNSSEC Validation Metrics
Registry Agreement Spec 6DNSSEC 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 | Status |
|---|---|---|---|---|---|
| 24h | 100% | 139ms | 160ms | 2 | |
| 7d | 100% | 139ms | 159ms | 142 | |
| 30d | 100% | 139ms | 160ms | 212 |
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 | TSLAC |
|---|---|---|---|---|---|---|---|
DNS
|
v4 | 122ms | 41 minutes ago | local | NSID: app9.nrt1.hosts.meta.re… | OK | |
DNS
|
v6 | 138ms | 41 minutes ago | local | NSID: app4.nrt1.hosts.meta.re… | OK | |
DNSSEC
|
v4 | 161ms | 5 hours, 24 minutes ago | local | Key: 33631 | OK | |
DNSSEC
|
v6 | 139ms | 5 hours, 24 minutes ago | local | Key: 33631 | OK | |
EPP *
|
v4 | 50ms | 3 hours, 21 minutes ago | local | Tudor EPP (Mock) v2.0 | OK | |
EPP *
|
v6 | 49ms | 3 hours, 21 minutes ago | local | Tudor EPP (Mock) v2.0 | OK | |
WHOIS
|
v4 | 298ms | 1 hour, 33 minutes ago | local | — | OK | |
WHOIS
|
v6 | 289ms | 1 hour, 33 minutes ago | local | — | OK |
Nameservers
15 IPs tested| Hostname | IP Address | AF | Status |
|---|---|---|---|
a.dns.jp |
203.119.1.1 |
v4 | |
a.dns.jp |
2001:dc4::1 |
v6 | |
b.dns.jp |
202.12.30.131 |
v4 | |
b.dns.jp |
2001:dc2::1 |
v6 | |
c.dns.jp |
156.154.100.5 |
v4 | |
c.dns.jp |
2001:502:ad09::5 |
v6 | |
d.dns.jp |
210.138.175.244 |
v4 | |
d.dns.jp |
2001:240::53 |
v6 | |
e.dns.jp |
192.50.43.53 |
v4 | |
e.dns.jp |
2001:200:c000::35 |
v6 | |
f.dns.jp |
150.100.6.8 |
v4 | |
f.dns.jp |
2001:2f8:0:100::153 |
v6 | |
g.dns.jp |
203.119.40.1 |
v4 | |
h.dns.jp |
161.232.72.25 |
v4 | |
h.dns.jp |
2a01:8840:1bc::25 |
v6 |
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 APIAccess .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).
Save this key now! It cannot be retrieved later.
Tier:
Rate limit: /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 |