Open
Cached
·
just now
87/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
C=US, ST=Massachusetts, L=Waltham, O=Constant Contact, Inc., CN=rs6.net
Issuer
C=BE, O=GlobalSign nv-sa, CN=GlobalSign Atlas ECCR5 OV TLS CA 2026 Q1
Valid From
March 12, 2026
Valid Until
September 27, 2026
141 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
CC:3F:C7:32:01:30:85:6B:07:04:3B:6B:DD:07:50:AF:CF:73:50:0D:9F:80:3A:E0:62:E5:2B:0A:9C:DC:4D:72
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
Good
max-age=31536000; includeSubDomains
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Strengthen CSP by removing 'unsafe-eval'
- • 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