Open
Cached
·
just now
86/100
SECURITY SCORE
Detected Technologies
AWS API Gateway
AWS CloudFront
Let's Encrypt
PayPal
Adyen
Arcade
AWS
Amazon S3
Beamer
Google Analytics
Google DoubleClick
Google Fonts
Google reCAPTCHA
Google Search
Google Tag Manager
Microsoft Clarity
Microsoft 365
Qualified
Salesforce Cloud
Salesforce Sites
Microsoft SharePoint
Sierra
Slack
Stripe
TrustArc
Certificate Information
Subject
CN=navexglobal.com
Issuer
C=US, O=Let's Encrypt, CN=YR1
Valid From
June 17, 2026
Valid Until
September 15, 2026
46 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
2B:E2:7E:24:6B:EB:29:D8:A0:7A:C1:32:F2:B7:37:11:B2:EB:7C:FB:D2:76:AB:81:42:D4:78:0E:35:BD:EC:5F
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=63072000; includeSubDomains
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Significantly strengthen CSP directives
- • 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