Check a 301 or 302 chain
See whether an old URL reaches the new one in a single hop or wanders through three, and which hop drops the query string.
Paste a link. A real browser opens it from the country and device you choose and reports every redirect on the way: status codes, JavaScript and meta refreshes, and the app-store hand-off at the end.
Most redirect checkers send one HTTP request and follow the Location header. That shows 301 and 302 hops and nothing else. Tracking links rarely stop there: the pre-lander redirects with JavaScript, a meta refresh sends the visitor on after a second, and a mobile offer ends with a deep link or an app-store page that only a browser can reach.
OfferProbe opens the link in a real browser, with a real fingerprint, from a real residential or mobile IP in the country you pick. Every hop the browser makes is recorded with its status code and kind, whether it came from a header, a script or a tag, and the page it ends on is the page a visitor would see.
Because the exit is a real connection, geo-targeted and carrier-targeted redirects fire the way they do for the audience: a link that sends German visitors somewhere else shows that path when you test from Germany.
Any tracking, affiliate or short link. Add the destination you expect, an app package, a store id or a landing domain, and the result comes with a verdict.
Country and, if it matters, state, city, carrier or connection type. Pick the device, OS version and browser the traffic will use.
Each hop with its URL, status code and kind, in order, ending on the final page. Usually well under a minute.
See whether an old URL reaches the new one in a single hop or wanders through three, and which hop drops the query string.
Branded short domains and tracker links unwrap to their real destination before anyone clicks.
Deep links and store hand-offs are followed on the device you choose, so an iOS link that opens the Play Store shows up as wrong destination.
A 301 is permanent: browsers and search engines treat the new URL as the address. A 302 is temporary: the old URL stays the address and the browser follows it each time. The chain lists the code of each hop so you can see which was used.
Yes. The link is opened in a real browser, so redirects made by a script, a meta refresh tag or a form submit are followed and recorded, along with the HTTP ones.
Redirects often depend on where the visitor is and what they use. Test from the country, carrier and device your traffic has and the chain should match; a different chain from a different setting is the answer, not an error.
There is no fixed limit on the chain. The browser follows the link until it settles on a page or the test’s time budget, about 90 seconds, runs out.
With an account you can submit batches of up to 100 links over the API and receive a webhook when each finishes.