Dennis Longen

Dennis Longen is a registry contact for AS210922 with unverified authority. The only public evidence is RIPE Database records showing his handle DL10489-RIPE. No employer, title, or decision-making power is confirmed. Monitoring changes to his record is a key watchpoint for operational shifts. The profile is constrained by the absence of first-party biography or live BGP data.

Dennis Longen

Dennis Longen is a named contact in public RIPE Database records for autonomous system AS210922 and its associated route entity for prefix 185.169.52.0/22. Listed under handle DL10489-RIPE as administrative and technical contact, he represents a human point of coordination for the network. However, his employer, decision-making authority, and current operational engagement are not confirmed by any public source beyond the registry entries.

Why It Matters

If Dennis Longen's registry entry is inaccurate or hijacked, operators attempting to resolve routing issues or report abuse for AS210922 may direct communications to the wrong party. This could result in prolonged security incidents, misconfiguration of BGP announcements, or even prefix hijacking. The impact is moderate but amplified by the absence of any verified fallback contact for the ASN.

What Public Sources Show

Dennis Longen appears as the administrative and technical contact for Internet autonomous system AS210922 in public RIPE Database records. This registry listing makes him a human interface for operators who need to reach the entity behind the ASN. If the contact information is stale or compromised, coordination for routing issues or abuse reports could break down, and route-entity changes could be abused to hijack the associated prefix 185.169.52.0/22.

Registry sources show Dennis Longen via the handle DL10489-RIPE. The RIPE Database person entity is referenced as the admin-c and tech-c for AS210922. A route entity for 185.169.52.0/22 also ties the ASN to the same registry context. No other public documents – such as an employer website, LinkedIn profile, or company biography – corroborate his current role, title, or organisational affiliation.

His operating surface is bound to the RIPE Database entities he is listed on. With the necessary credentials, he could update contact details, modify routing policy attributes, or add new route entities for AS210922. There is no evidence that he has direct control over routers or financial decisions. The real influence depends on internal policies of the still-unknown organisation holding the ASN.

The profile is built solely from registry data. No independent source confirms whether Dennis Longen is still active in this role, whether he is an employee, contractor, or volunteer, or whether the records are up to date. The absence of live BGP routing data for the prefix leaves the operational status of the network itself unverified.

Analysts should monitor changes to the DL10489-RIPE person entity, such as updates or removal. New prefix announcements by AS210922, or the appearance of an official company website or PeeringDB entry, would flesh out the operating picture. Any security incident tied to the ASN could also expose the contact to personal scrutiny, given the public nature of the listing.

The central uncertainty is whether this registry entry reflects a current operational role or a historical artifact. The person’s employer, decision-making latitude, and actual responsiveness remain unknown. Until further evidence appears, the profile is a sketch of a registry contact, not a full professional portrait.

Operating Surface

He serves as the admin-c and tech-c contact for AS210922, as recorded in RIPE entities. This role grants him registry-level visibility and the potential ability to update routing policy entities, but it does not prove he controls network hardware or makes financial decisions. No public biography or employer page verifies his title or the organisation he represents.

Analysts monitoring internet numbering resources track registry contacts like Dennis Longen because changes to his handle can signal shifts in operational control or responsibility for AS210922. A compromised or stale entry could lead to misrouted traffic or delayed abuse response. Understanding who is publicly associated with the ASN helps map dependencies in the internet infrastructure ecosystem.

Watchpoints

Dennis Longen represents a human dependency for AS210922 registry maintenance. His continued listing or removal directly affects how the network is reachable for coordination. Since no alternative contact is identified, his role is a single point of contact. The lack of attribution to a known organisation means any strategic assessment of the ASN's operator must be inferred from the registry data alone.

If the DL10489-RIPE handle is removed or altered without replacement, it could indicate abandonment or transfer of the ASN, raising security and routing integrity concerns. Conversely, if new contacts are added alongside an official website or PeeringDB entry, the entity's operating posture becomes clearer. Live BGP announcements for the prefix would confirm active use.

Absent are: the legal name of the organisation holding AS210922, a public website or PeeringDB profile, live BGP routing data, and any biographical confirmation of Dennis Longen's current role. Filling these gaps would require direct inquiry of the registered maintainer or discovery of corporate filings linked to the ASN.

Sources

• RDAP record for AS210922 - The RDAP query returns Dennis Longen as a contact for AS210922, confirming his presence in the registry under handle DL10489-RIPE.
• RIPE Database query for handle DL10489-RIPE - The RIPE Database page for DL10489-RIPE shows the person entity details, verifying that Dennis Longen is a registered contact person.
• RIPE Database query for AS210922 - The query result for AS210922 shows the aut-num entity, referencing admin-c and tech-c contacts that include DL10489-RIPE, linking Longen to the ASN.
• RIPE Database route entity for 185.169.52.0/22 - The route entity confirms that prefix 185.169.52.0/22 originates from AS210922, establishing the routing registry context in which Longen’s handle appears.