Open
Cached
·
just now
86/100
SECURITY SCORE
Detected Technologies
Google Trust
YouTube
AWS
Amazon S3
Cloudflare CDNJS
Cloudflare Web Analytics
Facebook
Google Analytics
Google Cloud Storage
Google DoubleClick
Google Maps
Google Search
Google Static File Front End
Google Tag Manager
HubSpot
HubSpot Analytics
HubSpot Live Chat
Iframely
Intercom
JW Player
Mux
Pendo
Sentry
Stripe
TikTok
TikTok Analytics
Vimeo
Wistia
Google Cloud
Certificate Information
Subject
CN=exercise.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 10, 2026
Valid Until
July 09, 2026
64 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
57:DE:D6:4A:16:1A:8D:14:B0:08:55:0F:57:E1:35:D3:5A:2B:36:D9:8D:1F:1B:45:26:66:F7:08:5C:9D:B1:17
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
Excellent
max-age=63072000; includeSubDomains; preload, max-age=31536000; includeSubDomains
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • 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