STLSEC-HK
BGP inherited
Limited data: only 3 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
| Netblocks | 3 |
| Cluster ID | 193180869 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 5 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 125.215.216.64/28 | STLSEC-HK | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 202.82.202.200/30 | STLSEC-HK | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 218.103.84.192/28 | STLSEC-HK | APNIC | ASSIGNED NON-PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: D
how networks compare →
33.3%
of checked blocks have valid RPKI ROA coverage
(1 of 3)
No discrepancies found among checked blocks.
NIC Handles
AP706-AP
BNA2-AP
MAINT-HK-IMS-CS
MAINT-HK-PCCW-BIA-CS
TA66-AP