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 Says It Added JSContact. Its RDAP Guide Does Not Say Which One.
AFRINIC’s public record contains a useful sentence and an unfinished question. The current release entry for WHOIS 2.10.7 says that an RDAP feature called JSContact was added. The current RDAP guide tells a reader where the service is, which resources may be queried, which…
Story
AFRINIC’s DBWG Shows 46 Open Items. A Count Is Not a State Path
Forty-six is a number that asks to be over-read. Put it next to the word Open and it can be made to sound like a verdict on an institution, a team or a service. AFRINIC’s public Database Working Group overview does not warrant that verdict. On the frozen 31 August 2026 capture…
Story
RIPE NCC Began Verifying Roughly 1,600 No-Contract Legacy Holders. Its Q3 Plan Still Describes Two-Place Updates
RIPE NCC has a sensible plan to give old resource records a clearer organisational anchor. Its own quarterly plan also reveals the awkward middle of that migration: one change may still have to be performed manually in two places. The test is not whether the campaign looks…
Story
ARIN's NET Permissions Change With the Lookup Path
One child NET, three ways to identify it, and three different questions about authority. An ARIN community suggestion reported that a direct registrant could reclaim a Detailed Reassignment and retrieve it through an exact address range, but could not use the same API key to GET…
Story
AFRINIC Has 3,573 Address Entities Pointing to Geofeeds. Its Schema Still Has No Geofeed Field
AFRINIC’s public database already carries geofeed pointers at material scale, but it carries them as prose. The fallback is valid and useful. The missing question is whether a convention used by thousands of address records should remain a string that the schema cannot identify…
Story
ARIN Put 17,000 Legacy Networks in a Blog Post. The Status Table Is Missing
ARIN has published an unusually concrete warning about the contact records attached to legacy IPv4 space: roughly 17,000 networks, an `about half` risk description, 11% currently validated, another 20% incomplete, and a 76% comparison for resources under agreement. The figures…
ICANN
ICANN's IPIP Termination Notice Has Two Lists—and Only One Names the Breaches
ICANN has told registrar IPIP INC. that its accreditation will end on 13 September. The eight-page notice is more precise than the inevitable shorthand: it names four breaches that remained uncured, then separately records additional concerns, then sets out consequences and…
Europe and Middle East Regional ISP Trends
Trifle's pioneer story needs a current operator-control map
Trifle's pioneer story needs a current operator-control map 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 Europe…
Story
RIPEstat Wants Better AS Names—and a Map of Which ASNs Are One Entity
RIPEstat Wants Better AS Names—and a Map of Which ASNs Are One Entity 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.…
Story
One Source IP Accounted for 38.76% of APNIC's WHOIS Queries in an Hour
One Source IP Accounted for 38.76% of APNIC's WHOIS Queries in an Hour 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.…
Story
ARIN’s RDAP Parent Handle Describes Registration Hierarchy, Not Network Transit
Two handles in one ARIN RDAP response can reconstruct how an address block sits inside the registry, but they cannot reveal who carries its traffic. The distinction is small in syntax and consequential in analysis.
Story
AFRINIC’s RDAP CIDR Array Describes a Registered Range, Not a BGP Route
AFRINIC’s RDAP service can render a registered address interval in the same CIDR notation used by routing systems. The shared notation is useful for comparison, but the registry field does not establish that a route exists, identify its origin or prove that traffic can reach the…
Story
APNIC's RDAP port43 Points to a Legacy WHOIS Service, Not Network Authority
In a live APNIC RDAP record, `port43` names `whois.apnic.net`. That is useful evidence about where to query the legacy registration service—but it is not a statement about who operates, routes or controls the addressed network.
ICANN
ICANN Wrote a 24-Hour Disclosure Clock. Authentication Decides When It Starts
The most consequential sentence in ICANN's new urgent-disclosure rules is not the one containing “24 hours.” It sits lower on the same policy page, in an implementation note: the obligations become effective when ICANN fully implements a Consensus Policy that establishes…
Story
APNIC Can Filter the Next WHOIS Download. It Cannot Recall the Old Ones
APNIC can remove contact fields from the next bulk-WHOIS dataset it generates. That is a real and testable privacy control. It cannot make the same edit reach backward into files that bulk-access users may already have downloaded under earlier terms. `prop-162` places both…
Story
APNIC’s prop-167 Status Needs Two Rows
APNIC did publish the hourly directory statistics its community asked to see. The live files make that success unusually easy to verify. They also make a second fact harder to ignore: `prop-167-v002` asked for another output, and the Executive Council gave it a different…
Story
LACNIC’s RDAP Last Changed Event Dates the Registry Record, Not the Network Handover
A timestamp in a registration record can anchor an investigation, but it cannot substitute for the event the investigator actually needs to prove. LACNIC’s live RDAP data makes that boundary unusually visible: a network entity and the entities embedded inside it carry different…
ICANN
When a Registration-Data Request Becomes Urgent—and What the New Clock Still Does Not Authorize
ICANN’s new urgent-request timetable can make a registrar answer faster. It cannot turn urgency into an automatic right to private data. The policy times acknowledgement and decision; authentication, necessity, legal basis and the merits of disclosure remain separate questions.
Leaders
Aaron Wendel and What Two Failed ARIN Proposals Reveal About Operator Power
Fourteen years apart, two public tallies put Aaron Wendel on the losing side of consequential debates about Internet number resources. The defeats are more revealing than a conventional success story: they show how practical operating knowledge enters policy, how commercial…
ICANN
The 90-Day Emergency Policy That Kept Domain Registration Data Moving
Eight days before the GDPR became applicable, ICANN used a temporary contractual power to keep one registration-data regime from fragmenting into hundreds of private answers. The power was immediate, but deliberately self-expiring: permanent policy had to come from somewhere…