Is it up? Check a site and its redirect chain
Requests the four variants of a domain (http and https, with and without www), follows every redirect, and shows the status, final URL and response time for each. Catches the half-configured sites where one variant times out, loops, or lands somewhere different from the others.
Any public page. Try .
What to do about it
The check found it. These are the ways to fix it, keep it fixed, or run the same check for every business you serve.
TagFrog Pro
Server-side tracking, consent and every ad platform API, proven with a real test order and kept current. Watch included when it launches.
See TagFrog ProWatch
Re-runs this check every week and emails you the moment the answer changes: site down, tag gone, score dropped, certificate expiring.
Join the waitlistWebsite
No website yet? $499, live in two days, or rebuild a tired one for the same price. Hosting and TagFrog on from day one, Watch when it launches, changes by chat, never a call. Have an agency? They can resell this.
Get online, $499OpsBlu
This same check, run for every local business in a territory. Leads with a reason to call, as CSV, API and MCP.
Go to opsblu.comWhat we check
- http://, https://, www and bare host, all four
- HTTP status and every hop of the redirect chain
- Final URL agreement across the variants
- DNS, connect, TLS and first-byte timings
- Redirect loops and chains longer than two hops
- Whether http:// lands on https://
Cost of one run: 1-4 requests. Results for the same URL are kept for a few minutes, so running twice is free and instant.
Questions
Why do you test four URLs?
Because visitors type all of them. A site that works at https://www. but times out at http:// without www loses the people who typed the bare name, and search engines see two sites.
How many redirects are too many?
Each hop costs a round trip. http to https to www is two and fine. Anything longer, or a chain that passes through a tracking domain, slows every first visit and leaks link equity along the way.
The check says up but my visitors say down. Why?
We test from one location. A regional DNS or CDN issue can affect their city and not ours. If it keeps happening, scheduled checks from several locations (Watch this, coming soon) show the pattern.