This folder contains allowlist-only validators for assets you own or are explicitly authorized to test.
authorized_batch_http_validator.py is useful for checking whether a list of internal endpoints or approved callback/collaboration servers are reachable.
TXT input:
python authorized_batch_http_validator.py -i targets.txtIf -o is omitted, the CSV is saved in the same folder as targets.txt.
CSV input, reading column 0:
python authorized_batch_http_validator.py -i targets.csv --column 0 -o results.jsonl --format jsonl --threads 16Force HTTP instead of HTTPS when inputs have no scheme:
python authorized_batch_http_validator.py -i targets.txt --scheme http -o results.csvUse a proxy:
python authorized_batch_http_validator.py -i targets.txt --proxy http://127.0.0.1:8080 -o results.csvinput_value: original input valuenormalized_url: probed URLdns_ok: whether DNS resolution workedresolved_ips: resolved IP listprobe_ok: whether HTTP/HTTPS probe completedhttp_status: HTTP status codefinal_url: final URL after redirectselapsed_ms: probe timecontent_type,server,title: basic response metadataerror: request error if any
Do not use this with blind third-party FOFA/Shodan lists. Use only with approved targets.
authorized_collaborator_healthcheck.py checks connectivity for approved Collaborator/OAST-style servers:
- DNS resolution
- TCP ports
53,80,443,25,587,465by default - HTTP and HTTPS basic responses
- SMTP/SMTPS banner/connectivity where available
Example:
python authorized_collaborator_healthcheck.py -i collaborators.txtIf -o is omitted, the CSV is saved in the same folder as collaborators.txt.
Default verdict logic:
PASS: all checks passedPASS_WITH_WARNINGS: one or two checks failedFAIL: more than two checks failed
Change tolerance:
python authorized_collaborator_healthcheck.py -i collaborators.txt --max-fail 1Custom ports:
python authorized_collaborator_healthcheck.py -i collaborators.txt --ports 53,80,443 -o collaborator-results.jsonl --format jsonlImportant: this only proves network connectivity. It cannot prove that a third-party server will return interaction records to your Burp client. For reliable testing, use Burp's official Collaborator service or a private server you control.