cc-FAW-COM
Cluster stats
| Netblocks | 18 |
| All fragments | 7,757 blocks across 6,229 clusters |
| Cluster ID | 193136655 |
| Registry | APNIC |
| 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 (18)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 221.8.0.0/24 | cc-FAW-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 221.8.1.0/24 | cc-FAW-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 221.8.2.0/24 | cc-FAW-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 221.8.3.0/24 | cc-FAW-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 221.8.4.0/24 | cc-FAW-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 221.8.5.0/24 | cc-FAW-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 221.8.6.0/24 | cc-FAW-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 221.8.7.0/24 | cc-FAW-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 221.8.8.0/24 | cc-FAW-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 221.8.9.0/24 | cc-FAW-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 221.8.40.0/24 | cc-FAW-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 221.8.41.0/24 | cc-FAW-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 221.8.42.0/24 | cc-FAW-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 221.8.43.0/24 | cc-FAW-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 221.8.44.0/24 | cc-FAW-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 221.8.45.0/24 | cc-FAW-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 221.8.46.0/24 | cc-FAW-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 221.8.47.0/24 | cc-FAW-COM | APNIC | ASSIGNED NON-PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(18 of 18)
RPKI-inferred operator
CNCGROUP IP network of ShangHai IDC
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-CNCGROUP-JL
XY371-AP
XY371-AP