Open
Cached
·
just now
85/100
SECURITY SCORE
Detected Technologies
Google Trust
AWS CloudFront
YouTube
Google Tag Manager
Amazon Advertising
Google Hosted Libraries
Reddit
Yahoo
HubSpot Forms
Active incidents
Azure Blob Storage
Google DoubleClick
Google Analytics
Microsoft Advertising
Adalyser
Mixpanel
New Relic
Google Cloud Storage
Google Static File Front End
Google Fonts
Twitter
Hotjar
LinkedIn
Singular
Cloudflare Turnstile
Google Search
Navattic
Google Cloud Functions
Facebook
Decagon
Amazon S3
Cloudflare CDNJS
AWS
SpeedCurve
HubSpot
Active incidents
Quora
The Trade Desk
Google Cloud
Certificate Information
Subject
CN=transferwise.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
March 22, 2026
Valid Until
June 20, 2026
51 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
31:CD:36:8D:73:E0:A7:4B:AF:55:2A:D1:0E:A6:34:67:81:46:B6:43:26:B9:88:82:24:C9:8B:07:AD:67:68:36
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
Present
max-age=31536000
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Present
ch-ua-model=("https://sdk-api-v1.singular.net"), ch-ua-platform-version=("https://sdk-api-v1.singular.net"), ch-ua-full-version-list=("https://sdk-api-v1.singular.net")
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
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