Infrastructure - https://weibo.com BeaverCheck Audit

D

Crawlability

Action

robots.txt present, sitemap with 0 URLs

FIX

robots.txt present, sitemap with 0 URLs

robots.txt is present

Got: 383 bytes

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.

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml is empty — no URLs found

An empty sitemap provides no value. Add <url> entries for your pages.

robots.txt references 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

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more ▾

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

robots.txt 200 OK

Size 383 B Sitemaps referenced 1 User-agents HaosouSpider, YisouSpider, 360Spider, bingbot, smspider, Baiduspider, Googlebot, *, Sogou web spider Blocking Yes — all crawlers blocked

Sitemap: https://weibo.com/sitemap.xml

User-Agent: Baiduspider

Disallow:

User-agent: 360Spider

Disallow:

User-agent: Googlebot

Disallow:

User-agent: *

Allow: /ads.txt

User-agent: Sogou web spider

Disallow:

User-agent: bingbot

Disallow:

User-agent: smspider

Disallow:

User-agent: HaosouSpider

Disallow:

User-agent: YisouSpider

Disallow:

User-agent: *

Disallow: /

sitemap.xml 200 OK

Type URL Set URLs 0 entries Valid XML Yes

D

CDN & Delivery

Action

No CDN detected

FIX

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), 2436 ms total

REVIEW

1 redirect(s), 2436 ms total

Single redirect

Got: https://weibo.com → https://passport.weibo.com/visitor/visitor?entry=miniblog&a=enter&url=https%3A%2F%2Fweibo.com%2F&domain=weibo.com&ua=Mozilla%2F5.0%20%28compatible%3B%20BeaverCheck%2F1.0%3B%20%2Bhttps%3A%2F%2Fbeavercheck.com%29&_rand=1776360077560&sudaref= (302)

Uses 302 (temporary) redirect

If permanent, use 301 instead.

Got: https://weibo.com

Redirect overhead: 2436 ms total

Got: 2436 ms

Cross-domain redirect detected

https://weibo.com

1143 ms · HTTP/1.1

302

https://passport.weibo.com/visitor/visit...

1292 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://weibo.com	302	1143 ms	HTTP/1.1	SHANHAI-SERVER
2	https://passport.weibo.com/visitor/visit...	200	1292 ms	HTTP/1.1	nginx

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

C

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

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

HTTP Probe Timing

Total 928 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

3 ms

TCP Connect

211 ms

TLS Handshake

426 ms

Time to First Byte

928 ms

Total Time

928 ms

Connection waterfall

DNS Lookup 3 ms TCP Connect 211 ms TLS Handshake 426 ms Server Processing 288 ms Content Transfer 0 ms

B

TLS Certificate Expiry & Recommendations

45 days until leaf cert expires — 4 issues to address

REVIEW

Certificate validity

45

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

2 A records, 508 ms lookup

PASS

2 A records, 508 ms lookup

Resolves to 2 IPv4 address(es)

Got: 36.51.224.123, 36.51.224.126

No IPv6 (AAAA) records

6 nameserver(s) configured

Got: ns3.sina.com, ns4.sina.com, ns1.sina.com.cn, ns2.sina.com.cn, ns3.sina.com.cn, ns4.sina.com.cn

1 mail exchanger(s) configured

CAA records not checked

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

SPF record present in TXT

DNS resolution is slow (508 ms)

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

Got: 508 ms

A	36.51.224.123, 36.51.224.126
AAAA	—
CNAME	—
NS	ns3.sina.com, ns4.sina.com, ns1.sina.com.cn, ns2.sina.com.cn, ns3.sina.com.cn, ns4.sina.com.cn
MX	10 mx.sina.net
TXT	google-site-verification=P4n0nSkaw97YPTZ_JTcVtmAnD8TzURwDaqKi8WGZSb4 SPF v=spf1 include:spf.weibo.com -all
CAA	Lookup not available with standard resolver

Resolved in 508 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+

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

www/non-www redirect configured correctly (preferred: non-www)

HTTP correctly 301-redirects to HTTPS

www / non-www

302https://www.weibo.com/

200https://weibo.com/

Preferred variant: non-www

HTTP → HTTPS

301http://weibo.com/ → https://weibo.com/

Consistent

A+

Domain Intelligence

weibo.com — via Xiamen 35.com Information Co., Ltd., 27 years, 5 months old, hosted on SINA 15F,Ideal Plaza No.58 Bei Si Huan Xi Road, CN

PASS

weibo.com — via Xiamen 35.com Information Co., Ltd., 27 years, 5 months old, hosted on SINA 15F,Ideal Plaza No.58 Bei Si Huan Xi Road, CN

Domain registered until Mar 20, 2027 (11 months remaining)

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.

Registrar: Xiamen 35.com Information Co., Ltd.

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.

Hosting: SINA 15F,Ideal Plaza No.58 Bei Si Huan Xi Road, CN

Got: AS37936

Domain expiry

249 days

March 20, 2027

SSL certificate

45 days

Issued by DigiCert, Inc.

Domain age

27 years, 5 months

Registered March 20, 1999

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

SINA 15F,Ideal Plaza No.58 Bei Si Huan Xi Road, CN

ASN AS37936

36.51.224.123

Registrar

Xiamen 35.com Information Co., Ltd.

Unlocked 6 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 Xiamen 35.com Information Co., Ltd.

Created March 20, 1999 (27 years, 5 months ago)

Expires March 20, 2027 (11 months)

Last Updated March 21, 2026

Name Servers ns1.sina.com.cn, ns2.sina.com.cn, ns3.sina.com, ns3.sina.com.cn, ns4.sina.com, ns4.sina.com.cn

DNSSEC Not enabled

Hosting

IP Address 36.51.224.123

ASN AS37936 (SINA 15F,Ideal Plaza No.58 Bei Si Huan Xi Road, CN)

Provider SINA 15F,Ideal Plaza No.58 Bei Si Huan Xi Road, CN

Data source: rdap (0.1s)

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