bilibili.tv

Readiness by lane

Green: bilibili.tv. Thin bar: Entertainment & Video Streaming peer median.

Priority fixes for bilibili.tv

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Enable

   robots.txt published

   Observed: No robots.txt file was returned at the site root.

   Why it matters: robots.txt is where crawlers look first for crawl rules and sitemap locations. Without it, they assume everything is open.

   What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.

   87% of Entertainment & Video Streaming peers do this. Limit: Only the standard location was requested, once, at the time of the check.

   Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes

2. Priority 2 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.

   31% of Entertainment & Video Streaming peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.bilibili.tv.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   31% of Entertainment & Video Streaming peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   43% of Entertainment & Video Streaming peers do this.

   Guide: A Practical Website Health Check for Owners

What bilibili.tv already does well

Practices fewer than half of Entertainment & Video Streaming peers use.

• No render-blocking scripts in <head>Head scripts load without blocking.42% of peers
• Structured data presentJSON-LD structured data found.48% of peers
• Certificate lifetime of 100 days or lessShort-lived 89-day certificate from Let's Encrypt, already inside the 2027 limit.50% of peers

What we saw

Homepage checked

https://www.bilibili.tv/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-26

DNS operators

Google Cloud DNS

Homepage HTML

23 KB, gzip

Images on homepage

2 (webp 1, png 1)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Entertainment & Video Streaming sites

• ateamas.com62
• digionline.ro62
• disneyplus.com62
• tving.com63
• xcream.net63

Entertainment & Video Streaming readiness benchmark