Open
Cached
·
just now
92/100
SECURITY SCORE
Certificate Information
Subject
CN=forum.aurora.dev
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
November 28, 2025
Valid Until
February 26, 2026
40 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
79:09:0B:27:89:B2:7B:31:A9:11:8B:49:10:6C:41:AC:FD:BD:DC:25:AD:66:C2:62:1A:4A:DB:80:04:FE:D0:5C
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
Basic
upgrade-insecure-requests; base-uri; object-src; +3 more
upgrade-insecure-requests; base-uri 'self'; object-src 'none'; script-src 'nonce-JZn9AumpdyglhEfuGjwW0H4k1' 'strict-dynamic'; frame-ancestors 'self'; manifest-src 'self'
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • 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
Configured
(Restricts certificate issuance)
Current Issuer
Authorized
(Matches CAA policy)
Authorized CAs
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts
- • Consider adding 'issuewild' records to control wildcard certificate issuance