Cached · just now
79/100 SECURITY SCORE

Certificate Information

Subject
CN=*.accelo.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M01
Valid From
March 19, 2026
Valid Until
October 02, 2026 143 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
0F:76:2B:D8:D4:B3:97:A8:64:8D:79:10:14:EE:8D:F3:61:CA:61:1D:EE:6A:09:A5:09:50:3F:40:91:6F:FF:DD
Alternative Names

Security Configuration

TLS Protocols
TLS 1.2
Forward Secrecy
Limited (Check cipher configuration)
Warnings
  • TLS 1.3 is not supported (recommended)

HTTP Security Headers

Status
Strict-Transport-Security
Present
max-age=300; includeSubDomains; preload
Content-Security-Policy
Weak
frame-ancestors Analyze
Content-Security-Policy-Report-Only
Basic
script-src; script-src-elem; object-src; +1 more Analyze
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • Significantly strengthen CSP directives
  • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
  • 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