HTTP Status & Redirect Checker Widget

An embeddable HTTP status and redirect checker for SEO guides and webmaster blogs. Readers enter a URL and see every redirect hop with its status code and Location header, the final destination, and how long the whole chain took.

SEO & Content Live check Checked by A2Z server Free · no ads

Customize your widget

Theme
Auto follows the visitor's light/dark setting.
Style
Attribution on your page
Optional and entirely your choice. The exact line is shown in the code below; it links to the tool with rel="nofollow".
More options
Starting values
Leave blank to use the widget's defaults. Visitors can still change every value.

Live preview

Exactly what your visitors will see

Embed code

<iframe src="https://a2z.tools/embed/w/http-status-checker" title="HTTP Status &amp; Redirect Checker by A2Z Tools" width="100%" height="470" style="border:0;width:100%" loading="lazy" allow="clipboard-write"></iframe>

A plain iframe. Works everywhere, including site builders that strip scripts. Adjust height if your content needs more room.

Works with

How it works

A2Z requests the URL through the same SSRF-guarded fetcher its network tools use, follows up to ten redirects one hop at a time - re-checking each new address before connecting - and returns every hop with its status code and Location header, plus the final status, the negotiated HTTP version and the total time. Seeing each hop matters for SEO, because a chain of several redirects, or a 302 where a 301 was intended, is invisible in a browser that simply lands on the final page.

What is checked

  • GET request; 3xx responses followed hop by hop, each new host re-validated (RFC 9110 section 15.4)
  • Private, loopback, link-local and reserved addresses are refused, including after a redirect
  • Result cached for two minutes per URL

Worked examples

Old URL after a migration

Inputs: http://example.com/old-page

Result: 301 -> https://example.com/old-page, 301 -> https://www.example.com/new-page, 200

Two hops: scheme change then path change. Pointing the old URL straight at the final address saves one.

Limitations

  • JavaScript and meta-refresh redirects are not followed - only HTTP 3xx responses.
  • Sites that block automated clients may answer differently than they do to a browser.
  • Requests come from A2Z's server location, which can affect geo-redirects.

Where publishers use it

  • SEO tutorials about 301 versus 302 redirects
  • Site migration checklists
  • Webmaster forums and help pages

Questions

What is the difference between 301 and 308?

Both are permanent redirects. A 308 also guarantees the request method and body are kept, which matters for form posts and APIs; for ordinary page moves either is fine. 302 and 307 are their temporary equivalents.

Why do I get 403 when the page works in my browser?

Some sites block automated requests. The widget shows exactly what A2Z's server received rather than guessing what a browser would see.

Does it follow JavaScript or meta-refresh redirects?

No, only HTTP redirects (3xx with a Location header). Client-side redirects need a browser to run the page.

How many hops is too many?

Search engines follow several hops, but each one adds latency and risk. One hop from an old URL to its final address is the usual goal after a migration.

Sources

  1. RFC 9110 - HTTP Semantics (status codes and redirection) - IETF

Cite or recommend this tool

If you reference this tool in an article, course or documentation, these formats are ready to copy. They are optional - nothing is added to your site unless you paste it.

A2Z Tools HTTP Status & Redirect Checker
https://a2z.tools/http-status-checker

Related widgets

More SEO & Content widgets →

Preview

CustomizeGet code