Autonomous system
AS201329 reinachbl Gemeinde Reinach BL
Unclassified RIPE Enterprise
Summary
Gemeinde Reinach BL
government municipal switzerland
The AS handle REINACHBL is held by Gemeinde Reinach BL.
What it's used for
- The address space carries municipal infrastructure, identified by the netname
CH-REINACHBL-20180702and registrantGemeinde Reinach BL. - The inventory consists of 1024 IPv4 addresses within a single prefix, 162.12.200.0/22, with 2 observed neighbours.
- Traffic from this network represents internal communications and services for the municipality of Reinach in the Canton of Basel-Landschaft.
Notable
- The RDAP registrant
Gemeinde Reinach BLaligns directly with the AS holder and the registry name. - The address inventory is a single contiguous /22 block, consistent with a small-scale internal corporate or municipal estate rather than a public access network.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-11-02, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 1 prefixes · 1.02K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| CH | Switzerland | 1 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS201329- Registry name
- reinachbl
- Registrant
- ch-reinachbl-1-mnt
- Abuse contact
- helpdesk@reinach-bl.ch
- Registered
- 2018-07-02
- Last changed
- 2018-09-04
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- reinachbl
- Also known as
- reinachbl
- Network type
- Enterprise
- Scope
- Regional
- Traffic ratio
- Mostly Outbound
- Peering policy
- Open
- Website
- http://www.reinach-bl.ch
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 0% valid · 0 valid, 1 with no ROA
- ROAs
- 0 authorising AS201329
- ASPA
- no ASPA record
- IRR
- 100% registered · 1 of 1 announcements
- Route objects
- 3 naming AS201329
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 449 networks and 1,846 prefixes, as published 2026-11-03. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere