RDAP rate limits and access tiers
RDAP rate limits vary wildly by registry, from 10 requests per 10 seconds to 300 a day, none of it standardized. Real per-registry numbers and what ICANN's RDRS access-tier system actually is in 2026.
RDAP rate limits vary wildly by registry, from 10 requests per 10 seconds to 300 a day, none of it standardized. Real per-registry numbers and what ICANN's RDRS access-tier system actually is in 2026.
An RDAP JSON response reads in four groups: identity, events, entities, and status, plus a few blocks you can skip. Walked through with one real response for example.com, field by field, in the order you actually need them.
WHOIS and RDAP look up the same domain registration record, but only one of them is still the protocol ICANN actually requires. Here is the real difference and the verified 2019 to 2025 timeline that made RDAP the default.
Domain monitoring and DNS monitoring watch two different layers of the same name: registration versus resolution. Here is what each one catches, where they overlap at the nameserver, and which layer catches which outage, so you know why you need both.
Domain hijacking shows up in the registration record before you lose the name: a transfer lock removed, a pendingTransfer flag, a nameserver or registrant rewrite. Here is how to detect domain hijacking early by watching WHOIS and RDAP, with the perl.com case as the lesson.
Domain expiry monitoring reads your domain's WHOIS or RDAP record on a schedule and warns you weeks ahead, so a missed renewal never takes your site, email, and certificates offline at the same time. Here is the expiry lifecycle, how to check it, and how to alert in time.