Open
Cached
·
just now
93/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
YouTube
Google AdSense
Chili Piper
Google Tag Manager
Ahrefs
RudderStack
Google Hosted Libraries
Netlify
Reddit
HubSpot Forms
Cookiebot
Capterra
Google DoubleClick
Google Analytics
Microsoft Advertising
Crazy Egg
6sense
Active incidents
Greenhouse
Active incidents
Google Static File Front End
Apple Podcasts
Google Fonts
Vidyard
Twitter
LinkedIn
Contentful
ZoomInfo
HubSpot Analytics
Google Search
Adobe Marketo
Navattic
Qualified
Facebook
Vercel
jQuery
HubSpot
Vector
Optimizely
Google Cloud
Certificate Information
Subject
CN=diligentmessenger.com
Issuer
C=US, O=Let's Encrypt, CN=YR2
Valid From
June 30, 2026
Valid Until
September 28, 2026
45 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
B7:C2:18:09:CE:30:3E:A0:BF:E8:24:5B:E6:12:D2:C1:14:8B:17:C4:95:3B:63:EF:97:3A:41:81:70:B1:3F: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
Excellent
max-age=63072000; includeSubDomains; preload
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
camera=(), microphone=(), geolocation=()
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
CAA Records (Certificate Authority Authorization)
CAA Records
Configured
(Restricts certificate issuance)
Current Issuer
Authorized
(Matches CAA policy)
Authorized CAs
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts
- • Consider adding 'issuewild' records to control wildcard certificate issuance