HUBEI-UNICOM-THIRD-GENRATION-INTERNET — IP ranges & network footprint

IP Ranges (2)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
113.57.244.0/22	HUBEI-UNICOM-THIRD-GENRATION-INTERNET	APNIC	ASSIGNED NON-PORTABLE	● low
113.57.250.0/23	HUBEI-UNICOM-THIRD-GENRATION-INTERNET	APNIC	ASSIGNED NON-PORTABLE	● low

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “HUBEI UNICOM” — 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.

HUBEI-UNICOM-PRODUCT-AND-CREATIVE-DEPARTMENT 1 blocks
Hubei-unicom-Management-Information-Systems-Department 1 blocks

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.

HUBEI-UNICOM-PRODUCT-AND-CREATIVE-DEPARTMENT via CNCGROUP IP network of ShangHai IDC sub-allocation
Hubei-unicom-Management-Information-Systems-Department via CNCGROUP IP network of ShangHai IDC sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

100.0% of checked blocks have valid RPKI ROA coverage (2 of 2)

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-HB YH1396-AP YH1396-AP

Netblocks	2 · 1,534 IPv4 addresses
All fragments	4 blocks across 3 clusters
Cluster ID	210334972
Registry	APNIC
Customers	find customers using this network →

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