Open
Cached
·
just now
88/100
SECURITY SCORE
Detected Technologies
Google Trust
YouTube
Google AdSense
Criteo
Active incidents
Google Tag Manager
Bing
Google Hosted Libraries
AppNexus (Xandr)
Yahoo
Google DoubleClick
Google Analytics
Microsoft Advertising
Tealium
Google Static File Front End
Outbrain
Google Fonts
AppDynamics
Cloudflare Web Analytics
Hotjar
LinkedIn
Cloudinary
Teads
Google Search
Facebook
Snapchat
Pinterest
TrustArc
Google Optimize
Akamai
Active incidents
The Trade Desk
Sentry
Google Cloud
Certificate Information
Subject
CN=navionics.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
February 01, 2026
Valid Until
May 02, 2026
32 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
89:21:FA:80:30:B9:32:F2:F0:00:B9:C0:28:49:B8:C6:FD:65:9D:BE:26:0A:CA:0B:A9:D0:63:54:D4:93:3E:E8
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
Missing
Not configured
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
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • 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