BAIDU-LTD-BJ
Cluster stats
| Netblocks | 6 |
| All fragments | 8 blocks across 2 clusters |
| Cluster ID | 194352702 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
2 weekly snapshots · JSON
6
0 netblocks since 2026-07-05
2026-07-05
peak 6
2026-07-06
IP Ranges (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 61.181.16.96/30 | BAIDU-LTD-BJ | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 61.181.16.100/30 | BAIDU-LTD-BJ | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 111.161.35.0/24 | Baidu-Ltd-Bj | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 125.39.78.0/23 | Baidu-Ltd-Bj | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 125.39.81.20/30 | BAIDU-LTD-BJ | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 125.39.81.148/30 | BAIDU-LTD-BJ | 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
(6 of 6)
Possible discrepancies (2)
These blocks are registered to BAIDU-LTD-BJ 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.
| 125.39.78.0/23 /23 | authorized for AS4837 — CNCGROUP IP network of ShangHai IDC |
| 111.161.35.0/24 /24 | authorized for AS4837 — CNCGROUP IP network of ShangHai IDC |
NIC Handles
AC2798-AP
HZ19-AP
HZ19-AP
MAINT-CNCGROUP-TJ