Open
Cached
·
just now
87/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Google AdSense
Zscaler
Google Tag Manager
Brightcove
GoDaddy
OpenX
Liveramp
Google DoubleClick
Google Analytics
Crazy Egg
Adobe Audience Manager
Cloudflare CDN
Basis Technologies
Google Static File Front End
Google API JS Client
Clickagy
Qualtrics
LinkedIn
ZoomInfo
Google Search
BootstrapCDN
Cloudflare
Facebook
OneTrust
Matomo
Sketchfab
Ceros
jQuery
Salesforce Pardot
Akamai
Active incidents
YouTube
The Trade Desk
MyFonts
jsDelivr
Google Cloud
Certificate Information
Subject
CN=*.baxter.com
Issuer
C=US, ST=Arizona, L=Scottsdale, O=GoDaddy.com, Inc., OU=http://certs.godaddy.com/repository/, CN=Go Daddy Secure Certificate Authority - G2
Valid From
April 02, 2025
Valid Until
May 04, 2026
23 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
D8:A4:7D:AD:A1:CB:25:6B:10:96:56:56:55:A8:5F:D1:2F:81:49:0C:59:78:67:68:52:D9:DA:BF:25:95:D3:DD
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=31536000
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
microphone=(), camera=()
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