Gemeente Dinkelland
BGP inherited
Cluster stats
| Netblocks | 3 |
| All fragments | 1,533 blocks across 321 clusters |
| Cluster ID | 192186682 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 6 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 212.178.65.32/28 | GEMEENTE-DINKELLAND | RIPE | ASSIGNED PA | ● low |
| 2a07:3500:1b30::/46 | Gemeente Dinkelland | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a07:3500:1b30::/48 | Gemeente Dinkelland | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(2 of 3)
Possible discrepancies (1)
These blocks are registered to Gemeente Dinkelland but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2a07:3500:1b30::/48 /48 | authorized for AS1136 — KPN B.V. |
NIC Handles
DUMY-RIPE
DUMY-RIPE
KPN-MNT
LOGIUS
ORG-GD145-RIPE
ZIGGO-AUTOREG1