Core Entity Brief
| Entity | Thomas Heinzmann |
|---|---|
| Public role | Monitoring the registry contact allows analysts to detect changes in AS212009's resource attribution or custodianship. If linked to a known operator or if the ASN begins originating prefixes, the contact could become operationally significant for routing analysis. |
| 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 | 1 public source reference |
| Related coverage | Profile anchor article |
| Website | Public evidence pending |
| Last update | Jun 03, 2026 |
Thomas Heinzmann is an individual registry contact, not a corporate entity; no commercial business model or corporate structure is evidenced.
What It Does
- Registry contact role: The person is listed as admin and tech contact for AS212009, implying a formal relationship with the autonomous system's resource holder, but no commercial activity is established.
- Absence of revenue evidence: No supplied evidence indicates any revenue, customers, contracts, or commercial operations associated with the subject.
Operating Snapshot
- Registry signal: The only operational signal is the RDAP entry; no routing, peering, or service activity is detected.
- No routing footprint: AS212009 does not originate prefixes, and the subject has no associated network infrastructure in public routing data.
Control Surface
- Registry record: The contact designation is the sole checkable control surface; any change in the RIPE registry would alter the assessment of the subject's role.
Watchpoints
- Record changes: Modifications to the RDAP entry, such as removal or update of the contact, would signal a change in resource attribution.
- Routing emergence: If AS212009 starts announcing prefixes, the subject’s potential operational significance increases.

