What Is RDAP (And Why Replace WHOIS)?
WHOIS has long been the go-to protocol for retrieving domain registration details — but it’s also long been outdated, inconsistent, and insecure. It lacks standardized data structures, robust access control, and modern authentication. The same query could return wildly different formats depending on the registrar.
That’s where RDAP comes in.
RDAP (Registration Data Access Protocol) is a modern alternative that:
- Provides structured, machine-readable JSON responses
- Supports secure access, authentication, and rate limiting
- Allows for internationalization and standardized error messages
- Makes it easier to comply with privacy regulations (like GDPR)
In short: RDAP is WHOIS done right.
Key Timeline: When Is WHOIS Being Deprecated?
According to ICANN’s latest announcement, here’s the current timeline:
- ✅ Now (Early 2025): RDAP is fully live and supported by all registries and registrars.
- ⛔️ By 31 July 2025: Public Port 43 WHOIS services will be officially deprecated.
- 🔒 Registrars and registries will be expected to shift exclusively to RDAP.
- 🔁 WHOIS may still be available in limited, controlled scenarios — but not as a default public service.
For anyone monitoring domains or pulling WHOIS data in automated tools, this transition is critical.
What This Means for Developers, Sysadmins & Monitoring Tools
If your systems or scripts rely on WHOIS:
- 🧨 Port 43 access will break by Q3 2025.
- ❌ Inconsistent WHOIS responses will no longer be supported.
- 🔐 Rate limiting, authentication, and structured output will be enforced by registrars.
You’ll need to switch to RDAP — and that means either rewriting your scripts or using a platform that already supports it.
Acumen Logs: Future-Proof Domain Monitoring
At Acumen Logs, we’ve already made the switch.
Our domain monitoring features now use RDAP as the default protocol to retrieve:
- Expiry dates
- Registrar data
- Domain status flags (e.g., clientHold, serverDeleteProhibited)
- Nameserver changes
- Registrar transfers
✅ Fully compliant with ICANN’s requirements
✅ Supports ccTLDs and internationalized domains
✅ Automated expiry warnings via Slack, email, or webhook
✅ Works seamlessly alongside SSL, uptime, and synthetic monitoring
No need to rewrite WHOIS scripts or chase JSON parsing inconsistencies. We’ve built it into the platform — ready now, not later.
How to Prepare (If You're Still Using WHOIS)
If you're still using raw WHOIS:
- Start exploring RDAP endpoints (here’s a list from IANA).
- Expect to add headers, handle rate limiting, and parse structured JSON.
- Update cron jobs or monitoring pipelines that fetch domain expiry data.
Or — skip the infrastructure work and let Acumen Logs handle it for you.
Final Thoughts
The sunsetting of WHOIS marks a big shift in how domain data is accessed. RDAP brings consistency, security, and structure — but also complexity for teams still relying on legacy scripts.
ICANN has made the move official. The clock is ticking.
If you rely on domain data to prevent downtime, compliance issues, or expired services, now’s the time to switch.
