Summary of www.bitgo.com [Desktop version] Website Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 6th, 2026 11:29 GMT+0
Server IP:104.18.1.206
Reverse DNS:-
Location:N/A
Version:for desktop
Your final score:
- A
- B
- C
- F
A
Test Results Summary for www.bitgo.com
- No third-party web software dependancies were identified. Show details.
- Potential GDPR compliance issues were identified related to Cookie Disclaimer. The following checks were not performed, as no corresponding cookies with personal or tracking information seem to be sent by the website: Website Security. Show details.
- The website is compliant with PCI DSS Requirement 6.3, while being non-compliant with Requirement 6.4. Show details.
- Issues were identified with key security header misconfigured Content-Security-Policy. Optional HTTP headers appear to be properly configured: Server, Permissions-Policy, Referrer-Policy, Cache-Control. Deprecated HTTP headers detected: X-XSS-Protection. Show details.
- Content-Security-Policy is enforced but configuration issues were identified: directive errors. A report-only Content-Security-Policy is not present. Show details.
- 6 cookies detected; _zitok, OptanonConsent, _twsid, _twpid, country have security or privacy-related configuration issues. Show details.
- 25 external requests detected; 7 requests failed. SRI is not used for 9 third-party JavaScript and CSS files. Show details.
- 12 robots.txt rules and 8 bot protection mechanisms detected. No protection detected via User-Agent blocks or meta restrictions. Additional anti-scraping protection appears to be provided by external infrastructure. Show details.
Compliance Summary for www.bitgo.com
- GDPR Compliance Failed: Potential GDPR compliance issues were identified related to Cookie Disclaimer. The following checks were not performed, as no corresponding cookies with personal or tracking information seem to be sent by the website: Website Security.
- PCI DSS Compliance Failed: The website is compliant with PCI DSS Requirement 6.3, while being non-compliant with Requirement 6.4.


