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.
ICANN
A Valid Inbox Is Not a Title Deed: The Four Proofs ICANN’s Accuracy Rules Keep Separate
ICANN’s registration-data rules can test whether a field is well formed and whether somebody answers an email or telephone call. Those are useful controls. They are not the same as proving who controls the registrar account, still less deciding which person or company has the…
Story
AFRINIC Took Identity Proofing to Kigali. The Registry Handoff Needs a Receipt
A government ID can cross a conference desk in seconds. A registry change must remain explainable long after the badge, booth and meeting room have disappeared. AFRINIC's AfPIF service offer joined those two moments; the missing public entity is the receipt that keeps them…
Story
LACNIC's Anti-Fake-IXP Log Has No Event Column
LACNIC has made a scarce IPv4 reserve unusually visible. Its public file can show who holds an issued interval and how much of the pool remains reserved. What it cannot say in one row is what happened. A log commissioned to cover assignments, recoveries and returns still…
Story
APNIC's Impact Assessments Leave the Both-Pass Outcome Undefined
The word `nibble` will appear twice on APNIC 62's policy agenda. One proposal would move the minimum IPv6 allocation from `/32` to `/40`. The other would leave `/32` untouched and align a larger, already-validated request. A shared hexadecimal convenience hides two different…
Story
LACNIC's Legacy Deadline Is Running Ahead of Its Policy
Prior BTW reporting describes legacy IPv4 holders answering an administrative request while the community rule that would govern the same evidence is still being debated. That sequence does not make the outreach illegitimate. It makes the label on every decision unusually…
Story
The Evidence ARIN Should Require Before Retiring Legacy Whois
ARIN's new directory-services consultation looks like a consolidation project. Its migration inventory tells the more important story: an API can announce its own retirement, a local reassignment server needs a conversion tool, and Port 43 can hide inside scripts that the…
Story
The Resolution That Opened the Ledger — and No More
On 20 January 2021, AFRINIC’s Board approved publication of a report that put numbers against weaknesses in the registry’s public word. The decision made part of the institution’s bookkeeping open to inspection, an important act in a system where operators and outsiders may rely…
Story
The Seven-Day Ledger: AFRINIC’s 2014 Registration Proposal and the Line It Could Not Cross
An assignment of eight IPv4 addresses could have started a seven-business-day countdown: under a 2014 proposal, an AFRINIC member would have had to turn that customer or infrastructure allocation into a documented WHOIS record. The discipline was practical and potentially…
Global Cloud Services Trends
An IP address is a routing identifier, not a person
Addresses let networks deliver packets and administrators trace responsibility. Shared access, reassignment and translation make them weak evidence of individual identity.
Global Regional ISP Trends
Public operator identity needs dated evidence
William-Marie DESPORTES appears across registry and software-maintenance contexts. That is an accountability clue, not proof that every role remains current.
Story
ARIN records coordinate resources, not networks
ARIN allocates number resources and maintains public records in its service region. Operators still decide how addresses and routes behave.
Story
The RIPE NCC combines registry service and community
The RIPE NCC operates number-resource services while the wider RIPE community develops policy. Keeping those roles visible is part of accountability.
Global Cloud Services Trends
An IPv4 address needs an accountable owner
An IPv4 address locates an interface for routing. Scarcity and reuse make its current operational custodian as important as the number itself.
Global Cloud Services Trends
Changing an IP address needs a dependency inventory
The routing change may take minutes; hidden allowlists, DNS records, certificates, reputation systems and support procedures can take far longer to follow.
Story
The Khartoum Line Between Maintenance and Consequence
At AFRINIC-17, a practical dispute over inaccurate registry contacts exposed a harder institutional question: when does responsible database maintenance become a rule that changes a member’s position? The meeting record shows why the answer matters to both network continuity and…
Story
When a WHOIS Edit Became a Cryptographic Instruction
In 2012, AFRINIC gave members a way to send DS records towards parent reverse-DNS zones by updating `domain` entities in its WHOIS database. The feature sounded like a modest extension of registry administration. In fact, it joined two very different systems: a record about who…
Story
The Returned Envelope and the Locked Drawer
AFRINIC’s 2012 WHOIS cleanup proposal began with a sensible ledger problem and ended with an authority it could not possess. The useful question was how a private registry should keep contact records accurate and make its own maintenance work visible. The dangerous one was…
Story
AFRINIC's 2010 infrastructure reinvestment jumped to USD 346,203—but the office took most of it
AFRINIC's own presentations show a Board-authorised capital programme whose largest disclosed result was a new office, not a documented technical transformation. The useful question is not whether premises can count as infrastructure, but whether each capital decision can be…
Story
AFRINIC May Check the Colon; It May Not Rule the Network
AFRINIC May Check the Colon; It May Not Rule the Network 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…
North America Regional ISP
Inside The Internet, Inc and AS14473 show two announced IPv4 prefixes with uneven RPKI coverage
Inside The Internet, Inc and AS14473 show two announced IPv4 prefixes with uneven RPKI coverage intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…