i4HK Limited
RUBYCOURT-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 | 206875601 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 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 |
|---|---|---|---|---|
| 43.251.35.0/24 | RUBYCOURT-HK | APNIC | ALLOCATED NON-PORTABLE | ● low |
| 43.252.171.0/24 | RUBYCOURT-HK | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 122.115.77.0/24 | RUBYCOURT-HK | APNIC | ALLOCATED 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)
RPKI-inferred operator
i4HK Limited
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
MAINT-HK-ISP
RC1503-AP
RC1503-AP
RC1503-AP