nl-kruyswijk-ict
Unresolved
Cluster stats
| Netblocks | 2 |
| All fragments | 11,902 blocks across 6,389 clusters |
| Cluster ID | 194121185 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 31.22.86.240/28 | nl-kruyswijk-ict | RIPE | ASSIGNED PA | ● low |
| 2a00:1188:13::/48 | nl-kruyswijk-ict | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
Possible discrepancies (1)
These blocks are registered to nl-kruyswijk-ict 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.
| 2a00:1188:13::/48 /48 | authorized for AS8455 — atom86 BV |
NIC Handles
ATOM86-MNT
DUMY-RIPE
DUMY-RIPE