Website Security Test of
wallet.tether.io

Test Results Summary for wallet.tether.io

• Web Software Security Test
  One third-party web software dependancy was identified. It appears to be outdated, but no known vulnerabilities were detected. No Content Management System (CMS) was identified. One CMS component, JS-library or framework was identified: react. Show details.
• GDPR Compliance Test
  No obvious GDPR-related compliance issues were detected across Privacy Policy, Website Security, TLS Encryption, Cookie Protection, Cookie Disclaimer. Show details.
• PCI DSS Compliance Test
  The website is compliant with PCI DSS Requirement 6.3, while being non-compliant with Requirement 6.4. Show details.
• HTTP Headers Security Test
  Issues were identified with key security headers: missing X-Content-Type-Options; misconfigured Content-Security-Policy. Optional HTTP headers appear to be properly configured: Server, Access-Control-Allow-Origin, Cache-Control. Show details.
• Content Security Policy (CSP) Test
  Content-Security-Policy is enforced but configuration issues were identified: directive errors, overly permissive directives, deprecated directives. A report-only Content-Security-Policy is not present. Show details.
• Cookies Privacy and Security Test
  3 cookies detected; _ga_RJ2C204DFE, _ga have security or privacy-related configuration issues. Show details.
• External Content Security Test
  7 external requests detected; 1 request failed. SRI is not used for 5 third-party JavaScript and CSS files. Show details.
• Protection from Data Scraping Test
  No significant anti-scraping protections were detected. Additional anti-scraping protection appears to be provided by external infrastructure. Show details.

Compliance Summary for wallet.tether.io

• GDPR Compliance Passed: No obvious GDPR-related compliance issues were detected across Privacy Policy, Website Security, TLS Encryption, Cookie Protection, Cookie Disclaimer.
• PCI DSS Compliance Failed: The website is compliant with PCI DSS Requirement 6.3, while being non-compliant with Requirement 6.4.