Core Entity Brief
| Entity | Julian Kuhn |
|---|---|
| Public role | Julian Kuhn is a person name in public internet-number registry data as the holder of RIPE entity handle JK16176-RIPE. If the same person remains listed in authoritative registry data, analysts can map responsibility and escalation paths for AS210235. The evidence supports dependency review at the registry-contact layer, not attribution of operational control. |
| Region | Global |
| Category | Individual registry-holder label |
| Primary domain | Infrastructure |
| Signal focus | Institution Type |
| Time horizon | Quarter (30-120d) |
| Impact | Medium |
| Confidence | 0.95 |
| Evidence coverage | 3 public source references |
| Related coverage | Profile anchor article |
| Website | Public evidence pending |
| Last update | Jun 02, 2026 |
Julian Kuhn is an individual whose public internet infrastructure footprint is limited to a registry contact role for AS210235.
What It Does
- Registry contact role: Julian Kuhn serves as the administrative and technical contact for AS210235, designated for official communications. No revenue or commercial operation is associated with this role.
Operating Snapshot
- Person, not organization: Julian Kuhn is a human being whose public footprint is limited to a registry contact listing for AS210235.
- No active routing: AS210235 has no observed BGP announcements, limiting the operational context of the contact role.
Control Surface
- Registry contact entry: The sole verifiable control surface is the contact entry in the AS210235 registration record. It designates Julian Kuhn as the recipient for registry queries but does not imply control over routing or infrastructure.
Watchpoints
- Record freshness: Stale, conflicting, or changed public records are the main uncertainty when translating source evidence into an operating profile.
- Footprint change: New ASN, prefix, official website, PeeringDB, or registry evidence would raise or lower Julian Kuhn's infrastructure relevance.

