Primary Domain
WHOIS/RDAP Accountability
Within the Primary Domain facet, WHOIS/RDAP Accountability intelligence groups reporting by primary domain so readers can follow a focused area of internet infrastructure, governance, connectivity markets, or digital capital. The page brings together related articles, public evidence, institutions, companies, people, regional exposure, operating dependencies, and market context that may otherwise sit across separate category pages. It explains the domain, the likely actor class, the market or governance context, and the source material readers should use when comparing signals. Operators, analysts, and governance readers can see how the same domain appears across events, profiles, market shifts, public-source evidence, regional dependencies, and longer-cycle infrastructure decisions over time.
Asia-Pacific Cloud Services Trends
One Mailbox, Two Companies, One Address: What Reproduced APNIC Whois Text Shows About NEXGENET COMPANY LIMITED's Accountability Surface
NEXGENET COMPANY LIMITED looks, from a distance, like an ordinary small internet provider in Yangon. Look directly at the registry records that define who answers for its networks, and the picture becomes more complicated: one generic role entity named "NEXGENET COMPANY LIMITED…
Global Institutional
Tideo Administration: The Contact Handle That Outlived Its Network
Tideo Administration: The Contact Handle That Outlived Its 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…
Asia-Pacific Regional ISP
NEXGENET COMPANY LIMITED and the Question the Registry Still Cannot Answer
NEXGENET COMPANY LIMITED and the Question the Registry Still Cannot Answer 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…
CASE FILE
Tideo Administration: The Registry Record That Refused to Move
Tideo Administration: The Registry Record That Refused to Move 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 CASE…
CASE FILE
Three Names on One Netblock: How Custody of Svea's Legacy Abuse Contact Split Across a Merger
When a Swedish bank merges, its internet number resources do not disappear — they inherit. The RIPE Database record for 193.105.138.0/24 is a rare case where you can read the aftermath directly in a public registry entity: three distinct legal parties, one dissolved predecessor…
Story
Control Split: Who Held Prevention and Detection on the Svea Abuse-Contact Surface
Svea Ekonomi AB merged into Svea Bank AB on 3 January 2022, but the RIPE registry entities that describe the group's abuse-contact surface have barely moved since 2021 and 2022. A timestamp-by-timestamp reading shows that recent maintenance in this chain fell almost entirely on…
CASE FILE
GoCodeIT Support: a role label, a corporation, and where accountability actually sits
GoCodeIT Support is a name that looks like a person in the registry, but the public evidence shows it is an institutional contact role — and the accountability behind it sits with a company in two RIRs at once.
CASE FILE
The Chain That Was Touched: Where Attention Fell in the Svea Abuse-Contact Record
The Chain That Was Touched: Where Attention Fell in the Svea Abuse-Contact Record intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that…
CASE FILE
Filing the Complaint: The Public Remedy Path Behind the Svea Abuse Contact
Svea's abuse contact in the RIPE registry passes every automated check the registry runs, and no public source shows it has ever answered a report. This briefing sets out the filing test: the channels a reporter can actually use today, and the observable responses that would…
CASE FILE
One Validated Mailbox, One Unresolved Holder: Reading NEXGENET's Accountability Surface Directly
APNIC's own whois confirms that the abuse mailbox behind three autonomous systems was validated on 7 July 2026 — but the holder of one of those systems is now written differently by different public mirrors, and the registry of record still cannot be read first-hand.
Asia-Pacific Regional ISP
A Mailbox Held Accountable: NEXGENET's Contact Surface After the July 2026 Validation
Behind three registered autonomous systems at a small Yangon LIR sits one self-referential role entity and one company mailbox. The freshest signal in the public record — an abuse-mailbox validation remark dated 7 July 2026 — says that surface is still maintained. What it does…
Europe and Middle East Regional ISP
AS210837: a registry record without a network, read only through its mirrors
AS210837: a registry record without a network, read only through its mirrors 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…
IETF
The token is valid. The RDAP query still has no entitlement
RFC 9560 gives RDAP a federated identity and token flow. It does not make authentication proof of purpose, query-level authorization, proportionate disclosure or a useful registration-data outcome.
Story
What Comes After ARIN’s Empty Whois Replies
ARIN resolved a problem with some Whois queries in August. For anyone whose tools retained a suspect result, the next task is different: checking the local copy without turning a failed observation into a registration verdict.