Kantonspolizei Zürich holds AS210378 (KNET) and uses the Network Operation registry contact to maintain a RIPE NCC presence. Three public sources link the police force to the ASN, confirming a government-owned internet number resource. The ASN’s routing status is unobserved in supplied evidence, confining the current profile to registry stewardship. Watchpoints include RDAP record changes, prefix announcements, and any official documentation. Uncertainty persists around the police force’s internal team and strategic purpose for the ASN.

Kantonspolizei Zürich

Kantonspolizei Zürich, the Zurich Cantonal Police, holds Autonomous System 210378 (KNET) and maintains the registry contact label “Network Operation” for administrative, technical, and abuse functions. Public sources link the police force to this internet number resource, providing a verifiable attribution point for infrastructure monitoring and abuse reporting, though the ASN’s routing status remains unobserved from supplied evidence.

Why It Matters

The practical impact is currently limited to registry governance and abuse handling, as no IP prefixes are announced in the provided evidence. However, the first routing update or a contact detail change would immediately alter the public attribution, potentially revealing new operational capabilities or organisational changes within the police force.

What Sources Show

Kantonspolizei Zürich, the Zurich Cantonal Police, publicly registers Autonomous System 210378 (KNET). The RIPE NCC record lists “Network Operation” as the administrative, technical, and abuse contact. This label is not a separate company; it is a role account maintained by the police force’s network operations staff. The contact email and phone link directly to the police authority through official domain and directory sources.

The registry attribution allows network analysts and security staff to assign responsibility for the ASN to a specific government body. If the ASN were ever used for routing, that link would become an operational dependency for threat intelligence, abuse handling, and service mapping. Even in a dormant state, the record serves as a public reference for the police force’s presence in the internet numbering ecosystem.

The RDAP lookup at rdap.org displays the AS210378 entry with contact handles under the name Network Operation, using an email at kapo.zh.ch. The official Kantonspolizei Zürich website (www.kapo.zh.ch) confirms that domain. A Swiss directory (search.ch) ties the listed phone number to the same authority. These three sources converge, yet no direct police IT webpage mentions the ASN outright.

Evidence gaps: The supplied evidence does not include BGP routing tables, so the current operational state of AS210378 is unobserved. There is no PeeringDB entry and no official documentation from the police that explicitly confirms the ASN’s purpose. The internal team or department responsible is not identified. These gaps confine the assessment to registry-level stewardship rather than live network operations.

Control surface: The RIPE NCC database entry for AS210378 is the primary control point. Authorised personnel can alter the admin, tech, and abuse contact details, the AS name, or the affiliated organisation, directly changing public attribution. The domain and phone provide corroboration but are managed separately. No active routing control points exist in the available evidence.

Several concrete events would alter the profile. A change to the RDAP contact handles, AS name, or maintainer could signal a transfer or restructuring. The first IP prefix originated by AS210378 would shift the role from dormant registry to active network node. A PeeringDB record or police IT publication would offer stronger verification. ASN transfer or de‑registration would break the current linkage.

The police force’s exact motivation for holding the ASN—future connectivity, a reservation, or legacy practice—is not public. The individuals behind the Network Operation label are anonymous; the role may be shared among several IT officers. Until routing activity appears or official statements clarify the purpose, the intelligence value rests on registry maintenance and attribution capability rather than live network insight.

Operating Surface

The police force acts as the holder of AS210378, using the Network Operation role to satisfy RIPE NCC registration requirements. Although the role does not involve active routing management at this time, it establishes the canton’s law-enforcement agency within the internet numbering system, enabling abuse complaint routing and resource stewardship.

Monitoring this police‑held ASN matters because any future registry change or routing announcement would signal shifts in the internet infrastructure posture of Zurich Cantonal Police, supporting dependency mapping, abuse contact tracking, and oversight of government‑controlled number resources.

Watchpoints

The registry entry anchors a Swiss law‑enforcement body within the internet numbering ecosystem, providing a stable attribution point even in the absence of active routing. Should the police force activate the ASN, it would move from a dormant registry artefact to a live operational node, potentially with government interconnections that demand monitoring.

Any alteration of the RDAP contact details, AS name, or maintainer object could indicate an organisational change or ASN transfer. The appearance of BGP announcements for AS210378 would dramatically escalate the entity’s operational relevance and require immediate dependency mapping. Publication of a PeeringDB entry or official police network documentation would strengthen the attribution.

Direct confirmation from Kantonspolizei Zürich that it operates AS210378 is missing. The absence of routing data prevents assessment of the network’s scale, upstream providers, or actual usage. Internal team composition and the ASN’s intended purpose (future services, private connectivity, or legacy reservation) remain undisclosed.

Sources

• Registry RDAP / WHOIS record - Public RDAP record for AS210378 showing Network Operation as admin, tech, and abuse contact, with a kapo.zh.ch email.
• Operator website - The official website for Kantonspolizei Zürich establishes kapo.zh.ch as the official web domain of Zurich Cantonal Police, matching the domain visible in the RDAP contact email.
• search.ch - A public Swiss directory page associates published published contact points with Kantonspolizei Zürich, supporting the registry phone number's linkage to the same organization context.