Open
Cached
·
just now
88/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
Adobe Fonts (Typekit)
Basis Technologies
Bing
Microsoft Advertising
Clickagy
Demandbase
Facebook
Google AdSense
Google Analytics
Google Conversion Tracking
Google DoubleClick
Google reCAPTCHA
Google Static File Front End
Google Tag Manager
Instagram
jsDelivr
LinkedIn
Liveramp
Microsoft Clarity
Mouseflow
OneTrust
OpenX
Outbrain
Segment
StackAdapt
Taboola
The Trade Desk
Vimeo
YouTube
ZoomInfo
Google Cloud
Certificate Information
Subject
CN=ims.broadridge.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
April 13, 2026
Valid Until
July 12, 2026
55 days
Public Key
RSA
4096 bit
Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
EB:0C:CA:13:5A:96:ED:BC:6D:85:33:51:4E:27:7D:26:B1:45:3A:15:3C:DB:51:84:57:80:78:C1:EA:2E:64:38
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
Good
SAMEORIGIN
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