Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Google AdSense
Chili Piper
CodeJudge
Oracle Cloud
Google Tag Manager
UserWay
Bing
SalesLoft
Google Cloud Run
Amplitude
Active incidents
Kinsta
Amazon Advertising
AppNexus (Xandr)
PartnerStack
Fullstory
Reddit
Klenty
Yahoo
HubSpot Forms
TrackJS
Factors.AI
Trustpilot
DigiCert
Google DoubleClick
TeamMe
Google Analytics
Microsoft Advertising
Google Conversion Tracking
Trendemon
6sense
Report URI
Cloudflare CDN
Greenhouse
Google Cloud Storage
Google Static File Front End
Geoapify
Twitter
Qualtrics
LinkedIn
ShareThis
HubSpot Analytics
Drift
unpkg
Google Search
BootstrapCDN
Yandex
Cloudflare
Active incidents
Adobe Marketo
Facebook
Amazon S3
Mouseflow
OneTrust
GitHub
Active incidents
Dynatrace
TikTok
AWS
Taboola
Google Optimize
Convert
HubSpot
Highcharts
Quora
YouTube
The Trade Desk
Microsoft Clarity
Optimizely
jsDelivr
Google Cloud
Certificate Information
Subject
C=US, ST=New York, L=New York, O=Payoneer Inc., CN=*.payoneer.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid From
June 30, 2025
Valid Until
June 29, 2026
61 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
50:7E:B5:A7:80:AD:68:D1:E0:D0:4E:8F:1F:1B:2A:8B:61:53:63:37:01:35:DD:C0:80:7B:FE:E0:AA:F4:04:1D
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; includesubdomains; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • 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