Skip to content
https://bilibili.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
75
GRADE
C
FIX
1
REVIEW
5
PASS
3
INFO
0
Probed from New York, United Stated
301 Moved Permanently
Checks
9
3 PASS 5 REVIEW 1 FIX
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), 1230 ms total
REVIEW
1 redirect(s), 1230 ms total
Info::
Single redirect
Got: https://bilibili.com → https://www.bilibili.com/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1230 ms total
Got: 1230 ms

https://bilibili.com

783 ms · HTTP/1.1

301

https://www.bilibili.com/

447 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://bilibili.com301783 msHTTP/1.1Tengine
2https://www.bilibili.com/200447 msHTTP/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

C
Crawlability
Action
robots.txt present, sitemap with 8 URLs
REVIEW
robots.txt present, sitemap with 8 URLs
Info::
robots.txt is present
Got: 559 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::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 8 entries
Info::
Sitemap index with 8 child sitemaps
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

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 559 B Sitemaps referenced 0 User-agents Yisouspider, bingbot, Sogou web spider, 360Spider, Facebot, Twitterbot, *, Applebot, Sogou inst spider, Googlebot, Baiduspider, Bytespider, PetalBot, facebookexternalhit Blocking Yes — all crawlers blocked
User-agent: *
Disallow: /medialist/detail/
Disallow: /index.html

User-agent: Yisouspider
Allow: /

User-agent: Applebot
Allow: /

User-agent: bingbot
Allow: /

User-agent: Sogou inst spider
Allow: /

User-agent: Sogou web spider
Allow: /

User-agent: 360Spider
Allow: /

User-agent: Googlebot
Allow: /

User-agent: Baiduspider
Allow: /

User-agent: Bytespider
Allow: /

User-agent: PetalBot
Allow: /

User-agent: facebookexternalhit
Allow: /tbhx/hero

User-agent: Facebot
Allow: /tbhx/hero

User-agent: Twitterbot
Allow: /tbhx/hero

User-agent: *
Disallow: /
sitemap.xml 200 OK
Type Sitemap Index URLs 8 entries Valid XML Yes
Child Sitemaps:
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.bilibili.com/
200https://bilibili.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

B
TLS Certificate Expiry & Recommendations
240 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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, 256 ms lookup
PASS
4 A records, 256 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 119.3.70.188, 139.159.241.37, 8.134.50.24, 47.103.24.173
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns4.dnsv5.com, ns3.dnsv5.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 (256 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 256 ms
A119.3.70.188, 139.159.241.37, 8.134.50.24, 47.103.24.173
AAAA—
CNAME—
NSns4.dnsv5.com, ns3.dnsv5.com
MX
10 mgw.bilibili.co
15 bilibili-com.mail.protection.partner.outlook.cn
TXT
google-site-verification=mELEdNHOoMJP22VlKs3jXTZWCUs2MZkx3DR1lrk50PM
SPF v=spf1 a:mgw.bilibili.co include:spf.protection.partner.outlook.cn -all
631e1b0504e1498bb21249778d962064
apple-domain-verification=JTrkMNP33h0KMlcP
MS=B2EC5BBDB22D5D9AC11125D7FE2513F1DD3A1A10
google-site-verification=532rCcNWX80OoYjazA-kB6IGvDqvXg8TlB-I3UWHUBw
CAALookup not available with standard resolver
Resolved in 256 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
bilibili.com — via Alibaba Cloud Computing (Beijing) Co., Ltd., 21 years, 9 months old, hosted on HWCSNET Huawei Cloud Service data center, CN
PASS
bilibili.com — via Alibaba Cloud Computing (Beijing) Co., Ltd., 21 years, 9 months old, hosted on HWCSNET Huawei Cloud Service data center, CN
Info::
Domain registered until Oct 21, 2031 (5 years, 7 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: Alibaba Cloud Computing (Beijing) 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: HWCSNET Huawei Cloud Service data center, CN
Got: AS55990
Domain expiry

1956 days

October 21, 2031

SSL certificate

240 days

Issued by GlobalSign nv-sa

Domain age

21 years, 9 months

Registered October 21, 2004

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

HWCSNET Huawei Cloud Service data center, CN

ASN AS55990

119.3.70.188

Registrar

Alibaba Cloud Computing (Beijing) Co., Ltd.

Unlocked 2 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 Alibaba Cloud Computing (Beijing) Co., Ltd.
Created October 21, 2004 (21 years, 9 months ago)
Expires October 21, 2031 (5 years, 7 months)
Last Updated December 29, 2021
Name Servers ns3.dnsv5.com, ns4.dnsv5.com
DNSSEC Not enabled
Hosting
IP Address 119.3.70.188
ASN AS55990 (HWCSNET Huawei Cloud Service data center, CN)
Provider HWCSNET Huawei Cloud Service data center, CN
Data source: rdap (2.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

A
HTTP Probe Timing
Total 699 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
11 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
232 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
224 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
699 ms
Total Time Total request time from DNS lookup through full response.
700 ms

Connection waterfall

DNS Lookup 11 ms TCP Connect 232 ms TLS Handshake 224 ms Server Processing 232 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback