Open
Cached
·
just now
91/100
SECURITY SCORE
Certificate Information
Subject
CN=afw.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
January 20, 2026
Valid Until
April 20, 2026
88 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
2E:54:EC:19:D7:92:48:C8:8E:41:81:51:41:FF:A7:4E:B8:56:FB:1F:73:37:17:63:2D:9E:AB:C2:66:A9:23:A6
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
Content-Security-Policy
Basic
default-src; connect-src; font-src; +7 more
default-src 'self'; connect-src * webpack:; font-src * data: webpack:; frame-src * *.wellsfargo.com; img-src * data:; media-src *; object-src *; script-src * *.wellsfargo.com 'unsafe-inline' 'unsafe-eval' blob:; style-src * 'unsafe-inline'; manifest-src https://*.afw.com;
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
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'
- • 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