Sincan_belediye_baskanligi
BGP inherited
Cluster stats
| Netblocks | 4 |
| Cluster ID | 209876092 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 88.255.151.128/28 | Sincan_belediye_baskanligi | RIPE | ASSIGNED PA | ● low |
| 95.0.152.216/29 | Sincan_belediye_baskanligi | RIPE | ASSIGNED PA | ● low |
| 212.174.59.64/26 | Sincan_Belediye_Baskanligi | RIPE | ASSIGNED PA | ● low |
| 2a01:358:4014:b00::/56 | Sincan_Belediye_Baskanligi | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
Possible discrepancies (1)
These blocks are registered to Sincan_belediye_baskanligi 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.
| 2a01:358:4014:b00::/56 /56 | authorized for AS9121 — Turk Telekomunikasyon Anonim Sirketi |
NIC Handles
AS9121-MNT
DUMY-RIPE
DUMY-RIPE