terabox.app

Readiness by lane

Green: terabox.app. Thin bar: Cloud Storage & File Transfer peer median.

Priority fixes for terabox.app

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

1. Priority 1 · Accelerate

   HTTP/2 negotiated

   Observed: The TLS handshake selected http/1.1 instead of HTTP/2.

   Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.

   What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

   82% of Cloud Storage & File Transfer peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: CDN Guide for Website Owners

2. Priority 2 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

   91% of Cloud Storage & File Transfer peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 2 days, below the one-year benchmark.

   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 Cloud Storage & File Transfer peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for no max-age, short of the 30-day benchmark.

   What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

   35% of Cloud Storage & File Transfer peers do this.

   Guide: Browser Caching Guide for Website Owners

What terabox.app already does well

Practices fewer than half of Cloud Storage & File Transfer peers use.

• Canonical URL declaredCanonical link present.41% of peers
• XML sitemap discoverableSitemap found.44% of peers
• Social preview image setog:image present.47% of peers

What we saw

Homepage checked

https://www.terabox.app/

Homepage response

HTTP 200

TLS

TLSv1.2, http/1.1

Certificate

DigiCert, 389-day validity, expiring 2027-01-16

DNS operators

Amazon Route 53

HSTS

max-age 2 days

Homepage HTML

19 KB, gzip

Images on homepage

0

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 Cloud Storage & File Transfer sites

• apkadmin.com53
• dailyuploads.net54
• exploader.net54
• fotoshare.co53
• hotpic1.cc54

Cloud Storage & File Transfer readiness benchmark