Open
Cached
·
2h ago
89/100
SECURITY SCORE
Certificate Information
Subject
CN=*.nginx.com
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
November 02, 2025
Valid Until
January 31, 2026
86 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
FF:68:A7:74:1A:3E:A8:AF:0F:CE:5A:DB:21:FE:70:43:8F:83:0F:03:31:73:4D:F0:12:4D:ED:31:DB:3D:14:7C
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
Content-Security-Policy
Weak
frame-ancestors; form-action
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Present
Permissions-Policy: geolocation=(), microphone=(), camera=(), gyroscope=(), magnetometer=(), payment=(), fullscreen=(self), autoplay=(self)
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Significantly strengthen CSP directives
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