PUBLIC-SECURITY

BGP inherited
Cluster stats
Netblocks6
Registered in China (3) · Saudi Arabia (3)
All fragments 14 blocks across 8 clusters
Cluster ID210201514
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 8 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

3 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-12

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
61.175.98.140/30 PUBLIC-SECURITY APNIC ASSIGNED NON-PORTABLE ● high
61.175.100.64/29 PUBLIC-SECURITY APNIC ASSIGNED NON-PORTABLE ● high
61.175.101.52/30 PUBLIC-SECURITY APNIC ASSIGNED NON-PORTABLE ● high
5.42.239.144/28 Public-Security RIPE ASSIGNED PA ● low
87.101.152.168/30 Public-Security RIPE ASSIGNED PA ● low
87.101.227.208/28 Public-Security RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “PUBLIC SECURITY” — 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.
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 (6 of 6)
No discrepancies found among checked blocks.

NIC Handles

AC1602-AP CZ6-AP DUMY-RIPE DUMY-RIPE GZ1035-AP ITC-NOC-MNT MAINT-CN-CHINANET-ZJ-ZS ZL2368-AP