Open
Cached
·
just now
81/100
SECURITY SCORE
Detected Technologies
Bing
Buzzsprout
Cloudflare CDNJS
Entrust
Facebook
Google Analytics
Google API JS Client
Google DoubleClick
Google Search
Google Static File Front End
Google Tag Manager
Hotjar
jsDelivr
LinkedIn
Microsoft Clarity
Qualtrics
Active incidents
Reddit
6sense
Active incidents
Sovrn
The Trade Desk
Twitter
YouTube
Google Cloud
Certificate Information
Subject
CN=navistar.com
Issuer
C=CA, O=Entrust Limited, CN=Entrust DV TLS Issuing RSA CA 2
Valid From
November 11, 2025
Valid Until
November 11, 2026
90 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
1E:4F:F4:C7:EF:AC:07:0F:E2:07:56:A2:8C:75:0D:C0:98:75:5C:67:13:25:89:32:0D:E5:B3:E0:BA:15:95:1C
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
Missing
Not configured
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Add Strict-Transport-Security header with max-age of at least 1 year
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add X-Content-Type-Options: nosniff
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
- • 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