BAIDU, INC.
Baidu, Inc.
LEI
254900AL64IANZYI1E02
Registered name
BAIDU, INC.
Jurisdiction
Ultimate parent
No parent on file in GLEIF
Cluster stats
| Netblocks | 62 |
| Cluster ID | 191707561 |
| Registry | APNIC |
| Owner jurisdiction | KY |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Legal identity | LEI 254900AL64IANZYI1E02 |
| Shared handles | clustered on 44 shared RIR contact/maintainer handles |
| Registry names | 9 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (62)
showing 50 of 62 — see all — ⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 27.111.228.237/32 | Baidu | PEERINGDB | ASSIGNED | ● high |
| 27.111.229.24/32 | Baidu | PEERINGDB | ASSIGNED | ● high |
| 36.255.56.217/32 | Baidu | PEERINGDB | ASSIGNED | ● high |
| 36.255.57.44/32 | Baidu | PEERINGDB | ASSIGNED | ● high |
| 61.135.185.0/24 | baidu | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 61.135.186.0/24 | baidu | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 80.81.192.122/32 | Baidu | PEERINGDB | ASSIGNED | ● high |
| 101.203.88.216/32 | Baidu | PEERINGDB | ASSIGNED | ● high |
| 101.203.88.217/32 | Baidu | PEERINGDB | ASSIGNED | ● high |
| 103.231.152.87/32 | Baidu | PEERINGDB | ASSIGNED | ● high |
| 115.239.209.0/27 | BAIDU-CO-LTD | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 115.239.209.32/27 | BAIDU-CO-LTD | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 116.247.112.144/28 | Baidu | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 119.63.192.0/21 | Baidu, Inc. | BGP | ANNOUNCED | ● high |
| 119.63.192.0/24 | Baidu, Inc. | BGP | ANNOUNCED | ● high |
| 119.63.193.0/24 | Baidu, Inc. | BGP | ANNOUNCED | ● high |
| 119.63.194.0/24 | Baidu, Inc. | BGP | ANNOUNCED | ● high |
| 119.63.195.0/24 | Baidu, Inc. | BGP | ANNOUNCED | ● high |
| 119.63.196.0/24 | Baidu, Inc. | BGP | ANNOUNCED | ● high |
| 119.63.197.0/24 | Baidu, Inc. | BGP | ANNOUNCED | ● high |
| 119.63.198.0/24 | Baidu, Inc. | BGP | ANNOUNCED | ● high |
| 119.63.199.0/24 | Baidu, Inc. | BGP | ANNOUNCED | ● high |
| 123.124.229.176/28 | BAIDU-CO | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 123.255.90.131/32 | Baidu | PEERINGDB | ASSIGNED | ● high |
| 123.255.91.61/32 | Baidu | PEERINGDB | ASSIGNED | ● high |
| 206.51.40.43/32 | Baidu | PEERINGDB | ASSIGNED | ● high |
| 2001:504:13:1::43/128 | Baidu | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8::da9f:0:1/128 | Baidu | PEERINGDB | ASSIGNED | ● high |
| 2001:7fa:0:1::ca28:a083/128 | Baidu | PEERINGDB | ASSIGNED | ● high |
| 2001:7fa:0:1::ca28:a13d/128 | Baidu | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:4::5:5967:1/128 | Baidu | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:4::5:5967:2/128 | Baidu | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:7::5:5967:3/128 | Baidu | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:7::5:5967:4/128 | Baidu | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:c::5:5967:1/128 | Baidu | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:c::5:5967:2/128 | Baidu | PEERINGDB | ASSIGNED | ● high |
| 2001:df5:b800:bb00:0:5:5967:1/128 | Baidu | PEERINGDB | ASSIGNED | ● high |
| 42.199.0.0/16 | Baidu | APNIC | ALLOCATED PORTABLE | ● low |
| 45.113.192.0/22 | Baidu (Hong Kong) Limited | APNIC | ALLOCATED PORTABLE | ● low |
| 58.252.73.104/32 | Baidu | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 101.247.0.0/17 | Baidu | APNIC | ALLOCATED PORTABLE | ● low |
| 103.6.76.0/22 | Baidu | APNIC | ALLOCATED PORTABLE | ● low |
| 103.125.44.0/22 | BAIDU-CLOUD | APNIC | ALLOCATED PORTABLE | ● low |
| 103.235.44.0/22 | Baidu (Hong Kong) Limited | APNIC | ASSIGNED PORTABLE | ● low |
| 106.12.0.0/15 | Baidu | APNIC | ALLOCATED PORTABLE | ● low |
| 114.110.64.0/18 | Baidu | APNIC | ALLOCATED PORTABLE | ● low |
| 114.111.0.0/19 | Baidu | APNIC | ALLOCATED PORTABLE | ● low |
| 117.58.0.0/17 | Baidu | APNIC | ALLOCATED PORTABLE | ● low |
| 119.75.208.0/20 | Baidu | APNIC | ALLOCATED PORTABLE | ● low |
| 120.48.0.0/15 | Baidu | APNIC | ALLOCATED PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
54.8%
of checked blocks have valid RPKI ROA coverage
(34 of 62)
Possible discrepancies (2)
These blocks are registered to Baidu, Inc. 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.
| 61.135.186.0/24 /24 | authorized for AS4808 — China Unicom |
| 61.135.185.0/24 /24 | authorized for AS4808 — China Unicom |
NIC Handles
AB1359-AP
AC1591-AP
AC1601-AP
AC1602-AP
AC1718-AP
APNIC-HM
AS38627
AS55967
BHKL1-AP
BHKL1-AP
BN261-AP
BN261-AP
+32 more