Extract endpoints and parameters from crawls and saved traffic

xnLinkFinder pulls endpoints, and the parameters that go with them, out of a target. Point it at a URL or domain and it crawls to a configurable depth, or hand it a file of URLs, a Burp or ZAP export, a Caido CSV, or even a directory of files, and it parses links straight out of saved traffic. Either way it returns the routes an application exposes plus a target-specific wordlist built from the words it saw along the way.

Scope control keeps the output usable. You can filter found links to a scope, prefix relative links with the target domain, exclude paths, and stop early when too many responses come back 403, 429, or time out. The wordlist generation has its own switches to include or drop path words, parameters, digits, plurals, and comments, so the byproduct is tuned rather than noisy.

On Trickest, xnLinkFinder is a Discovery node that takes an input and writes a folder of results. Run it after you have collected URLs or proxy traffic, then feed the endpoints into a prober and the parameters into a fuzzer so later stages work from a real map of the application.