.рус (xn--p1acf)

TLD SLA Compliance Monitoring

TLD SLA Compliance Metrics

Spec 10

No metrics available yet

Metrics will appear after probes start reporting data. Check back in about an hour.

Current Check Status

Reported by Any53 Probes
Type AF RTT Last Check Source Details Status TSLAC
DNS v4 1.5ms 33 days, 14 hours ago local NSID: 3.ord.pch OK
DNS v6 1.6ms 33 days, 14 hours ago local NSID: 4.ord.pch OK
DNSSEC v4 21ms 33 days, 15 hours ago local Key: 50380 OK
DNSSEC v6 30ms 33 days, 15 hours ago local Key: 50380 OK
RDAP v4 276ms 33 days, 17 hours ago local TLS 1.3 OK
RDAP v6 277ms 33 days, 17 hours ago local TLS 1.3 OK

RDAP HTTPS Timing

277ms total
DNS Lookup
—
TCP Connect
89ms
TLS Handshake
99ms
Time to First Byte
277ms

TLS 1.3 / TLS_AES_256_GCM_SHA384

Nameservers

6 IPs tested
Hostname IP Address AF ASN RPKI Status
ns1.anycastdns.cz 185.38.108.108 v4 AS60592
ns1.anycastdns.cz 2a00:fea0:dead::beef v6 — —
ns1.nic.xn--p1acf 72.42.113.2 v4 — —
ns1.nic.xn--p1acf 2620:171:d01:dc::2 v6 — —
ns2.nic.xn--p1acf 72.0.49.2 v4 — —
ns2.nic.xn--p1acf 2620:171:a01:ad::2 v6 — —

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

Test With Your Computer

DNS

dig @ns1.anycastdns.cz xn--p1acf. SOA +dnssec +nsid Query SOA with DNSSEC validation and NSID
drill -D xn--p1acf. SOA @ns1.anycastdns.cz Alternative using drill with DNSSEC trace

RDAP

curl -sS "https://rdap.nic.xn--p1acf/domain/nic.xn--p1acf" | jq . Fetch RDAP JSON (positive lookup)
curl -I -sS "https://rdap.nic.xn--p1acf/domain/nic.xn--p1acf" Headers only (check TLS, timing)
Open in Browser View RDAP response directly

Registry Information

Active
TLD .рус (xn--p1acf)
Operator Rusnames Limited
RDAP Server https://rdap.nic.xn--p1acf/ RDAP Client

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).
RDAP SLA RTT ≤ 4000ms for 95% of queries. Availability: 98% (max 864 min/month downtime).

API Access

JSON API

Access .рус (xn--p1acf) compliance metrics programmatically via our REST API.

Quick Start

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

Example Response

{
  "tld": "xn--p1acf",
  "display_name": ".рус (xn--p1acf)",
  "operator": "Rusnames Limited",
  "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": "RDAP",
    "availability_24h": 99.95,
    "rtt_p50_ms": 180,
    "rtt_p95_ms": 412,
    "sla_threshold_ms": 4000
  },
  "servers": {
    "rdap_url": "https://rdap.nic.xn--p1acf/"
  },
  "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