Bulk URL Checker
Check HTTP status codes, follow redirects, and see whether UTM parameters change along the way.
0 URLs entered
Load example only fills in sample URLs. Nothing is checked until you select Check URLs, and real results vary by destination.
URLs are sent to our server to check their HTTP responses. Avoid submitting private links or URLs containing passwords or access tokens.
What this checks
Each URL is requested once. The checker follows up to 5 HTTP redirects, records the status at every hop, and compares the UTM parameters on the first URL with those on the final one.
- HTTP redirects only. JavaScript and meta refresh are not followed.
- Headers only. Page content is never downloaded or rendered.
- One 15 second limit covers each URL and all of its redirects.
- No scheduled monitoring. Checks run only when you ask.
Results
Paste your URLs and select Check URLs to see status codes, redirects, and UTM comparisons here.
How to use this tool
- Paste your URLs. One full URL per line, up to 20 per run.
- Select Check URLs. Each row updates as its response arrives. You can stop a run at any point.
- Review and export. Filter the results, open Details for the redirect chain and UTM comparison, then copy or download a CSV.
Common questions
Each URL needs a real HTTP request, and some destinations are slow. Keeping each run to 20 URLs keeps results quick and keeps the shared checker available for everyone. Run several batches if you have a longer list.
The checker follows up to 5 HTTP redirects and records the status of every hop. It follows only real HTTP redirect responses with a valid location. Redirects performed by JavaScript or a meta refresh tag are not followed, so the final URL shown is the end of the HTTP chain only.
Some servers refuse automated requests, or limit how often they answer. A 403 means the server refused this particular check, and the page may still load normally in your browser. A 429 means the destination is limiting requests and is worth retrying later.
It compares the UTM parameters in the URL you entered with those in the final URL after redirects. That shows whether the link preserved your tags. It does not confirm that analytics recorded the visit, and it cannot see parameters a destination captures server side before redirecting.
No. A 200 only means the server answered successfully. This tool reads response headers and never downloads or renders the page, so it cannot tell you whether the content, the product, or the tracking script on that page is right.
On our server. A browser cannot inspect the HTTP responses of other websites directly, so each URL you submit is sent to our own endpoint, which makes the request and returns the status and redirect information. Avoid submitting private links or URLs containing tokens.
No. This is a one-off check that runs when you select Check URLs. There are no accounts, no saved lists, and no scheduled or repeated checks.