Bulk redirect checker: every hop, status code and final URL for up to 500 links
In short: Paste URLs and follow each one's redirects: every hop with its 301, 302, 307 or 308, the final URL and its status, with long chains, loops and HTTPS-to-HTTP downgrades flagged. Limit: HTTP redirects only: JavaScript and meta refresh redirects aren't followed.
A bulk redirect checker follows each URL's redirects and shows every hop. Paste up to 100 links, or 500 after a free Google sign-in, and each row lists the status codes on the way (301, 302, 307, 308), the final URL and its status, with loops, chains of more than three hops and HTTPS-to-HTTP downgrades flagged. Use it on tracking links, short links and old pages. CSV out.
Price: this tool is free. Checking a whole email list is from $9/mo, and the first 100 checks are free with Google, no card. Check your list free nowSee pricing
Sample result
http://acme.example/pricing takes 2 redirects to reach https://www.acme.example/pricing.
- URL
- http://acme.example/pricing
- Hops
- 301 → 301 → 200
- Final
- www.acme.example/pricing
What this means for you
One redirect from the old URL to the final page is best; long chains slow every click.
- Every hop with its status code
- Final URL and final status
- Loops, long chains, HTTPS downgrades
- HTTP redirects only; CSV out
- 301
- Redirect chain
- Tracking links
By SimpleVerifier Team · Last updated
Also in: Português (Brasil) · Español · Deutsch · Français · Türkçe · 简体中文 · Русский · Nederlands · Italiano · Tiếng Việt · Bahasa Indonesia · Polski · العربية · Українська · Čeština · Magyar · 日本語 · 한국어
Checking the links in a cold email before you send it?
- A link that redirects through three hosts or lands on an error page hurts a campaign, but so do bounces. Upload the recipient list at /verify to remove addresses that would bounce.
- The first 100 email checks are free with a Google sign-in, no card. To check every link inside an email's HTML at once, use the email link checker.
How do I check where many URLs redirect?
- Paste full URLs, one per line, up to 100 a run, or 500 after a free Google sign-in. A line without http:// or https:// is checked as https://.
- Press Check redirects. Each URL is requested once and its HTTP redirects are followed, up to ten hops, ten URLs a request.
- Read each row: OK, Redirects, Broken (the final page answers 4xx or 5xx), Loop, Too many hops or No answer, with every hop and its status code listed.
- Filter to broken or long chains and download the CSV with the hop count, every hop, the final URL and the final status.
Example
- You enter
- Two URLs:
http://acme.example(redirects to HTTPS) andhttps://acme.example/old-page(moved, then removed). - You get
- http://acme.example: Redirects, one 301 hop to https://acme.example/, which answers 200. https://acme.example/old-page: each hop is listed with its status code, and the 404 at the end shows as Broken. Download the CSV.
- Limits
- Up to 100 a run without an account and 500 when signed in with Google, counted over a minute. 10 URLs a request, up to 10 redirects each, at most 60 requests a minute to one host.
How does the redirect checker follow a URL?
It sends one GET request to the URL, and when the answer is a redirect (a 3xx status with a Location header), it requests the new address, up to ten times. Every hop is recorded with its status code. RFC 9110 defines the codes: 301 and 308 are permanent, 302 and 307 temporary, and 303 points to a different resource.
Requests identify themselves honestly as SimpleVerifier, send no cookies, use only ports 80 and 443, never connect to private or reserved addresses, and read at most 16 KB of the final page. Redirects made by JavaScript or a meta refresh tag inside a page aren't followed, because they need a browser.
What do the flags mean?
Loop: a URL redirects back to one it already visited, so browsers give up with an error. Too many hops: the chain went past ten redirects. Long chain: more than three hops, which works but is slower and loses more visitors on mobile. HTTPS to HTTP: a hop drops from https to plain http, which browsers warn about and which exposes the visitor's request.
Broken means the redirects worked but the final page answered with an error such as 404 or 500. Some sites refuse automated requests and answer 403 or 429 to anything that isn't a browser, so a 403 here can still load for a person; open it to confirm.
Why check redirects on cold email links?
Click tracking rewrites every link to go through the tracking domain first, and link shorteners add another hop. Spam filters can follow those redirects and judge every domain on the way, so one blocklisted hop affects the whole link. Checking where each link really goes, and how many hosts it passes, catches a broken or badly chained link before it costs you replies.
For the CNAME behind a custom tracking domain, use the bulk CNAME lookup or the tracking domain checker.
Can I use it after a website migration?
Yes. Paste the old URLs and confirm each one lands on its new page with a single 301 or 308, not a chain or a 404. To check only that a list of domains' home pages load, the bulk website status checker adds parked-domain signals, and the WWW redirect checker tests the http, https, www and non-www versions of each domain.
To keep the tool fair for everyone, each run counts towards a per-minute limit, and the tool sends at most 60 requests a minute to any one host, across all users.
How is this different from the bulk website status checker?
| Bulk redirect checker | Bulk website status checker | |
|---|---|---|
| Input | Any full URL, with path and query | Domains (home page only) |
| Redirects followed | Up to 10, every hop listed | Up to 5, every hop listed |
| Flags | Loops, long chains, HTTPS downgrades | Parked and for-sale signals |
| Best for | Tracking links, short links, migrations | Lead lists and domain portfolios |
Who uses this tool, and for what?
- Cold emailers
- Check where tracked and shortened links really go, and how many hosts they pass, before a campaign.
- SEO teams
- Confirm old URLs reach their new pages with one 301 after a migration, with no chains or 404s.
- Marketers
- Test the links in ads, QR codes and newsletters before they go out.
- Agencies
- Audit a client's redirect map in one run and send the broken rows as a CSV.
What can’t this tool tell you?
- HTTP redirects only: JavaScript and meta refresh redirects aren't followed.
- Sites that block automated or cloud traffic can answer 403, 429 or time out while working in a browser.
- Each URL is requested once with GET; a site that answers differently by country or device may redirect others elsewhere.
- Private and reserved addresses, and ports other than 80 and 443, are never requested.
- Up to 100 URLs a run without an account, 500 signed in, and at most 60 requests a minute to one host.
Common questions
- How do I check where a list of URLs redirects?
- Paste them into a bulk redirect checker like this one. It follows each URL's redirects and shows every hop with its status code, the final URL and its status, with a CSV download.
- Is this bulk redirect checker free?
- Yes. Up to 100 URLs a run without an account, and up to 500 a run when you sign in with Google, with no card.
- What is the difference between a 301 and a 302 redirect?
- A 301 is permanent: search engines move the old URL's ranking to the new one. A 302 is temporary. 308 and 307 are their equivalents that keep the request method.
- Does it follow JavaScript or meta refresh redirects?
- No. It follows HTTP redirects only, the 3xx status codes with a Location header. Redirects made inside the page need a browser.
- Why does a link show 403 here but work in my browser?
- Many sites refuse automated requests. A 403 or 429 here doesn't mean the page is down; open it in a browser to check.
- How many redirects is too many?
- Browsers give up after about 20, and this tool after 10. More than three hops already slows the page down, so one redirect from the old URL to the final one is best.
Sources
A tidy list can still be full of dead addresses.
Extracting, deduplicating and syntax checks all work on the text of an address. None of them can tell whether the mailbox exists. Only the server that hosts it can answer that, through an SMTP check, and that is what the paid product does.
- Upload the cleaned file as it is: CSVs up to 100,000 rows
- A real SMTP mailbox check on every row, with catch-all detection
- Small list? Starter at $9/mo covers 2,500 emails a month, cancel anytime
Plans from $9 a month, cancel anytime, no contract. Sign in with Google and your first 100 email checks are free, no card. The free tools stay free either way.