Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
Gravatar
Adobe Audience Manager
Akamai
Active incidents
Bing
Microsoft Advertising
Calendly
Clickagy
G2
Google Analytics
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Search
Google Static File Front End
Google Tag Manager
HubSpot
HubSpot Forms
LinkedIn
Liveramp
Microsoft Clarity
Pantheon
Reddit
The Trade Desk
Twitter
Usercentrics
Wistia
Google Cloud
Certificate Information
Subject
CN=*.addigy.com
Issuer
C=US, ST=Texas, L=Houston, O=SSL Corporation, CN=SSL.com RSA SSL subCA
Valid From
July 22, 2025
Valid Until
August 22, 2026
115 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
27:50:B2:EF:DC:63:0C:3A:1A:74:B0:6E:05:DC:B7:30:70:A6:E7:1A:0A:38:B9:DA:28:59:E3:EA:CA:A5:0C:C4
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=15552000; includeSubDomains
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-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'
- • 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