Skip to main content

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.

Flat editorial illustration on a dark navy background: a registry database record card outlined in teal with a blank contact-person silhouette, connected by thin lines to a small Europe and Middle East routing map with one isolated, dim amber-highlighted dormant node.

Europe and Middle East Institutional

Tideo Administration: The RIPE Contact Handle That Outlived Its Operator

Tideo Administration: The RIPE Contact Handle That Outlived Its Operator 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…

Oct 8, 2026
Dim server room mapped as a network topology graph, with a few IP allocation nodes glowing under scrutiny and ledger-like registry lines in the background

Europe and Middle East Regional ISP Trends

Inside almazcloud.network's Corporate Substance: A Fish-Farm Registration Behind a Cloud Storefront

Inside almazcloud.network's Corporate Substance: A Fish-Farm Registration Behind a Cloud Storefront intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…

Oct 8, 2026
Abstract network documentation pattern evoking WHOIS and RDAP record structures for AS152663

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…

Oct 8, 2026
Editorial illustration contrasting a frozen network registry layer with a live routing layer for EDEKA's number resources

Story

EDEKA's organisation object stays live while the AS210860 aut-num record returns no entries

EDEKA's organisation entity stays live while the AS210860 aut-num record returns no entries intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…

Oct 7, 2026
A compact relational node set branches into an oversized directory tree; an internal referral loops while a normalized core feeds a cleaner client view.

History

The Directory Tree Grew Sixfold. The Client Still Needed a Map.

RFC 3663’s Referral LDAP experiment made domain-registration data easier to query in principle. Its own engineering record shows how much work moved into data layout, referrals and clients before a familiar protocol could feel like a usable service.

Oct 7, 2026
Abstract technical diagram of RIPE registry object cards with icon shapes connected by typed lines, beside a blank name tag dissolving into static

Global Cloud Services

Who answers for AS209874: Novacloud's contact surfaces, registry objects and the handle that resolves to nothing

Who answers for AS209874: Novacloud's contact surfaces, registry entities and the handle that resolves to nothing intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the…

Oct 5, 2026
Abstract editorial illustration: a softly lit registry record card at center, surrounded by concentric faint registry-hierarchy outlines with a thin amber line descending from above to the card.

CASE FILE

Who answers for a silent network: DFINFRA's contact layer, the EDEKA merger and the accountability gap

Who answers for a silent network: DFINFRA's contact layer, the EDEKA merger and the accountability gap intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the…

Oct 5, 2026
Flat-vector registry record sheet being stamped and updated, with routing lines and a shield emblem over a world map grid, no text

Story

Record Hygiene or Real Movement? What AS210328's 2026 Ledger Edits Actually Changed

Record Hygiene or Real Movement? What AS210328's 2026 Ledger Edits Actually Changed intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that…

Oct 5, 2026
Editorial illustration: a database record sheet for AS210972 on a dark desk with faded routing graphs, symbolising a frozen registry contact

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…

Oct 4, 2026
Abstract illustration of a registry record stack and divergent routing paths joined by a glowing question mark, representing the AS152663 holder divergence

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…

Oct 4, 2026
Illustration of a hosting storefront contrasted with registry documents and a mismatched calendar

Europe and Middle East Cloud Services

NovaCloud-Hosting's paperwork does not match its storefront: the commercial-legal trace BTW had not yet examined

NovaCloud-Hosting presents one commercial face to customers, but the Portuguese registry, the LEI record and the operator's own checkout pages tell a different story about what kind of company is actually selling the hosting. This briefing reads that paperwork layer — the part of…

Oct 3, 2026
Conceptual illustration of a creator’s account linked to a person POC, beside a shared role POC connected to several accounts.

Story

ARIN’s Person-POC Workflow Links the Creator’s Account by Default

ARIN’s latest POC guidance identifies a consequential distinction at the moment a contact record is created: the person it is meant to represent may not be the user account that ARIN Online attaches to it.

Oct 2, 2026
Abstract layered network topology with delegated address blocks as stacked geometric tiles, no text or labels

Global Cloud Services

NovaCloud-Hosting's registry administration is split across three maintainers: who actually runs the operator's record?

NovaCloud-Hosting's registry administration is split across three maintainers: who actually runs the operator's record? intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and…

Oct 1, 2026
Stylised Europe map with abstract network nodes and highlighted registry data rows rendered as geometric bars, no text

Global Cloud Services

One operator, two RIPE organisations: the administrative layer BTW had not yet mapped

One operator, two RIPE organisations: the administrative layer BTW had not yet mapped intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…

Oct 1, 2026
Abstract editorial illustration: a frozen registry record card labeled TA8097-RIPE beside a routing table grid with an empty row

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…

Oct 1, 2026
Abstract custody-chain diagram of four linked nodes with one broken link, illustrating the split registry custody of network block 193.105.138.0/24

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…

Sep 30, 2026
Abstract documentary scene of an official decision document with embossed seal, approached by network routing lines and unlabeled mailbox rows that stop short of its operative core

CASE FILE

Sanctioned but Not Ordered: Svea's Two Accountability Channels

When a Swedish financial regulator fined Svea Bank AB 170 million kronor in December 2025, the fine made headlines. What the decision itself ordered — and, more precisely, what it did not — tells a sharper story about where accountability for the bank and for its internet-facing…

Sep 30, 2026
Editorial illustration: a dark map of European networks with one dimmed node representing AS210860's routing silence since late March 2026 and a translucent magnifying layer suggesting mirror-only registry records.

Story

AS210860 without a first-party witness: what the registry's unreadable endpoint means for DFINFRA

AS210860 without a first-party witness: what the registry's unreadable endpoint means for DFINFRA intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…

Sep 30, 2026
Abstract case-file illustration: a dark archive folder on a desk beside a document sheet with a highlighted blue band and a broad red band, both otherwise blank

CASE FILE

The Mailbox Was Never the Remedy: Where Accountability Actually Fired in the Svea Abuse-Contact Chain

Every abuse report has to land somewhere. For Svea's legacy routed network block 193.105.138.0/24, the landing place shown by independent mirrors of the RIPE Database is a shared mailbox on the Verizon Business domain — a carrier-era contact inherited from a lineage Svea never…

Sep 30, 2026
A dimmed network operations desk at night with one glowing abstract data-record card on a monitor, illustrating a stale registry abuse-contact record with no legible text.

CASE FILE

The Mailbox That Exists Only in the Registry: Svea's Abuse Contact and the Limits of "Valid"

When Svea Ekonomi AB merged into Svea Bank AB on 3 January 2022, the group's abuse-contact surface in the RIPE registry did not follow the merger. Nearly four years later, the routed legacy netblock 193.105.138.0/24 still presents a mailbox on a third party's domain…

Sep 30, 2026