Topic
WHOIS/RDAP Accountability
Within the Topic facet, WHOIS/RDAP Accountability topic intelligence connects articles that share a specific subject, signal focus, or monitoring theme. The page gives readers a richer path through related reporting, source evidence, market actors, and infrastructure implications, with enough context to understand why the topic matters across company movements, governance decisions, regional exposure, and operational risk. Readers can compare recurring signals, affected organisations, public evidence, market context, service continuity, procurement, competition, compliance, and strategic planning questions behind the subject instead of stopping at a thin list of matching articles. It explains what the topic covers, which infrastructure actors or policies are involved, what evidence supports the coverage, and why the subject may matter for operators, customers, investors, and policy readers.
Story
AFRINIC Shelved AS328472. RDAP Kept Its “Active” Badge.
AFRINIC Shelved AS328472. RDAP Kept Its “Active” Badge. intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow. The Story…
Leaders
Hollis Kara cannot retire Whois for users ARIN cannot find
ARIN wanted one modern directory. Its oldest lookup door still draws more traffic than the replacement, and much of that traffic arrives wearing a cloud provider's address. A retirement notice has to reach someone behind the proxy.
Story
RIPE Gave ScopeSky Three /24s. One Still Speaks Through Elsuhd’s ASN.
RIPE Gave ScopeSky Three /24s. One Still Speaks Through Elsuhd’s ASN. intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow.…
Leaders
Kaveh Ranjbar Wants the Registry to Point Beyond Its Own Record
A lookup can find the holder of a network and still miss the holder’s current registration data. At RIPE 93, Kaveh Ranjbar asked the database community to make that last hop visible—and to decide what happens when the destination lies.
Story
APNIC Gave Two Neighbouring /23s Names. RDAP Remembered Only One.
A 2 November allocation put adjacent IPv4 blocks in Indonesia and Bangladesh. The machine-readable lookup names Braintel; the Indonesian holder appears in Whois while RDAP returns a root entity.
Story
RIPE's /18 Has No /18 Record. Its Last Two /24s Have Different Registrants.
Vodafone ONO's old address span now ends in two separately registered /24s. RIPE's transfer file tells the two departures with different original-block fields; a literal /18 RDAP query misses the whole local story.
Leaders
Terry Manderson Gave APNIC Email Updates a Year to Live. The Room Kept Them.
APNIC wanted registry changes to arrive through authenticated transactions rather than a crowded mailbox. The people who had built their own update scripts wanted to know who would pay for the switch.
Story
A School Stayed Inside Fatbeam’s ARIN Block. The Transfer Came Two Years Later.
ARIN’s transfer ledger and live RDAP give different names for the same first address. One records the parent’s 2018 handover; the other still exposes a child assignment dated 2016.
Leaders
Aftab Siddiqui Put an Owner's ASN in the AS-SET Name
Aftab Siddiqui Put an Owner's ASN in the AS-SET Name intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow. The Leaders…
Leaders
Leo Vegoda Wants the New RDAP Desk to Tell Everyone the Same Story
A registry can point a lookup to someone else's server. Leo Vegoda's question at RIPE 93 was what happens after the handoff: will that server show the registry one record and the rest of the Internet another?
Story
RIPE Logged a U.S. Recipient. The /20 Stayed in RIPE’s Book.
A 30 October transfer moved 4,096 IPv4 addresses to a U.S.-registered company. RIPE filed it as an internal transfer, and its live database still holds the record.
Story
RIPE Replaced the Database Cookie. Then the Web App Ran Out of Sockets.
The new login reached the RIPE Database website in September. A connection leak then stopped its web application for minutes while neighbouring database services kept running.
Story
APNIC Promises Public Bulk RDAP. The Access Rules Are Still Missing.
APNIC plans to make bulk RDAP data public in 2026. Its current bulk Whois page still asks for a signed use agreement. The difference matters to anyone building a reliable picture of who holds Internet number resources—and the council minutes leave the terms of the new door…
Story
Nearly 15 Months After RIPE NCC’s RDAP Promise, ENUM Still Gets a 501
RIPE NCC said in August 2025 that its database team would add e164.arpa to RDAP. On 1 November 2026, queries for the zone and a country-code branch still returned “Not Implemented”; the October update said work had progressed, but named no release date.
Story
A New RDAP Draft Adds Six IRR Paths. Three Stay Optional.
A 29 October Internet-Draft from authors at RIPE NCC and ARIN sketches a JSON route for six Internet Routing Registry entity types. Its own text leaves three families—and a bundle of route-policy fields—to each server’s choice.
Story
ARIN Chose RDAP. Port 43 Still Has No Retirement Date
ARIN’s new directory-services roadmap replaces one sunset calendar with four separate readiness tests. Port 43 WHOIS, still used across security and research, now has no fixed retirement date.
Story
RIPE’s WHOIS Light Went Green. Which Edits Got Through?
The registry marked an intermittent update fault fixed and resolved in under half an hour on 28 October. Its public clock says when the service recovered, not what happened to each attempted edit.
Story
AFRINIC’s Reverse-DNS Rule Meets the Delete Key
An operator says the database makes him remove reverse-domain records before he can repair the address records that justify them. A tidy rule has acquired a messy exit.
IETF
The RDAP Redirect Can Deliver the Record and Drop the Question
A registry-data query can reach the right server and still lose the instruction that shaped the question. The current IETF working-group draft on RDAP extensions draws that line deliberately: a server issuing a cross-authority redirect cannot simply copy the original query string…
ICANN
First in Line, Short on Cash: ICANN’s Four-TLD Dropzone Has a Second Rule
Jolly Host wants to move expiring names in four top-level domains into a parallel application queue. The application calls it first come, first served. Its next sentence supplies the other rule: when the first registrar lacks enough money in its registry account, the name goes to…