Open
Cached
·
just now
92/100
SECURITY SCORE
Certificate Information
Subject
CN=activecampaign.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
November 15, 2025
Valid Until
February 13, 2026
45 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
56:D2:64:86:4B:09:4B:39:E1:44:99:BD:FA:2A:D7:84:D2:08:ED:51:DC:B0:F2:90:23:2D:5A:9A:55:35:96:12
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
Excellent
max-age=63072000; includeSubDomains; preload
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-b03oEjzltEYGMpRRXd9Owtb7i' 'strict-dynamic'; frame-ancestors 'self'; 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
- • 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
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