MINGNAN-INTERCOM-CN
BGP inherited
Cluster stats
| Netblocks | 5 · 506 IPv4 addresses |
| Cluster ID | 210234383 |
| 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 (5)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 203.196.3.0/26 | MINGNAN-INTERCOM-CN | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 203.196.3.0/24 | MINGNAN-INTERCOM-CN | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 203.196.3.64/26 | MINGNAN-INTERCOM-CN | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 203.196.3.128/26 | MINGNAN-INTERCOM-CN | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 203.196.3.192 – 203.196.3.254 | MINGNAN-INTERCOM-CN | 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
(5 of 5)
Possible discrepancies (1)
These blocks are registered to MINGNAN-INTERCOM-CN but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 203.196.3.0/24 /24 | authorized for AS4808 — China Unicom |
NIC Handles
AC1601-AP
JJ1-CN
Jj596-AP
MAINT-CNNIC-AP
SG1-AP