Open
Cached
·
just now
92/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
YouTube
Google AdSense
Google Tag Manager
Bing
Reddit
HubSpot Forms
Active incidents
Google DoubleClick
Google Analytics
Microsoft Advertising
Crazy Egg
Segment
Google Static File Front End
LaunchDarkly
Ghost
Google API JS Client
Twitter
Transcend
LinkedIn
Cloudinary
Stripe
HubSpot Analytics
Active incidents
unpkg
Google Search
Facebook
Amazon S3
GitHub
AWS Certificate Manager
Visual Website Optimizer
IP-API
HubSpot
Active incidents
Vector
Microsoft Clarity
HubSpot Live Chat
Active incidents
jsDelivr
Google Cloud
Certificate Information
Subject
CN=app.onfleet.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M01
Valid From
January 29, 2026
Valid Until
February 27, 2027
302 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
13:C0:69:88:DF:01:DF:A9:0F:87:36:2E:AC:D4:C5:73:A0:E3:91:4C:82:16:4F:6F:5C:5B:3C:CE:4E:36:2C:5E
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
Good
max-age=31536000; includeSubDomains
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Strengthen CSP by removing 'unsafe-eval'
- • 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