MILKY-JEROMEDAVID
Handle
Cluster stats
| Netblocks | 16 |
| All fragments | 31 blocks across 16 clusters |
| Cluster ID | 191819340 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | RIR handle |
| 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 | |
Footprint over time
2 weekly snapshots · JSON
16
0 netblocks since 2026-07-05
2026-07-05
peak 16
2026-07-06
IP Ranges (16)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a0e:e704:60::/48 | MILKY-JEROMEDAVID | RIPE | ASSIGNED | ● low |
| 2a0e:e704:61::/48 | MILKY-JEROMEDAVID | RIPE | ASSIGNED | ● low |
| 2a0e:e704:62::/48 | MILKY-JEROMEDAVID | RIPE | ASSIGNED | ● low |
| 2a0e:e704:63::/48 | MILKY-JEROMEDAVID | RIPE | ASSIGNED | ● low |
| 2a0e:e704:64::/48 | MILKY-JEROMEDAVID | RIPE | ASSIGNED | ● low |
| 2a0e:e704:65::/48 | MILKY-JEROMEDAVID | RIPE | ASSIGNED | ● low |
| 2a0e:e704:66::/48 | MILKY-JEROMEDAVID | RIPE | ASSIGNED | ● low |
| 2a0e:e704:67::/48 | MILKY-JEROMEDAVID | RIPE | ASSIGNED | ● low |
| 2a0e:e704:68::/48 | MILKY-JEROMEDAVID | RIPE | ASSIGNED | ● low |
| 2a0e:e704:69::/48 | MILKY-JEROMEDAVID | RIPE | ASSIGNED | ● low |
| 2a0e:e704:6a::/48 | MILKY-JEROMEDAVID | RIPE | ASSIGNED | ● low |
| 2a0e:e704:6b::/48 | MILKY-JEROMEDAVID | RIPE | ASSIGNED | ● low |
| 2a0e:e704:6c::/48 | MILKY-JEROMEDAVID | RIPE | ASSIGNED | ● low |
| 2a0e:e704:6d::/48 | MILKY-JEROMEDAVID | RIPE | ASSIGNED | ● low |
| 2a0e:e704:6e::/48 | MILKY-JEROMEDAVID | RIPE | ASSIGNED | ● low |
| 2a0e:e704:6f::/48 | MILKY-JEROMEDAVID | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(16 of 16)
RPKI-inferred operator
ServerHouse Ltd
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
MILKYWAN-MNT