Open
Cached
·
just now
86/100
SECURITY SCORE
Certificate Information
Subject
CN=atomikos.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
December 08, 2025
Valid Until
March 08, 2026
54 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
BB:AF:B1:6F:65:6F:35:78:BF:C4:61:E3:DA:1D:C5:3E:84:D5:60:69:E9:03:A5:F6:DF:9A:20:83:B9:8A:06:08
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
connect-src; default-src; font-src; +9 more
connect-src 'self' disqus.com *.disqus.com cdn.subscribers.com *.google-analytics.com pro.ip-api.com createsend.com www.google.com px.ads.linkedin.com; default-src 'none'; font-src 'self' fonts.gstatic.com cdn.tinymce.com fonts.hellobar.com data:; frame-src *; img-src 'self' data: *; manifest-src 'self'; media-src *; object-src *; report-uri /bin/rest/SecurityHeadersPlugin/report; script-src 'self' disqus.com *.disqus.com *.disquscdn.com *.googleapis.com *.googletagmanager.com *.google-analytics.com connect.facebook.net 'unsafe-eval' 'unsafe-inline' lltrck.com cdn.subscribers.com *.doubleclick.net *.leadlander.com my.hellobar.com *.createsend1.com *.createsend.com assets.calendly.com *.googleadservices.com app.termly.io snap.licdn.com; style-src 'self' disqus.com *.disqus.com *.disquscdn.com fonts.googleapis.com 'unsafe-inline' fonts.hellobar.com assets.calendly.com *.googletagmanager.com ; upgrade-insecure-requests
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Present
same-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'
- • Add X-Content-Type-Options: nosniff
- • 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