tbondmntr

tbondmntr is a single-record RIPE NCC registry entity serving as admin/tech contact for AS210917. The evidence is a public RDAP lookup; no website, PeeringDB, or BGP data supports the handle. The entity's real-world identity, structure, and authority are unknown. Watchpoints include any modification to the handle or the emergence of new identifiers. The profile should be used as a monitoring baseline, not as confirmation of operational or commercial status.

tbondmntr

tbondmntr is a RIPE NCC registry entity serving as the administrative and technical contact for Autonomous System 210917, with no other public infrastructure footprint. The entire observable surface is a single RDAP record; no website, PeeringDB entry, or routing data links it to a commercial or operational network. See also: AER-CA LLC.

Why It Matters

Alteration or abandonment of the record could disrupt route coordination, abuse handling, and other operational processes tied to the autonomous system. The contact is a single point of failure for trusted communication with the ASN's administrator. See also: Tim Zuidema trading as TiZu.

What Sources Show

tbondmntr is a registry entity in the RIPE NCC WHOIS database, serving as the administrative and technical contact for Autonomous System 210917. The name appears only in this registry record; there is no independent network footprint such as ASN ownership, IP prefix announcements, or a PeeringDB entry. Its entire public operating surface is the contact handle TA7869-RIPE.

If the record is altered or deleted without proper transition, operators and peers who rely on the listed contact for routing coordination, abuse reporting, or legal notices could send communications to an outdated or malicious recipient, disrupting incident response and network operations for AS210917.

The sole public evidence is an RDAP lookup from rdap.org. It confirms the existence of entity handle TA7869-RIPE with the roles admin and tech. No corporate website, business registration, or professional network listing associates the name with a commercial entity, making it impossible to determine whether tbondmntr is a person, a role account, or an organization.

Control over the entity’s presence rests entirely with the RIPE database maintainer. Whoever holds the maintainer credentials can update the email, phone, or administrative details tied to AS210917. No corporate domain, service platform, or DNS zone has been linked to the handle, so external observability stops at the registry.

Three signals would change this assessment. A modification to the TA7869-RIPE entry—such as a new email or replacement—would indicate a change in AS210917 administration. The appearance of a website, PeeringDB network record, or direct ASN/prefix registration under the tbondmntr name would give it independent infrastructure relevance. Conversely, if the record remains static for years without new data, its monitoring priority would decline.

The evidence gap is significant. There is no information about the subject’s real-world identity, scope of authority, or any associated operations beyond the one ASN. Until additional public records emerge, the profile can only describe a registry pointer, not an organization with a defined mission or infrastructure role.

Operating Surface

The entity functions as a registry-level contact point for administrative and technical queries related to AS210917. It does not operate a network, announce BGP routes, or hold IP resources independently; its authority is limited to the contact handle in the RIPE database.

If the registry record is modified or deleted without proper transition, operators and peers relying on AS210917's contact information for routing coordination, abuse reporting, or legal notices could send communications to an outdated or malicious recipient, disrupting incident response and network operations.

Watchpoints

tbondmntr represents a minimal registry footprint; its importance hinges entirely on the continued accuracy of the contact data for AS210917. Without corroborating infrastructure, it should be treated as a high-uncertainty node with potential for disruptive misdirection if the record is altered.

Two signals would change the assessment: any modification to the TA7869-RIPE entry (email, phone, or maintainer), and the appearance of a website, PeeringDB listing, or direct ASN/prefix registration under the tbondmntr name. Prolonged dormancy without change would lower its monitoring priority.

No corporate website, business registration, or public company record. No routing data or PeeringDB entry. The nature of the entity (person, role account, organization) is unknown. No information on the scope of authority or decision-making power of this contact.

Sources

• Registry RDAP / WHOIS record - Confirms tbondmntr as the administrative and technical contact for AS210917 with entity handle TA7869-RIPE.