Open
Cached
·
just now
86/100
SECURITY SCORE
Certificate Information
Subject
CN=openai.com
Issuer
C=US, O=Let's Encrypt, CN=E8
Valid From
September 27, 2025
Valid Until
December 26, 2025
50 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
92:B6:F2:3F:C0:E5:B9:C0:30:16:C7:26:F2:4A:61:4D:18:79:36:88:CB:E5:D6:5F:AF:93:B2:2B:25:58:8A:9F
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
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Content-Security-Policy header to prevent XSS attacks
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • 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)
Authorized CAs
godaddy.com
letsencrypt.org
pki.goog
; cansignhttpexchanges=yes
sectigo.com
amazon.com
digicert.com
; cansignhttpexchanges=yes
Wildcard CAs
sectigo.com
pki.goog
; cansignhttpexchanges=yes
digicert.com
; cansignhttpexchanges=yes
amazon.com
letsencrypt.org
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • You have authorized 6 CAs - consider limiting to only the CAs you actively use
- • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts