Contact
RedirectChecker is built and maintained by one person. Email reaches him directly — there is no ticket queue in between.
mail@abhinavvasudevan.comWhat to write about
Everything goes to the same address. The subject lines below just help sort it — clicking one opens your mail client with the subject already filled in.
Bugs and wrong results
A chain that traced incorrectly, a URL that failed to resolve, or a status code reported wrong. Include the exact URL you entered and the check ID from the results page — that ID lets the stored trace be looked up directly.
Email about thisFeature requests
Bulk checking, exports, scheduled monitoring, extra locales. Requests that describe the job you are trying to finish are far more useful than ones that name a feature.
Email about thisAPI early access
The API is still being built. Early users help decide the endpoint shape, the auth model, and the pricing, so a note describing your use case genuinely changes what gets shipped.
Email about thisPrivacy and data requests
Questions about what is stored, or a request to remove a saved check or delete an account. Checks are stored with a one-way hash of the IP address, never the address itself.
Email about thisResponse times
This is a side project, not a staffed support desk. Most email gets a reply within a few days. A bug that returns a wrong redirect chain jumps the queue — that is the one thing the tool exists to get right.
Reporting a wrong result
A report is much faster to act on when it includes:
- The URL exactly as you typed it, including the protocol if you used one.
- The check ID shown on the results page — every check is stored under that ID, so it can be pulled up and compared against a fresh trace.
- What you expected the chain to be, and what came back instead.
Who runs this
RedirectChecker is built and maintained by Abhinav Vasudevan. You can also reach him on Twitter or GitHub, though email is read most reliably.
For what the service does with the URLs you submit, see the privacy policy.