Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Let's Encrypt
Google Maps
Google Tag Manager
Bugsnag
Brightcove
Google reCAPTCHA
Mux
Google DoubleClick
Google Analytics
Google Cloud Storage
Google Static File Front End
Weglot
Google API JS Client
AzureFrontDoor
Google Fonts
Wistia
Hotjar
Airtable
Google Search
Localize.js
Amazon S3
OneTrust
GitHub
Adobe Fonts (Typekit)
Cloudflare CDNJS
AWS
Vimeo
Akamai
Active incidents
JW Player
Intercom
YouTube
Microsoft Clarity
jsDelivr
Google Cloud
Microsoft Azure
Certificate Information
Subject
CN=foxglobal.com
Issuer
C=US, O=Let's Encrypt, CN=YE2
Valid From
July 28, 2026
Valid Until
October 26, 2026
75 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
2E:8D:64:B1:CB:C0:ED:45:2B:89:BE:2E:4B:61:68:B8:AE:BC:C8:D5:F8:5E:9B:E5:DD:1E:F6:15:28:18:E5:AE
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
Present
origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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