What is the HTTP Redirect Network Tracer?
A stealth network investigator that forces manual HTTP resolution to intercept and log intermediary routing instructions without ever executing dangerous browser payloads.
How it Works under the hood
When a URL is sent to the tracer, our Node.js engine issues an explicitly manual HTTP request configured to NOT follow redirects natively. If the server responds with an HTTP 301, 302, 307, or 308 code, the engine halts, captures the raw `Location` Response Header, logs the latency hop, and then recursively triggers the process against the new destination until an HTTP 200 payload is reached.
SysAdmin & Security Use Cases
- »Safely expand masked bit.ly or t.co links heavily utilized in phishing campaigns.
- »Audit corporate affiliate link sequences for internal loop (ERR_TOO_MANY_REDIRECTS) vulnerabilities.
- »Track unencrypted HTTP-to-HTTPS downgrade hops that expose referrers.
- »Verify CDN proxy behavior when changing backend Load Balancer targets.