Open
Cached
·
just now
90/100
SECURITY SCORE
Certificate Information
Subject
CN=extra.co.th
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
December 08, 2025
Valid Until
March 08, 2026
36 days
Public Key
ECDSA
384 bit
(P-384)
Strong
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
6B:34:C2:28:48:5B:AA:7F:64:AA:10:2B:31:73:83:A3:10:06:EB:DC:35:E4:F3:CE:1A:A0:47:3C:A9:06:DC:3C
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
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Present
geolocation=*, midi=(), sync-xhr=(self "https://extra.co.th" "https://www.extra.co.th"), microphone=(), magnetometer=(), gyroscope=(), payment=(), fullscreen=(self "https://extra.co.th" "https://www.extra.co.th" )
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