Dmitry E Kiselyov

Dmitry E Kiselyov is the RIPE registry contact handle DEK-RIPE for silent AS210928. No employer, location, or operational activity ties to the name. The control surface is limited to registry communications and contact updates; there is no evidence of authority over BGP routing or network infrastructure. The profile is low-confidence and will remain so until routing activation, identity confirmation, or registry record changes appear. Watchpoints monitor registry state, ASN activity, and any real-world identity link.

Dmitry E Kiselyov

Dmitry E Kiselyov appears as the administrative and technical contact for silent autonomous system AS210928 in the RIPE Database under handle DEK-RIPE, with no verified employer, operational role, or active routing presence; the profile reflects a registry touchpoint of minimal current impact but potential future relevance.

Why It Matters

Currently, the subject has minimal routing impact due to no active BGP prefixes; however, if the registry record is authentic, the contact could facilitate resource transfers or updates, and activation of AS210928 would increase the infrastructure dependency risk.

What Public Sources Show

Dmitry E Kiselyov appears exclusively in the RIPE public registry as the administrative and technical contact for autonomous system AS210928, with the database handle DEK-RIPE. No other public digital footprint—such as a corporate website, professional profile, or biographical detail—ties this name to a verifiable person or organization. The handle itself is the sole persistent identifier, leaving the subject's real-world identity and authority uncertain.

AS210928 is an assigned autonomous system number in the RIPE region, but it currently announces no BGP prefixes and appears in no operational routing tables. This dormancy means the contact's practical influence on inter-domain routing is effectively zero. However, the registry listing grants the contact the ability to receive official communications and potentially update ASN registration details, a narrow but legitimate control surface.

The primary mechanism of impact, if the record is maintained and authorised, lies in registry administration: resource transfers, contact modifications, or future prefix registrations could all be handled through the DEK-RIPE handle. Because there is no evidence of the subject operating a network, managing routers, or executing routing policy, the current risk remains confined to the administrative layer of the number resource system. What public sources show is limited.

The RDAP/WHOIS query for AS210928 confirms the role and handle; the BGP monitoring page on bgp.he.net and the RIPE Stat overview each corroborate the ASN’s existence and the absence of announced prefixes. No source connects the name to an employer, a PeeringDB entry, a corporate registration, or any professional affiliation.

The information gap is significant: we cannot assess whether the handle is actively used, stale, or a placeholder created long ago. For these reasons, the subject merits a low-confidence baseline watch.

The assessment would shift materially if AS210928 begins announcing prefixes, if the DEK-RIPE handle changes its associated contact data, or if a real-world identity emerges—such as a LinkedIn profile, a company registration, or a PeeringDB record. Conversely, if the handle disappears or remains dormant indefinitely, the profile’s relevance will diminish.

Data gaps worth monitoring include the absence of any verified email address, phone number, or mailing address in public records; the unknown tenure of the handle; and the lack of a sponsoring organization. Without these, the subject cannot be confidently linked to any operational or jurisdictional risk. This profile will be updated when new public evidence becomes available.

Operating Surface

The subject is listed in RIPE public records as admin/tech contact for AS210928, granting the holder the ability to receive registry correspondence and potentially update contact details, but without demonstrated control over network operations or BGP announcements.

Dmitry E Kiselyov is tracked because the handle DEK-RIPE could influence registry matters for AS210928 if the record is active, and any change in routing status or contact details could shift the autonomous system from a dormant asset to an operational factor requiring monitoring.

Watchpoints

The handle DEK-RIPE represents a dormant registry contact with no current operational leverage. However, the mere existence of an assigned ASN with an unverified contact is a long-term watch item because the ASN could be activated and used in ways that create routing dependencies or security concerns. The strategic value is early detection: any change signals potential infrastructure movement.

Monitor RIPE DB for changes to DEK-RIPE's associated entities; track BGP announcements from AS210928 via public route collectors; search for corporate registrations, PeeringDB entries, or professional profiles linking the name Dmitry E Kiselyov to IT organizations; verify if the handle becomes unused or is transferred.

No employer, geographic location, or organizational affiliation is publicly known. No biographical or professional profiles exist. The handle's creation date and last update are not verified. No active BGP data. No contact email or phone is publicly visible outside the registry. These gaps prevent confidence in the subject's real-world identity and authority.

Sources

• Registry RDAP / WHOIS record - The RDAP record for AS210928 lists Dmitry E Kiselyov as administrative and technical contact with handle DEK-RIPE.
• bgp.he.net - The bgp.he.net page for AS210928 confirms the autonomous system exists and is assigned but shows no prefix announcements.
• RIPE registry record - RIPE Stat provides an official overview of AS210928, corroborating its assignment and the current absence of announced prefixes.