Summary

  • ARIN’s ARIN 58 Directory Services slides count 43 substantive Port 43 Whois comments: 24 opposing retirement or seeking a much longer transition, 11 supportive and eight neutral or procedural.
  • Its ten largest query sources in a seven-day snapshot resolved to cloud-provider addresses. ARIN will watch RDAP client adoption and traffic, then consult the community again on Port 43.

The funeral notice for Port 43 Whois has a comments section. ARIN’s Directory Services deck sorts 43 substantive submissions into three piles: 24 oppose retirement or ask for a much longer runway, 11 support it, and eight are neutral or procedural. Those are self-selected comments, but they are a remarkably clear warning to the people holding the calendar.

ARIN’s own traffic view also has a blind spot. The top ten query sources in a seven-day window all resolved to cloud-provider addresses. The registry can see the front door; those addresses do not identify which organizations or scripts are actually knocking. An automatic message to a cloud provider would reach a landlord before it reached the tenants. The deck gives no count of distinct end users behind those addresses.

The engineers’ proposed detour is hardly a shortcut. ARIN says a Whois-compatible proxy placed in front of RDAP would take more effort and operational risk than keeping the native service running longer. ARIN’s Whois guide explains the basic swap: Port 43 serves familiar text queries; RDAP provides structured HTTP and JSON access. The transition changes clients and workflows, even when the underlying registration data remains available.

In its 21 October consultation result, ARIN says it will monitor RDAP adoption in commercial products and query traffic, then return to the community when its prerequisites are met. It gives no numeric threshold or Port 43 retirement date. The old service keeps answering while the registry works out who uses it and how to find them.