Skip to content
https://baidu.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
72
GRADE
C
FIX
2
REVIEW
5
PASS
2
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
2 PASS 5 REVIEW 2 FIX
D
Crawlability
Action
robots.txt present, no sitemap
FIX
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 2814 bytes
Critical::
robots.txt blocks all crawlers
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

Why this matters

Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.

Learn more ▾

Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.

Source: Google Search Central

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 2814 B Sitemaps referenced 0 User-agents Googlebot, Sogou News Spider, Sogou web spider, Sogou blog, Sosospider, MSNBot, Baiduspider-image, Sogou spider2, Sogou Orion spider, Baiduspider, YoudaoBot, Sogou inst spider, ChinasoSpider, yisouspider, EasouSpider, * Blocking Yes — all crawlers blocked
User-agent: Baiduspider
Disallow: /baidu
Disallow: /s?
Disallow: /ulink?
Disallow: /link?
Disallow: /home/news/data/
Disallow: /bh

User-agent: Googlebot
Disallow: /baidu
Disallow: /s?
Disallow: /shifen/
Disallow: /homepage/
Disallow: /cpro
Disallow: /ulink?
Disallow: /link?
Disallow: /home/news/data/
Disallow: /bh

User-agent: MSNBot
Disallow: /baidu
Disallow: /s?
Disallow: /shifen/
Disallow: /homepage/
Disallow: /cpro
Disallow: /ulink?
Disallow: /link?
Disallow: /home/news/data/
Disallow: /bh

User-agent: Baiduspider-image
Disallow: /baidu
Disallow: /s?
Disallow: /shifen/
Disallow: /homepage/
Disallow: /cpro
Disallow: /ulink?
Disallow: /link?
Disallow: /home/news/data/
Disallow: /bh

User-agent: YoudaoBot
Disallow: /baidu
Disallow: /s?
Disallow: /shifen/
Disallow: /homepage/
Disallow: /cpro
Disallow: /ulink?
Disallow: /link?
Disallow: /home/news/data/
Disallow: /bh

User-agent: Sogou web spider
Disallow: /baidu
Disallow: /s?
Disallow: /shifen/
Disallow: /homepage/
Disallow: /cpro
Disallow: /ulink?
Disallow: /link?
Disallow: /home/news/data/
Disallow: /bh

User-agent: Sogou inst spider
Disallow: /baidu
Disallow: /s?
Disallow: /shifen/
Disallow: /homepage/
Disallow: /cpro
Disallow: /ulink?
Disallow: /link?
Disallow: /home/news/data/
Disallow: /bh

User-agent: Sogou spider2
Disallow: /baidu
Disallow: /s?
Disallow: /shifen/
Disallow: /homepage/
Disallow: /cpro
Disallow: /ulink?
Disallow: /link?
Disallow: /home/news/data/
Disallow: /bh

User-agent: Sogou blog
Disallow: /baidu
Disallow: /s?
Disallow: /shifen/
Disallow: /homepage/
Disallow: /cpro
Disallow: /ulink?
Disallow: /link?
Disallow: /home/news/data/
Disallow: /bh

User-agent: Sogou News Spider
Disallow: /baidu
Disallow: /s?
Disallow: /shifen/
Disallow: /homepage/
Disallow: /cpro
Disallow: /ulink?
Disallow: /link?
Disallow: /home/news/data/
Disallow: /bh

User-agent: Sogou Orion spider
Disallow: /baidu
Disallow: /s?
Disallow: /shifen/
Disallow: /homepage/
Disallow: /cpro
Disallow: /ulink?
Disallow: /link?
Disallow: /home/news/data/
Disallow: /bh

User-agent: ChinasoSpider
Disallow: /baidu
Disallow: /s?
Disallow: /shifen/
Disallow: /homepage/
Disallow: /cpro
Disallow: /ulink?
Disallow: /link?
Disallow: /home/news/data/
Disallow: /bh

User-agent: Sosospider
Disallow: /baidu
Disallow: /s?
Disallow: /shifen/
Disallow: /homepage/
Disallow: /cpro
Disallow: /ulink?
Disallow: /link?
Disallow: /home/news/data/
Disallow: /bh


User-agent: yisouspider
Disallow: /baidu
Disallow: /s?
Disallow: /shifen/
Disallow: /homepage/
Disallow: /cpro
Disallow: /ulink?
Disallow: /link?
Disallow: /home/news/data/
Disallow: /bh

User-agent: EasouSpider
Disallow: /baidu
Disallow: /s?
Disallow: /shifen/
Disallow: /homepage/
Disallow: /cpro
Disallow: /ulink?
Disallow: /link?
Disallow: /home/news/data/
Disallow: /bh

User-agent: *
Disallow: /
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
Redirect Chain
1 redirect(s), 3015 ms total
REVIEW
1 redirect(s), 3015 ms total
Info::
Single redirect
Got: https://baidu.com → https://www.baidu.com/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 3015 ms total
Got: 3015 ms

https://baidu.com

1668 ms · HTTP/1.1

301

https://www.baidu.com/

1347 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://baidu.com3011668 msHTTP/1.1
2https://www.baidu.com/2001347 msHTTP/1.1BWS/1.1

See the visual redirect chain in the HTTP Probe tab →

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.baidu.com/
200https://baidu.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://baidu.com/ → https://www.baidu.com/

Consistent

C
HTTP Probe Timing
Action
Total 1821 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
18 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
224 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
1.35 s
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.82 s
Total Time Total request time from DNS lookup through full response.
1.82 s

Connection waterfall

DNS Lookup 18 ms TCP Connect 224 ms TLS Handshake 1.35 s Server Processing 225 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
321 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

321
days left
0d 30d 60d 90d+

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A
DNS Records
4 A records, 222 ms lookup
PASS
4 A records, 222 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 111.63.65.103, 110.242.74.102, 124.237.177.164, 111.63.65.247
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: ns2.baidu.com, ns7.baidu.com, ns4.baidu.com, ns3.baidu.com, dns.baidu.com
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (222 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 222 ms
A111.63.65.103, 110.242.74.102, 124.237.177.164, 111.63.65.247
AAAA—
CNAME—
NSns2.baidu.com, ns7.baidu.com, ns4.baidu.com, ns3.baidu.com, dns.baidu.com
MX
10 mx.maillb.baidu.com
20 mx.baidu.com
TXT
google-site-verification=GHb98-6msqyx_qqjGl5eRatD3QTHyVB6-xQ3gJB5UwM
9279nznttl321bxp1j464rd9vpps246v
SPF v=spf1 include:spf1.baidu.com include:spf2.baidu.com include:spf3.baidu.com incl...
_globalsign-domain-verification=qjb28W2jJSrWj04NHpB0CvgK9tle5JkOq-EcyWBgnE
CAALookup not available with standard resolver
Resolved in 222 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Domain Intelligence
baidu.com — via MarkMonitor Information Technology (Shanghai) Co., Ltd., 26 years, 10 months old, hosted on CMNET-V4HEBEI-AS-AP Hebei Mobile Communication Company Limited, CN
PASS
baidu.com — via MarkMonitor Information Technology (Shanghai) Co., Ltd., 26 years, 10 months old, hosted on CMNET-V4HEBEI-AS-AP Hebei Mobile Communication Company Limited, CN
Info::
Domain registered until Oct 11, 2028 (2 years, 6 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: MarkMonitor Information Technology (Shanghai) Co., Ltd.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: CMNET-V4HEBEI-AS-AP Hebei Mobile Communication Company Limited, CN
Got: AS24547
Domain expiry

822 days

October 11, 2028

SSL certificate

321 days

Issued by DigiCert, Inc.

Domain age

26 years, 10 months

Registered October 11, 1999

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

CMNET-V4HEBEI-AS-AP Hebei Mobile Communication Company Limited, CN

ASN AS24547

111.63.65.103

Registrar

MarkMonitor Information Technology (Shanghai) Co., Ltd.

Unlocked 5 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Information Technology (Shanghai) Co., Ltd.
Created October 11, 1999 (26 years, 10 months ago)
Expires October 11, 2028 (2 years, 6 months)
Last Updated April 8, 2025
Name Servers ns1.baidu.com, ns2.baidu.com, ns3.baidu.com, ns4.baidu.com, ns7.baidu.com
DNSSEC Not enabled
Hosting
IP Address 111.63.65.103
ASN AS24547 (CMNET-V4HEBEI-AS-AP Hebei Mobile Communication Company Limited, CN)
Provider CMNET-V4HEBEI-AS-AP Hebei Mobile Communication Company Limited, CN
Data source: rdap (0.4s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback