Cedric Hoogendoorn is a name that appears in the RDAP record for autonomous system AS210320 and nothing else. No employer, title, or operational control is verified. The profile outlines the thin registry surface, lists concrete watchpoints (RDAP changes, routing activation, corroborating sources), and explicitly flags the uncertainty around authority and affiliation. This baseline helps analysts detect future shifts in the subject's infrastructure relevance and warns against over-reading the current footprint.

Cedric Hoogendoorn

Cedric Hoogendoorn is a name found only in the public RDAP registration for autonomous system AS210320. No employer, job title, or operational control is verified. The name's presence shapes how analysts attribute responsibility for the ASN, but the record is thin and could be outdated or represent a role account rather than an active individual.

Why It Matters

The registry listing can influence operational risk assessments and incident-response contacts. If the record is stale or misconfigured, it could mislead queries or create a false sense of attribution. Any update to the RDAP entry, the appearance of BGP announcements, or discovery of a real-world biography would directly change the subject's infrastructure significance.

What Public Sources Show

Cedric Hoogendoorn is not a company or a confirmed network operator. The name appears in a single public document: the RDAP registration record for autonomous system AS210320. No employer, job title, or operational authority is verified. That thin registry imprint is the entire visible control surface for this subject, and it is too faint to support any operational claim without new evidence.

Why the name matters: analysts who rely on internet registries to find responsible parties will encounter it. Used without corroboration, the entry can create a false sense of attribution or misdirect escalation during incidents. The name shapes public perception of who administers AS210320, even though the actual administrator may be someone else or an anonymous organisation.

two official sources anchor the profile. A query to https://rdap.org/autnum/210320 returns the name Cedric Hoogendoorn as a contact. A RIPEstat overview at https://stat.ripe.net/AS210320 confirms the autonomous system is registered but shows no active BGP prefixes. No PeeringDB entry, corporate website, professional network profile, or biographical source has been found to connect the name to a specific employer or role.

The operating surface begins and ends with that RDAP entry. There is no evidence that Hoogendoorn operates network hardware, configures routing, or makes policy decisions for AS210320. The name could be an administrative contact, a legacy entry, or an organisational role account. Without routing activity or additional sources, the subject has no observable operational footprint beyond the registry.

Three watchpoints would change the intelligence picture. First, any alteration of the contact name in the AS210320 RDAP record could signal a shift in administrative responsibility. Second, the appearance of BGP prefixes announced by AS210320 would indicate active routing; metadata referencing Hoogendoorn would strengthen the link to an operational role.

Third, discovery of a public biography, employer website, or PeeringDB entry naming Hoogendoorn alongside AS210320 would fill the current evidence gap.

The core uncertainty is that the name may be outdated or misconfigured registry data. Without a job title, employer, or confirmation of current role, the public record is a point-in-time snapshot that cannot distinguish between a live administrator and a historical contact. Any inference about seniority, decision-making power, or specific technical responsibility is unsupported by the public evidence.

Operating Surface

The only publicly supportable claim is that the name appears as a contact in the registry record. The registry does not specify whether the role is administrative, technical, or abuse-related, and no independent source confirms a specific function. The subject serves as a contact label for AS210320 but exercises no verifiable authority over routing or resources.

Because the name appears in a public internet registry, analysts may use it to infer an escalation path or assign responsibility for AS210320. Monitoring the record helps track changes that could signal a shift in administrative control. Without corroboration, the entry is weak, but its public visibility makes it a reference point for network dependency mapping.

Watchpoints

The presence of a personal name in an ASN registry gives a human face to an otherwise opaque resource, but without routing activity or corroborating sources, the subject provides no actionable intelligence about network operations or control. The strategic value lies in monitoring for changes that would convert a thin registry label into a real operating party.

Three observable events would upgrade the assessment: (1) any modification of the RDAP contact field for AS210320; (2) the first BGP announcements from AS210320, particularly if they carry a description or route object referencing Hoogendoorn; (3) the emergence of a PeeringDB entry, corporate website, or professional biography linking the name to an identifiable organisation.

No public source verifies the subject's job title, employer, location, or specific administrative role. Verification requires at least one of: a company website, a PeeringDB entry, a professional network profile, or a direct statement from the RIPE NCC or the ASN holder.

Sources

• Registry RDAP / WHOIS record - The RDAP entry for AS210320 lists Cedric Hoogendoorn as a contact, establishing the only public identity and registry context for this subject.
• RIPE registry record - RIPEstat confirms that AS210320 is a publicly registered autonomous system with no active BGP prefixes, providing routing context and visibility for the ASN.