How to allow Astra's scanners on Vercel (System Bypass Rules, WAF and Deployment Protection)
Last updated: November 16, 2026
Introduction
If your application is hosted on Vercel, Vercel's firewall may block or challenge Astra's scanner and agentic pentest requests. Typical symptoms are failed connectivity checks, incomplete login recordings, scans that stall midway, or large numbers of 403, 429 or challenge responses.
Vercel enforces protections in several independent layers, and each one must be told to let Astra through. This guide covers all of them and includes a script and an AI-assistant prompt if you would rather automate the setup.
System Bypass Rules are available on Vercel's Pro and Enterprise plans. Check your Vercel plan or contact Vercel support.
Who this is for
Developers or admins managing a Vercel-hosted target (production, staging or preview) in Astra.
Why allowlisting on Vercel takes more than one rule
Vercel evaluates traffic in this order, and an allow at one layer does not carry over to the next:
System Bypass Rules cover Vercel's platform-level DDoS and system mitigations. Custom WAF rules cannot override these.
Custom WAF rules and managed rulesets (Bot Protection, AI Bots, OWASP) are covered by a custom rule whose action is Bypass. A rule whose action is Log only records matching requests and allows nothing.
Deployment Protection (Vercel Authentication or password protection, on by default for preview deployments) is separate again. IP allowlisting does not bypass it.
Prerequisites
Admin access to your Vercel project
Your target already added in the Astra dashboard
Astra's scanner IP ranges. Add all of the listed IPs, since missing even one can cause failures.
Step 1: Add System Bypass Rules

Log in to your Vercel dashboard and open your project.
Open Firewall in the project sidebar, then add a System Bypass rule (Add New → System Bypass, or under Configure → DDoS Mitigations and System Bypasses → Add Bypass Rule).
Enter one Astra IP address, optionally a domain, and a note such as
Astra IP.Repeat for every IP in Astra's IP Ranges.
System Bypass Rules take effect immediately. No publish step is needed.
Domain scoping and preview deployments: If you enter a domain, the bypass only applies to that exact host. Preview deployments get a new unique URL on every deploy, so a rule scoped to one preview URL will not apply to the next one. For previews, either leave the domain empty (applies to all of the project's domains) or use a stable alias such as a branch domain or a custom preview domain.
Step 2: Add a custom rule with the Bypass action
In your project, go to Firewall → Configure → Custom Rules and create a new rule.
Name it, for example,
Bypass bot and WAF checks for Astra Scanner IPs.Set the condition to IP Address → Is any of, and paste all of Astra's IPs.
Set Then to Bypass. Do not leave it on Log.
Move the rule to the top of your rule list so nothing else matches first.
Click Save Rule, then Review Changes → Publish. Custom rule changes are staged as drafts and do not take effect until published.
Step 3: Check Deployment Protection (preview deployments)
If you are scanning a Vercel preview URL, Deployment Protection (Vercel Authentication or a password) may stop the scanner before the firewall is even involved. Allowlisted IPs do not bypass it. You have two options:
Scan a deployment that is not behind Deployment Protection, such as production or a custom domain you have made public.
Use Vercel's Protection Bypass for Automation. Generate the secret in your project's Deployment Protection settings, and have the scanner send it in the
x-vercel-protection-bypassheader. If you need help adding a custom header to your Astra target, contact Astra support.
Automate it with the Vercel CLI
If you have the Vercel CLI installed and linked to your project (vercel login, then vercel link), this script adds all Astra IPs as System Bypass Rules and creates or updates the custom Bypass rule. It runs as a dry run by default and prints what it would do. The script only stages the custom rule. Publish it yourself after reviewing the diff.
#!/usr/bin/env bash
# allow-astra-on-vercel.sh
# Usage:
# ./allow-astra-on-vercel.sh # dry run
# ./allow-astra-on-vercel.sh --apply # apply
# Optional environment variables:
# DOMAIN=preview.example.com Scope system bypass rules to one domain (default: all domains)
# SCOPE=my-team Vercel team slug
# PROJECT_NAME=my-app Only needed if you also pass --publish
# Add --publish to publish staged custom rule changes (requires PROJECT_NAME)
set -euo pipefail
APPLY=false; PUBLISH=false
for arg in "$@"; do
case "$arg" in
--apply) APPLY=true ;;
--publish) PUBLISH=true ;;
esac
done
SCOPE_ARGS=(); [[ -n "${SCOPE:-}" ]] && SCOPE_ARGS=(--scope "$SCOPE")
DOMAIN_ARGS=(); [[ -n "${DOMAIN:-}" ]] && DOMAIN_ARGS=(--domain "$DOMAIN")
RULE_NAME="Bypass bot and WAF checks for Astra Scanner IPs"
# Source of truth: https://help.getastra.com/articles/4460616397-astra-ip-ranges
# Compare this list against that page before running, as Astra may update its IPs.
IPS=(
168.144.85.193 34.69.226.239 35.193.102.27 12.202.180.108
34.136.217.65 35.222.104.14 104.154.201.208 34.27.197.32
34.135.0.247 153.54.104.217 34.70.219.138 104.154.186.213
34.69.130.106 34.135.25.35 34.66.6.242 34.41.10.119 168.144.87.223
)
run() { if $APPLY; then "$@"; else echo "DRYRUN: $*"; fi; }
echo "== System bypass rules (take effect immediately) =="
for ip in "${IPS[@]}"; do
run vercel firewall system-bypass add "$ip" "${DOMAIN_ARGS[@]}" --notes "Astra IP" --yes "${SCOPE_ARGS[@]}" \
|| echo "WARN: could not add ${ip} (it may already exist, so check 'vercel firewall system-bypass list')"
done
echo; echo "== Custom rule with Bypass action (staged until published) =="
IP_JSON=$(printf '"%s",' "${IPS[@]}"); IP_JSON="[${IP_JSON%,}]"
CONDITION="{\"type\":\"ip_address\",\"op\":\"inc\",\"value\":${IP_JSON}}"
if vercel firewall rules inspect "$RULE_NAME" "${SCOPE_ARGS[@]}" >/dev/null 2>&1; then
echo "Rule exists. Updating its condition and action to Bypass."
run vercel firewall rules update "$RULE_NAME" --condition "$CONDITION" --action bypass --yes "${SCOPE_ARGS[@]}"
else
echo "Rule not found. Creating it."
run vercel firewall rules add "$RULE_NAME" --condition "$CONDITION" --action bypass \
--description "Allow Astra scanner IPs to bypass bot protection and WAF rules" --yes "${SCOPE_ARGS[@]}"
fi
run vercel firewall rules move "$RULE_NAME" --first --yes "${SCOPE_ARGS[@]}" \
|| echo "WARN: could not move the rule to first position, so check its priority manually"
echo; echo "== Review staged changes =="
vercel firewall diff "${SCOPE_ARGS[@]}" || true
if $PUBLISH && $APPLY; then
: "${PROJECT_NAME:?set PROJECT_NAME to publish}"
vercel firewall publish --confirm-name "$PROJECT_NAME" "${SCOPE_ARGS[@]}"
else
echo; echo "Review the diff above, then publish with:"
echo " vercel firewall publish --confirm-name <your-project-name>"
fi
echo; echo "Verify with: vercel firewall status"Automate it with an AI coding assistant
If you use an AI coding assistant that can run terminal commands (such as Claude Code), you can paste the prompt below from a directory linked to your Vercel project. It makes the assistant show you its plan and stop for your approval before changing anything.
Allowlist Astra Security's scanner IPs on my Vercel project using the Vercel CLI (`vercel firewall ...`), so Astra scans and pentests stop getting blocked.
Context:
- Vercel enforces protections in separate layers. I need both:
1. System bypass rules (one per IP, applied immediately) for Vercel's system-level mitigations.
2. A custom firewall rule named "Bypass bot and WAF checks for Astra Scanner IPs" with condition "IP Address is any of <all Astra IPs>" and action `bypass` (NOT `log`). Custom rule changes are staged until `vercel firewall publish`.
- Fetch the official IP list from https://help.getastra.com/articles/4460616397-astra-ip-ranges and use every IP on that page.
Steps:
1. Confirm the CLI is logged in and linked to the right project and team (`vercel whoami`, `vercel link` if needed).
2. Inspect the current state: `vercel firewall status`, `vercel firewall system-bypass list`, `vercel firewall rules list`.
3. Ask me whether to scope the system bypass rules to one domain (`--domain`) or leave them for all domains. Note that per-deployment preview URLs change on every deploy.
4. Show me the exact commands you plan to run and WAIT for my approval. System bypass changes are live immediately.
- `vercel firewall system-bypass add <ip> [--domain <domain>] --notes "Astra IP" --yes` for each IP not already present
- Create or update the custom rule with action `bypass` and move it to the first position
5. Run `vercel firewall diff` and show me the staged changes. Do NOT run `vercel firewall publish` until I approve.
6. After I publish, verify with `vercel firewall status` and `vercel firewall system-bypass list`.
Constraints: do not touch attack mode, system mitigations, IP blocks or other rules. Do not print or store tokens. If a command fails (plan limits, permissions), stop and tell me instead of working around it. Also check whether Deployment Protection is enabled for previews and report it, but do not change it.Verify it worked
Run
vercel firewall statusto see the evaluation order, with bypass rules evaluated first.During a scan, check Firewall → Traffic in the Vercel dashboard (or
vercel firewall traffic list --since 1h --action deny). None of Astra's IPs should appear as denied, challenged or rate-limited.Return to your Astra dashboard and re-run the scan or connectivity check.
Expected Outcome
Once all layers are configured, Astra's scanners should connect to your site and complete scans and pentests reliably.
Troubleshooting
Scan still failing after adding the rules
Confirm all IPs from Astra's IP Ranges list are present in both the system bypass rules and the custom rule.
Confirm the custom rule's action is Bypass (not Log or Deny) and that you published it.
Make sure the custom rule sits above other rules that could match first.
Allow a few minutes for Vercel's firewall rules to propagate before retrying.
It works on one preview deployment but fails on the next
Your system bypass rule is probably scoped to a single per-deployment URL. Leave the domain empty or use a stable alias.
Requests get a Vercel login page or 401
Deployment Protection is blocking the scan. See Step 3.
Login recording fails but the connectivity check passes
The WAF may be applying additional bot protection during login. Make sure the bypass rules apply to all paths, not just the root URL.
Aggressive scans are still rate-limited
System-level mitigations can still trigger if any Astra IP is missing from the system bypass rules. Check
vercel firewall traffic list --action denyfor any Astra IP that is not covered.
For more detail, see Vercel's documentation on System Bypass Rules and the vercel firewall CLI command.