WHOIS Rate Limiting
Embed This Widget
Add the script tag and a data attribute to embed this widget.
Embed via iframe for maximum compatibility.
<iframe src="https://tldfyi.com/iframe/glossary/whois-rate-limiting/" width="420" height="400" frameborder="0" style="border:0;border-radius:10px;max-width:100%" loading="lazy"></iframe>Paste this URL in WordPress, Medium, or any oEmbed-compatible platform.
https://tldfyi.com/glossary/whois-rate-limiting/Add a dynamic SVG badge to your README or docs.
[](https://tldfyi.com/glossary/whois-rate-limiting/)Use the native HTML custom element.
WHOIS rate limiting is an anti-abuse measure implemented by [[registry-operator|registry operators]] and [[registrar|registrars]] that restricts the number of [[whois|WHOIS]] queries a single IP address or client can make within a given time window. Without rate limiting, automated scrapers can harvest bulk registrant contact data for spam campaigns or competitive intelligence — a practice that [[whois-privacy|privacy regulations]] like GDPR have also curtailed by restricting what data is returned. The [[rdap|RDAP]] protocol, which replaced WHOIS in many contexts, inherits rate-limiting support at the protocol level and allows finer-grained access control, including differentiated responses for authenticated vs. anonymous users. Verisign's WHOIS server for .com enforces a limit of roughly 1,000 queries per hour per IP.
Example
A domain research tool that submits more than a few hundred .com WHOIS queries per hour from the same IP will receive HTTP 429 or connection refusals from Verisign's WHOIS server; the tool must rotate IPs or implement backoff to continue operating.