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.
Redirect checker that follows the link like a phone would
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.
Another question? All four run the same test; each page only sets how the form starts.
Why a redirect checker needs a real browser
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.
How it works
- 01
Paste the link
Any tracking, affiliate or short link, with the parameters your traffic carries.
- 02
Choose where from
Country and, if it matters, state, city, carrier or connection type. Pick the device, OS version and browser the traffic will use.
- 03
Read the chain
Each hop with its URL, status code and kind, in order, ending on the final page. Usually well under a minute.
What you get
- Every hop, in order
- The URL of each redirect, its HTTP status or the script or tag that caused it, and the final URL.
- The final page as evidence
- On a paid plan, a screenshot of the landing page and, in Full mode, a recording of the session.
- A plain answer
- Success when the link reaches a page, Broken when it does not. When our side fails instead, the test is Inconclusive and never billed.
- The exit it was seen from
- The country, carrier, connection type and IP the browser used, so a geo-specific redirect can be reproduced.
What people check with it
Trace a short link
Branded short domains and tracker links unwrap to their real destination before anyone clicks.
Debug a mobile offer
Deep links and store hand-offs are followed on the device you choose, so an iOS link that opens the Play Store shows the Play Store as its final page.
Questions
What is the difference between a 301 and a 302 redirect?
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.
Does the checker follow JavaScript and meta refresh redirects?
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.
Why does the chain differ from what I see on my phone?
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.
How many redirects can a link have?
As many as a real browser follows. Script and meta-refresh hops are followed until the link settles on a page; like any browser, it gives up after about 20 HTTP redirects in a row (“too many redirects”), and no test runs past five minutes.
Can I check many links at once?
On a paid plan you can run a batch of up to 100 links from the Batch page; each result lands in your history.