SSL Verification Bypassed
The server's SSL certificate could not be verified. The analysis was completed using insecure mode. Data may be less reliable.
Reason:
Hostname Mismatch - certificate is issued for *.tv2.no, tv2.no, not for 2play.no
Open
Cached
·
just now
85/100
SECURITY SCORE
Certificate Information
Subject
C=NO, L=BERGEN, UNKNOWN={:asn1_OPENTYPE, <<12, 4, 53, 48, 48, 56>>}, O=TV 2 AS, CN=*.tv2.no, UNKNOWN=979484534
Issuer
C=NO, O=Buypass AS-983163327, CN=Buypass Class 2 CA 2
Valid From
October 14, 2025
Valid Until
October 14, 2026
322 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
C0:6A:A9:E1:39:72:56:37:6D:2A:6A:33:DD:74:6D:72:0B:86:49:29:3A:19:5D:EC:6A:BD:5E:50:91:5A:58:CA
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
HTTP Security Headers
Status
Strict-Transport-Security
Present
max-age=2592000; includeSubDomains
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
autoplay=, fullscreen=, geolocation=*, sync-xhr=(self)
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Add Content-Security-Policy header to prevent XSS attacks
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
CAA Records (Certificate Authority Authorization)
CAA Records
Not Configured
(Any CA can issue certificates)
CAA Issues
- • No CAA records configured - any CA can issue certificates
Recommendations
- • Implement CAA records to restrict which CAs can issue certificates for your domain
- • This adds an extra layer of security against unauthorized certificate issuance
- • Example: Add CAA record 'example.com. CAA 0 issue "letsencrypt.org"'
- • Consider adding 'iodef' record to receive security incident reports