JMP-CORE
Unresolved
Cluster stats
| Netblocks | 5 |
| All fragments | 75 blocks across 9 clusters |
| Cluster ID | 194168200 |
| 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 (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a0a:d6c0::/48 | JMP-CORE | RIPE | ASSIGNED | ● low |
| 2a0a:d6c0:2::/48 | JMP-CORE | RIPE | ASSIGNED | ● low |
| 2a0a:d6c0:3::/48 | JMP-CORE | RIPE | ASSIGNED | ● low |
| 2a0a:d6c0:4::/48 | JMP-CORE | RIPE | ASSIGNED | ● low |
| 2a0a:d6c0:6::/48 | JMP-CORE | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(5 of 5)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
ch-jmptechnology-1-mnt