Free WWW Redirect Checker

Four URL variants, one canonical — that's the goal, and most sites get it wrong. Browsers can't probe all four www/non-www × http/https variants, so NToolHub's WWW Redirect Checker generates the four curl tests plus the exact pass criteria: which variant should 200, which should 301, and how to spot chains.

ℹ️
Why no live result here? Browsers cannot probe the four www / non-www × http / https variants of a site — cross-origin requests are blocked by CORS. Instead, this tool builds the exact commands and one-click lookup links you need — everything runs from your own terminal or trusted lookup services.
Private by design. This page performs no live network lookups and uploads nothing — it only generates commands and links that run on your own machine or on trusted lookup sites you open yourself.

How to Use the WWW Redirect Checker

  1. Enter your domain (without www).
  2. Click Build Variant Tests to get curl commands for all four variants.
  3. Run each: only one should return 200, the rest 301.
  4. Fix chains so every variant lands on the canonical URL in one hop.

Features

Enter your domain (www stripped automatically) for four tailored curl commands testing http/https × www/non-www, with a clear healthy-setup checklist and chain warnings for multi-hop upgrades.

Benefits & Use Cases

You verify the complete canonicalization matrix in under a minute — catching the split-indexing and duplicate-content issues that silently halve your ranking power.

Tips

Pick one canonical (https + www or non-www), 301 the other three directly to it in single hops, and ensure http→https upgrades happen on every variant.

Frequently Asked Questions

Which www variant should be canonical?

Either works for SEO — pick one and commit. Non-www is shorter; www plays nicer with some DNS/CDN setups. Consistency matters, not the choice.

Why test all four variants?

Each variant can be indexed separately if it returns 200, splitting your ranking signals four ways. Three must 301 to the canonical one.

What's wrong with redirect chains here?

http://example.com → https://example.com → https://www.example.com is two hops for every visitor and crawler. Each variant should redirect directly to the final URL.

How do I fix variant issues?

With server redirect rules (.htaccess, nginx config, or Cloudflare rules): force HTTPS and your chosen www variant in single-hop 301s, then re-test.

Related Tools

↪️

Redirect Checker

Redirect Checker helper: real curl chain-tracing commands and tracer links. Audit every redirect hop honestly — free from NToolHub, no sign-up.

Open tool →

URL Status Checker

URL Status Checker helper: real curl status commands and a code reference guide. Verify 200s, 404s and 5xx honestly — free tool, no sign-up.

Open tool →

HTTP Header Checker

HTTP Header Checker helper: real curl commands plus SecurityHeaders.com scans. Honest header inspection walkthrough — free, no sign-up needed.

Open tool →

DNS Lookup

DNS Lookup helper: copy-ready dig and nslookup commands plus one-click DNS links. Honest, free DNS research tool by NToolHub — no fake results.

Open tool →

Canonical URL Generator

Generate canonical link tags and audit URL variants for duplicate-content issues. Free Canonical URL Generator from NToolHub — no sign-up needed.

Open tool →