Summary

  • LACNIC says RDAP standardizes queries and responses, uses JSON, supports UTF-8 and works through HTTP or HTTPS.
  • BTW analysis: those properties make registry lookup programmable, but dependable automation still requires discovery, schema, access and failure controls.

Sources: LACNIC’s 2015 RDAP deployment account and its CTO’s 2024 comparison with WHOIS.

LACNIC described its RDAP implementation as already in production in 2015, developed internally with RIPE NCC code libraries. It presented standardized query and response formats, JSON output, UTF-8 and special-character searches as practical improvements over traditional WHOIS.

The 2024 account makes the operational contrast sharper. Port 43 WHOIS returns free text, while RDAP uses HTTP or HTTPS and structured responses. Those properties make software integration easier to design.

Structure does not remove policy. LACNIC also describes differentiated access and secure handling of contact information. A client therefore needs to distinguish an absent record from restricted data, throttling, discovery failure and an unavailable endpoint.

The evidence does not show universal migration, identical disclosure across registries or a universal service guarantee. The defensible conclusion is narrower: RDAP offers a better interface for automation, while operators remain responsible for testing the contract they actually consume.