Open
Cached
·
just now
90/100
SECURITY SCORE
Certificate Information
Subject
CN=meta.discourse.org
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M03
Valid From
May 24, 2025
Valid Until
June 20, 2026
141 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
47:EE:3D:F0:D6:B3:BB:6D:CE:31:D1:CD:32:54:F4:3C:8F:FF:32:B2:34:A6:34:78:F1:D9:B1:10:64:27:1E:5A
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
Missing
Not configured
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-h8aFGlpTazwqn6vv2FyfSC5Qy' 'strict-dynamic'; frame-ancestors 'self' https://blog.discourse.org https://civilized-discourse-construction-kit-inc.ghost.io; 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
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • 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