Open
Cached
·
just now
92/100
SECURITY SCORE
Detected Technologies
GitHub
Let's Encrypt
Active incidents
UserWay
YouTube
Akamai
Algolia
AzureFrontDoor
Ceros
Contentful
Contentsquare
Demandbase
Active incidents
Formstack
Google Analytics
Google DoubleClick
Google Fonts
Google Maps
Google Search
Google Static File Front End
Google Tag Manager
Issuu
LinkedIn
Liveramp
Navattic
OpenStreetMap
Pusher
Securiti
unpkg
Vercel
Vimeo
Google Cloud
Microsoft Azure
Certificate Information
Subject
CN=csgi.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
April 29, 2026
Valid Until
July 28, 2026
80 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
5C:FD:54:AD:36:BB:18:C9:55:E3:28:0B:58:EB:90:29:A5:FB:5D:E4:BB:61:17:06:4F:6A:FF:CB:9E:EC:80:89
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=63072000
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
camera=(), microphone=(), geolocation=()
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Strengthen CSP by removing 'unsafe-eval'
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