Open
Cached
·
just now
92/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
CN=banxa.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
October 12, 2026
Valid Until
January 10, 2027
48 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
BE:25:E7:AE:78:3B:7B:AF:B0:62:09:EF:E4:EC:6C:EF:C0:87:7E:00:4A:19:8B:5C:05:90:B1:1C:B7:DC:51:C2
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
Weak
max-age=0; includeSubDomains
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Present
clipboard-write=(self), camera=(), microphone=(); +4 more
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Strengthen CSP by removing 'unsafe-eval'
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