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:

Expired Certificate - the server's certificate has expired

Cached · just now
72/100 SECURITY SCORE

Certificate Information

Subject
CN=www.7f.dk
Issuer
C=US, O=Let's Encrypt, CN=E8
Valid From
May 02, 2026
Valid Until
July 31, 2026 Expired
Public Key
ECDSA 384 bit (P-384) Strong
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
A5:72:9B:EF:07:24:2A:6F:55:AE:A4:7A:EB:B8:3C:80:43:B4:4C:8F:D2:35:C2:93:3C:96:8C:1A:12:1C:99:22
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=31536000; includeSubdomains;
Content-Security-Policy
Missing
Not configured Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • Add Content-Security-Policy header to prevent XSS attacks
  • • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
  • • Consider adding Permissions-Policy to control browser features

CAA Records (Certificate Authority Authorization)

CAA Records
Configured (Restricts certificate issuance)
Current Issuer
Authorized (Matches CAA policy)
Recommendations
  • • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts
  • • Consider adding 'issuewild' records to control wildcard certificate issuance

Subject Alternative Names

1 domain