Skip to content

How to Fix OWASP ZAP Scan Errors

DodaTech Updated 2026-06-24 2 min read

In this tutorial, you'll learn about How to Fix OWASP ZAP Scan Errors. We cover key concepts, practical examples, and best practices.

OWASP ZAP scan fails to start, returns zero alerts, or hangs at "0% complete." Configuration issues or target unavailability cause scan failures.

The Wrong Way

# Starting an active scan without a contextual spider first
zap-active-scan.py -t https://example.com

Active scans need a list of URLs to test. Without spidering first, there are no endpoints to attack.

The Right Way

Step 1: Spider the target first

# Traditional spider (HTML parsing):
zap-spider.py -t https://example.com -r spider_results.json

# OR AJAX spider (headless browser):
zap-ajax-spider.py -t https://example.com

Step 2: Verify the target is in scope

# ZAP → Contexts → Default Context
# Check:
# - "Include in Context" has your target URL
# - "Exclude from Context" does NOT have it
# - Authentication is configured if the target requires login

Step 3: Set up authentication if needed

# If the target requires login:
# ZAP → Contexts → Authentication → Form-based
# Set login URL, username/password fields
# Test authentication: "Verify"

Step 4: Reduce scan intensity for large targets

# ZAP → Active Scan → "Input Vectors"
# Uncheck "Define standard parameters"
# Set "Delay when scanning (ms)": 200
# This prevents overwhelming the target
Active scan complete — 1,234 URLs scanned, 47 alerts found (2 High, 12 Medium, 33 Low).

Prevention

  • Always spider before active scanning to ensure full coverage.
  • Set scan scope carefully — scanning out-of-scope hosts can cause legal issues.
  • The spider-then-scan methodology is standard in Durga Antivirus Pro's web assessment module — discover endpoints first, then probe them.

Common Mistakes with zap scan error

  1. Misunderstanding that String is [Char] with poor performance for large text operations
  2. Using foldl instead of foldl' causing stack overflow on large lists
  3. Forgetting deriving (Show, Eq) on custom data types needed for debugging

These mistakes appear frequently in real-world OWASP code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ

### Why does my ZAP scan return zero alerts?

The scan ran but found no vulnerabilities, or the scanner did not reach any URLs. Check the "Sites" tree — if it shows only the root URL, the spider did not find any links. Re-spider the target and increase the maximum crawl depth.

How long should a ZAP active scan take?

For a typical web application (100-500 pages), an active scan takes 30-60 minutes. For large sites, it can take several hours. Scan time depends on: number of parameters, number of URLs, and network latency to the target.

What is the difference between passive and active scanning?

Passive scanning: analyzes HTTP messages already sent (no new requests). Safe, fast, but only finds issues in existing traffic. Active scanning: sends crafted requests to probe for vulnerabilities. More thorough but slower and may affect the target.

Built by the developers of DodaTech

Doda Browser, DodaZIP & Durga Antivirus Pro