McAfee-CSP-JP

BGP inherited
Cluster stats
Netblocks8
All fragments 96 blocks across 18 clusters
Cluster ID210664423
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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 (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
185.221.70.1/32 McAfee-CSP-JP RIPE LIR-PARTITIONED PA ● low
185.221.70.2/32 McAfee-CSP-JP RIPE LIR-PARTITIONED PA ● low
185.221.70.3/32 McAfee-CSP-JP RIPE LIR-PARTITIONED PA ● low
185.221.70.4/32 McAfee-CSP-JP RIPE LIR-PARTITIONED PA ● low
185.221.70.12/32 McAfee-CSP-JP RIPE LIR-PARTITIONED PA ● low
185.221.70.13/32 McAfee-CSP-JP RIPE LIR-PARTITIONED PA ● low
185.221.70.14/32 McAfee-CSP-JP RIPE LIR-PARTITIONED PA ● low
185.221.70.15/32 McAfee-CSP-JP RIPE LIR-PARTITIONED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “McAfee CSP” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Combined view of all 18 name-family clusters →
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE SKYHIGH-SECURITY-MNT