Open
Cached
·
just now
92/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Gravatar
Let's Encrypt
Clickagy
CookieYes
DigitalOcean Spaces
Font Awesome
G2
Google Analytics
Google API JS Client
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Hosted Libraries
Google Maps
Google Search
Google Static File Front End
Google Tag Manager
Google Translate
G Workspace
LinkedIn
New Relic
Microsoft SharePoint
TechTarget
Usercentrics
Vimeo
YouTube
Zoho Mail
ZoomInfo
Google Cloud
Certificate Information
Subject
CN=modius.com
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
January 04, 2026
Valid Until
April 04, 2026
43 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
5B:77:5D:6F:A6:CB:48:62:7A:B6:2B:31:E8:12:D3:5D:D8:EF:14:72:DD:CB:AD:46:A8:65:43:06:83:75:D3:1B
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=31536000; includeSubDomains; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
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