Cached · just now
89/100 SECURITY SCORE

Certificate Information

Subject
C=US, ST=Massachusetts, L=Waltham, O=Constant Contact, Inc., CN=*.constantcontact.com
Issuer
C=BE, O=GlobalSign nv-sa, CN=GlobalSign Atlas R3 OV TLS CA 2025 Q4
Valid From
November 10, 2025
Valid Until
December 12, 2026 220 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
5A:A5:F8:9D:A0:F0:58:0F:FC:CC:0D:26:05:D2:8C:58:EB:9E:5A:2A:96:BE:0F:48:E7:42:F8:77:13:39:E8:E3
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
default-src; script-src; script-src-attr; +8 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Present
accelerometer=(), browsing-topics=(), camera=(); +15 more
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'

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