Open
Cached
·
just now
88/100
SECURITY SCORE
Certificate Information
Subject
CN=vygo.app
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
October 19, 2025
Valid Until
January 17, 2026
55 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
DF:C1:BD:6A:F6:1F:57:28:C2:3A:2D:A5:90:10:70:84:60:C7:1E:4C:B4:E9:99:15:69:7A:6E:90:8B:C9:53:B9
Alternative Names
Security Configuration
TLS Protocols
TLS 1.0
TLS 1.1
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
Warnings
- • TLS 1.1 is deprecated and should be disabled
- • TLS 1.0 is deprecated and should be disabled
HTTP Security Headers
Status
Strict-Transport-Security
Present
max-age=31556926
Content-Security-Policy
Good
default-src; script-src; style-src; +7 more
default-src 'self' https://*.vygo.app; script-src 'self' 'unsafe-inline' https://apis.google.com https://*.gstatic.com https://*.firebaseapp.com https://*.firebaseio.com; style-src 'self' 'unsafe-inline' https://*.googleapis.com; font-src 'self' https://*.gstatic.com; img-src 'self' blob: data: https://*.googleusercontent.com https://*.googleapis.com https://cdn.jsdelivr.net https://cdnjs.cloudflare.com https://api.dicebear.com https://avatars.dicebear.com https://images.unsplash.com https://*.loom.com; connect-src 'self' https://*.firebaseio.com https://*.googleapis.com https://*.cloudfunctions.net https://*.typesense.net https://*.ingest.us.sentry.io https://*.loom.com; frame-src 'self' https://apis.google.com https://*.loom.com; frame-ancestors 'none'; base-uri 'self'; object-src 'none';
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Strengthen CSP by removing 'unsafe-eval'
- • 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