Hardenly
Get Started
HomeSecurity IntelHow to Handle Vercel Security Checkpoint Error
vercelddos protectionsecurity checkpointattack challenge mode

How to Handle Vercel Security Checkpoint Error

September 28, 2025

On this page

Table of Contents

How to Handle Vercel Security Checkpoint ErrorWhat is the Vercel Security Checkpoint Error?Why This HappensHandling Vercel Security Checkpoint ErrorIf You Have Attack Challenge Mode EnabledIf You're Experiencing False Positives from DDoS Mitigation

How to Handle Vercel Security Checkpoint Error

TL;DR: When you encounter "We're verifying your browser" blocking all traffic to your site, it's usually when Attack Challenge Mode is enabled or when Vercel's DDoS mitigation falsely flags legitimate traffic. The solution is temporarily disable Attack Challenge Mode and/or pause system-level mitigations for 24 hours.

What is the Vercel Security Checkpoint Error?

If you're experiencing the vercel security checkpoint error where users see "We're verifying your browser: Vercel Security Checkpoint" blocking all traffic to your site, it means Vercel's DDoS protection has automatically activated to protect against what it perceives as malicious traffic.

This vercel browser verification error can completely block legitimate users from accessing your production site.

Common Symptoms:

  • All users see the security checkpoint page
  • Requests return HTML of Vercel checkpoint pages instead of your content
  • GraphQL or API endpoints experience timeouts
  • TLS connection errors with ECONNRESET codes

Why This Happens

This can happen due to two reasons:

  1. You have enabled Attack Challenge Mode. In this mode, every user visiting the site must complete a security challenge before accessing your site. All requests from genuine users will also be challenged.

  2. When Vercel's system-level DDoS mitigation thinks it's a potential malicious request. This false positive behavior can occur due to the following reasons:

  • Traffic patterns change suddenly
  • Using proxies/CDNs like Cloudflare infront of your Vercel apps
  • High volume of API requests from similar sources

Handling Vercel Security Checkpoint Error

If You Have Attack Challenge Mode Enabled

If you aren't facing any DDoS attack, disable the Attack Challenge Mode:

  1. Go to your Vercel project dashboard
  2. Navigate to Firewall tab
  3. Click the menu button with the ellipsis icon at the top right of the Firewall tab
  4. Select Disable Attack Mode
  5. Wait for changes to propagate (usually under 5 minutes)

If You're Experiencing False Positives from DDoS Mitigation

When Vercel's automatic DDoS protection incorrectly flags legitimate traffic, the issue should automatically resolve within an hour as the system learns your traffic patterns.

If the issue persists beyond an hour, you can create a "bypass system-level mitigations" rule so Vercel DDoS pauses automatic mitigation:

  1. Go to your Vercel project dashboard
  2. Navigate to Firewall tab
  3. Click the menu button with the ellipsis icon at the top right of the Firewall tab
  4. Select Pause System Mitigations
  5. Review the warning in the dialog and confirm to pause all automatic mitigations for the next 24 hours

Important: The bypass system-level mitigations feature is only available for Pro and Enterprise customers and not Hobby users.

⚠️ Warning: Bypassing system-level mitigations temporarily removes DDoS protection from your project, leaving it vulnerable to actual attacks.

On this page

Table of Contents

How to Handle Vercel Security Checkpoint ErrorWhat is the Vercel Security Checkpoint Error?Why This HappensHandling Vercel Security Checkpoint ErrorIf You Have Attack Challenge Mode EnabledIf You're Experiencing False Positives from DDoS Mitigation

Quick Security Check

See if your Vercel app has similar vulnerabilities.

Scan Your App

Security Scanner

Don't just read about it—fix it

Scan your Vercel deployment for the vulnerabilities discussed in this article. Free scan, results in 60 seconds.

$

Your scan includes:

  • Exposed secrets detection
  • Security header analysis
  • Server/client boundary checks
  • Step-by-step remediation