Updated Jul 14, 2026

Vulnerabilities

Fuzz marked URL parameters for open redirects

Async open-redirect fuzzer for parameterized URLs.

Agent

overview

What openredirex does

OpenRedireX replaces a marked keyword in each URL with redirect payloads and watches Location headers for off-site sends, including chained hops.

Point --payloads at your redirect tricks. Set --keyword when the injection marker is not FUZZ. Raise or lower --concurrency to match target tolerance.

Sit it after URL collection from a crawler or archive miner. URL list plus --payloads in, vulnerable redirects out as FILE and FOLDER.

source github.com/devanshbatham/OpenRedireX

use cases

Where openredirex fits

Fuzz a URL list for open redirects

Feed a file of parameterized URLs and let OpenRedireX swap each parameter for redirect payloads, flagging the ones that send the browser off-site.

Test with your own payloads

Point --payloads at a payloads file to run the exact redirect tricks you want, rather than a fixed built-in set.

Trace chained redirects

Read the reported Location header history to see the full hop path a payload triggered, not only the first redirect.

Tune concurrency for a big list

Raise or lower --concurrency to move a large URL file fast while staying within the target's tolerance.

reference

openredirex inputs and flags

5 inputs
NameTypeFlagDescription
urlSTRING·Single URL to test.
urls-fileFILE·File of URLs with parameters to test.
payloads-fileFILE--payloadsFile of redirect payloads to use.
keywordSTRING--keywordKeyword in URLs to replace with the payload (default FUZZ).
concurrencySTRING--concurrencyNumber of concurrent tasks (default 100).

Showing key inputs. openredirex exposes 5 inputs in total.

example

Run openredirex

openredirex · command
# fuzz a list of parameterized URLs with custom redirect payloadscat urls.txt | openredirex --payloads payloads.txt --keyword FUZZ --concurrency 50
sample output
[i] Reading URLs from input[i] Loaded 18 payloads[+] Testing https://example.com/login?next=FUZZ[VULN] https://example.com/login?next=//203.0.113.10       Location: //203.0.113.10[VULN] https://example.com/redirect?url=https:203.0.113.10       Location: https://203.0.113.10[-]   https://example.com/goto?to=FUZZ (no open redirect)[i] Done. 2 of 3 URLs vulnerable.

guidance

Choosing openredirex

Use OpenRedireX when you already have parameterized URLs and want open-redirect checks with your own payloads. Collect URLs first. For multi-class scanning, use a general scanner; for XSS parameters, use a dedicated XSS tool.

oralyzer

Open-redirect fuzzer that also checks CRLF. OpenRedireX focuses on async runs with custom payload files.

qsreplace

Rewrites query values to seed payloads. Pair it upstream to mark injection points for OpenRedireX.

dalfox

XSS-focused parameter scanner. OpenRedireX is the narrower open-redirect tool.

faq

openredirex questions

It swaps a keyword for redirect payloads and inspects Location header history. Off-site destinations under a crafted payload are flagged.

Run openredirex yourself

A URL list and a payloads file feed OpenRedireX, which fuzzes each URL and writes the ones vulnerable to open redirect as a queryable output.

Facts on this page come from the live Trickest tool library.