Free tool

Redirect checker

Follow the chain hop by hop. See status codes, the Location target, HTTPS upgrades, and whether a canonical change used a temporary 302.

What this redirect check actually does

We request the URL with redirects disabled, read Location, resolve the next host (and refuse private IPs), and repeat up to ten hops. The HTML body is not stored.

A single www or HTTP→HTTPS hop is normal. A long chain wastes crawl budget. HTTPS dropping back to HTTP is a fail. Pintelly's main product is the feedback widget.

What we look at

Hop count

Zero extra hops is a pass. Three to five is a warning. Six or more fails.

HTTPS

The chain must not downgrade. HTTP should end on HTTPS.

Final status

The last hop should be 2xx (or a 3xx we could not follow only if Location is missing — that fails).

301 vs 302

Host or scheme changes with 302/307 are flagged. Prefer 301 or 308.

How it works

1

Paste a public URL

http or https. Private IPs and localhost are refused — including mid-chain.

2

We walk Location

Each hop is a GET. Five traces per host per day.

3

You see the chain

Status, URL, and whether it was HTTPS. Cookie values are not included.

Frequently asked questions

Is this free?+

Yes. Five traces per host per day. No account.

Do you store the chain?+

No. Hops are scored in memory and discarded.

Why did a 302 to HTTPS warn?+

Scheme changes that are meant to be permanent should be 301 or 308 so crawlers consolidate on the HTTPS URL.

What if there is a loop?+

We stop and return an error. Loops are not scored as a pass.

Can I check any URL?+

Public HTTP(S). A hop to a private IP is refused, same as the first URL.

Other free checks

Feedback Widget

Pintelly's main product: visitors pin what is broken, with a screenshot.

The chain is a snapshot. Visitors still find the rest.

The checker is free. The feedback widget is how agencies catch what is actually broken — on the page, with a screenshot.

Five free redirect traces per site per day. The chain is not stored.