Open
Cached
·
just now
92/100
SECURITY SCORE
Certificate Information
Subject
CN=wiki.docchula.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
January 04, 2026
Valid Until
April 04, 2026
74 days
Public Key
RSA
4096 bit
Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
1E:79:09:62:7B:67:EF:BA:7B:54:C5:1E:7A:2B:E2:D5:81:69:6D:16:5F:F2:BC:49:53:89:BB:45:A4:EE:AC:DC
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=15552000; includeSubDomains
Content-Security-Policy
Good
base-uri; default-src; style-src; +5 more
base-uri 'none';default-src 'self';style-src 'self' 'unsafe-inline';script-src https://kb.aa.md.chula.ac.th 'nonce-37577f774772d81b0a109d184cca73f0';media-src * data: blob:;img-src * data: blob:;frame-src * data:;connect-src *
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Strengthen CSP by removing 'unsafe-eval'
- • 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