abema.tv

エラー | ABEMA

Last scanned 7 h agoCompare with another site →

Built with

No platform, CMS or framework detected. Detection is passive: it only sees what a site exposes in its HTML, headers and cookies, so custom or well-hidden stacks show up as nothing rather than as a guess.

Also detected

Infrastructure: Varnish

Overview

Status: alive
Registered: not looked up yet
First seen here: 2026-09-21
Security grade: F (45/100, from headers & TLS)
Privacy score: 90/100 (0 third-party script hosts, 0 tracking/marketing services)
Hosting: unknown
Linked to from: 0 other sites seen so far

What to fix

Add a Content-Security-Policy
Limits which scripts can run, and is the main defense against XSS. Start with Content-Security-Policy-Report-Only to test.
Add X-Content-Type-Options
Header: X-Content-Type-Options: nosniff
Prevent clickjacking
Header: X-Frame-Options: DENY (or a CSP frame-ancestors directive).
Add a Referrer-Policy
Header: Referrer-Policy: strict-origin-when-cross-origin
Mark cookies Secure and HttpOnly
At least one cookie is sent without these flags, exposing it to interception or scripts.

Security & email signals

✓ HTTPS
✓ HSTS
✗ Content-Security-Policy
✗ X-Content-Type-Options
✗ X-Frame-Options
✗ Referrer-Policy
✗ Permissions-Policy
✓ SPF record
✓ DMARC record
✗ DKIM record
✗ Cookies set securely
✗ Has real content (not an empty shell)
✓ Valid TLS certificate

Recent changes

2026-09-22: TLS expiry changed from "2027-02-16" to "2027-02-16"

Badge

Show this site's security grade in a README or footer:

<a href="https://webtelemetry.dev/site/abema.tv"><img src="https://webtelemetry.dev/badge/abema.tv.svg" alt="Security grade"></a>

Generated automatically from passive, publicly observable data. Think something here is wrong or want this profile removed? See /bot. Machine-readable: JSON.