Open
Cached
·
just now
92/100
SECURITY SCORE
Certificate Information
Subject
CN=admitad.com
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
November 17, 2025
Valid Until
February 15, 2026
43 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
61:F2:3F:98:64:D1:B1:FC:C0:E8:88:A6:1A:5F:74:D9:2D:DB:58:40:9E:DF:85:FD:75:CA:5B:B1:A0:BC:93:D3
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
Excellent
max-age=31536000; includeSubDomains; preload
Content-Security-Policy
Basic
base-uri; object-src; script-src; +1 more
base-uri 'self'; object-src 'none'; script-src 'nonce-2wTq8lDhuKjv0BX7MkjKyKkeDCXQWauiNTixmmPn1oyFZexuVWiJaoHlnsEXmlA2' 'strict-dynamic'; report-uri https://o59832.ingest.sentry.io/api/1197065/security/?sentry_key=be62e2ea3fb544f78dd5fbf3abbd8b8a;
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Missing
Not configured
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Consider adding Permissions-Policy to control browser features
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