Summary of vercel.com [Desktop version] Website Security Test
Provided "as is" without any warranty of any kind.
Date/Time:Nov 8th, 2026 19:19 GMT+0
Server IP:64.239.109.65
Reverse DNS:-
Location:Mount Hope, United States
Version:for desktop
Your final score:
- A
- B
- C
- F
A
Test Results Summary for vercel.com
- 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.
- No obvious GDPR-related compliance issues were detected across Privacy Policy, Website Security, TLS Encryption, Cookie Protection, Cookie Disclaimer. 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, Access-Control-Allow-Origin, Referrer-Policy, Cache-Control, Cross-Origin-Opener-Policy (COOP). Deprecated HTTP headers detected: X-XSS-Protection. Show details.
- Content-Security-Policy is enforced but configuration issues were identified: overly permissive directives, directive errors. A report-only Content-Security-Policy is not present. Show details.
- 5 cookies detected; g_state, vercel_session_id, _v-consent, _v-visitor-id-renewed, _v-visitor-id have security or privacy-related configuration issues. Show details.
- 5 external requests detected; all requests completed successfully. SRI is not used for 3 third-party JavaScript and CSS files. Show details.
- No significant anti-scraping protections were detected. Show details.
Compliance Summary for vercel.com
- 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.
