Open
Cached
·
just now
91/100
SECURITY SCORE
Detected Technologies
YouTube
Adobe Fonts (Typekit)
Microsoft Advertising
Brightcove
Cloudflare
Cloudflare CDN
Cloudflare CDNJS
Demandbase
Oracle Eloqua
Facebook
GitBook
Google Analytics
Google API JS Client
Google Conversion Tracking
Google Search
Google Static File Front End
Google Tag Manager
jsDelivr
Microsoft Clarity
Oktopost
OneTrust
OptinMonster
Qualified
Sectigo
ShareThis
Storylane
Twitter
UserWay
Vimeo
Google Cloud
Certificate Information
Subject
C=US, ST=California, O=Quest Software Inc., CN=*.quest.com
Issuer
C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA OV R36
Valid From
June 23, 2025
Valid Until
June 23, 2026
124 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
BC:6B:EA:8D:40:61:FF:38:43:CF:FB:E9:AE:92:A5:F4:DB:DA:63:81:1E:B7:0E:CC:E3:C3:6F:D3:5D:C5:91:DA
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=2592000; includeSubDomains
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Present
microphone=()
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
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