TapCub is live — analytics, insights and live chat, free on one platform

Free tool HTTPS and www redirect checker: one site, one address

Your site can be typed four ways: http or https, with or without www. Enter the domain and the checker requests all four, follows the redirects and shows whether they end on the same URL, each in one permanent hop. It flags temporary redirects, two-step chains, a www that does not resolve and an http version that never upgrades.

  • 4 variants per check
  • One-hop 301 rule
  • Sent only when you click

Check the four versions of a domain

Enter a domain (www or not, it makes no difference). A subdomain such as blog.example.com is tested for http and https only. Until you click Check, the result is a sample for github.com.

Checker
What is sent, and to whom. Nothing is requested when the page opens: the result below is a dated sample. When you click Check, the address goes to TapCub’s checking service check.tapcub.com, which fetches it from Cloudflare’s network with the user-agent shown and a From: tools@tapcub.com header, then returns the status codes, response headers and at most 512 KB of the page. One check uses four requests (two for a subdomain), plus one for the trailing-slash test. The service records only the host name, status and timing for rate limiting, not the path, query or page content, and stores no results. Limits: 10 requests a minute and 200 a day per IP address.

A domain or any URL on it; only the host name is used.

Usually /. Test a deeper page, such as /blog/post, to check that the path survives the redirect.

Sample result for github.com, fetched on 2026-11-17. Click Check to test it live, or enter your own address.

Canonical URL

https://github.com/

The address most variants end on.

Verdict

  • WarningCanonical URL is https://github.com/, but 1 variant(s) need fixing. See the table.
  • Warninghttp://www.github.com/ takes 2 redirects. Point it straight at the canonical URL.

Variant by variant

Good: the canonical URL itself, or one 301 / 308 to it.

VariantTested URLStatus codesFinal URLResult
http, no wwwhttp://github.com/301 → 200https://github.com/One 301 hop
https, no wwwhttps://github.com/200https://github.com/Canonical URL
http, wwwhttp://www.github.com/301 → 301 → 200https://github.com/2 hops
https, wwwhttps://www.github.com/301 → 200https://github.com/One 301 hop
The checks, tables and explanations are worked out in your browser from what the service returns. Nothing you check is saved to an account or shared.

Share these inputs: the values go after the # in the link, so they never reach a server.

Version v1.0Updated Update history

Read the result

What a clean setup looks like

Exactly one variant answers 200. The other three each send a single permanent redirect to it.

Why one canonical host matters

To a search engine, http://example.com and https://www.example.com are different URLs. Without redirects the same pages exist four times, links and signals are split, and the engine guesses which one to show.

Why one hop

http://example.com → https://example.com → https://www.example.com works, but every visitor typing the bare domain waits for two round trips. Point every variant straight at the final address.

Why permanent

A 301 or 308 tells search engines to index the target. A 302 or 307 keeps the variant itself as canonical, which is the opposite of what you want here.

www or not

Either is fine. Google does not prefer one. What matters is choosing one and redirecting everything else to it, and using that same version in canonical tags, sitemaps and internal links.

HSTS preload has one extra rule: the bare domain must first redirect http to https on the same host (http://example.com → https://example.com), even if you then send people to www. That two-step path is the one case where a second hop is deliberate.

How to use it

Three steps

Nothing is requested until you click Check.

  1. 1

    Enter the domain

    Type it with or without www; the checker builds the four variants itself.

  2. 2

    Optionally pick a path

    Test a deep page to make sure redirects keep the path instead of dumping everyone on the homepage. Tick the slash option to test /page versus /page/.

  3. 3

    Fix the red and yellow rows

    Use the redirect rule generator to write the rules for your server or CDN, then check again.

Method

How the canonical URL is chosen

Each variant is fetched from Cloudflare’s network through check.tapcub.com, following redirects (up to 5 hops):

  • The canonical URL is the final address reached by the most variants; on a tie, https wins, then the one that answers without redirecting
  • A variant passes if it is the canonical URL (200) or reaches it in one 301 / 308 hop. More hops or a 302 / 307 is a warning; a different final URL, an error page or no DNS is a failure
  • The trailing-slash test requests the path with the slash toggled on the canonical host; a redirect to the canonical URL or a 404 passes, a second 200 is a duplicate
  • Only status lines and headers are used; page bodies are not downloaded to your browser
A clean setup when https://www.example.com is canonical
You typeShould getHops
http://example.com/301 → https://www.example.com/1
https://example.com/301 → https://www.example.com/1
http://www.example.com/301 → https://www.example.com/1
https://www.example.com/2000
Worked example

github.com: three good variants and one two-step chain

The sample on this page was fetched on 2026-11-17.

github.com variants
VariantPath takenResult
http://github.com/301 → https://github.com/One hop, good
https://github.com/200Canonical URL
http://www.github.com/301 → https://www.github.com/ → 301 → https://github.com/Two hops: https first, then www removed
https://www.github.com/301 → https://github.com/One hop, good

The two-step chain on http://www is common: the server upgrades to https on the same host, and a second rule removes www. It is harmless for a rarely typed variant, but on your main entry point fold both rules into one.

Common mistakes

Where host redirects go wrong

They usually come from rules added at different times in different places: DNS, CDN, server, CMS.

www without DNS

The www record was never created, so www.example.com fails before any redirect can run. Add a CNAME and redirect it.

302 from the hosting panel

Some panels and CMS settings use temporary redirects for “force https” or “add www”. Check the code, then switch to 301.

Rules in two layers

The CDN forces https and the server adds www, which gives two hops. Do both in the first layer that sees the request.

Canonical tags disagree

Redirects point to www but canonical tags, sitemaps or hreflang use the bare domain. Every signal should name the same host.

FAQ

HTTPS and www redirect questions

Still have a question?

Chat with the team behind TapCub — we usually reply within a few hours on business days.

Should I use www or non-www?

Either. Google treats them the same for ranking. Pick one, redirect the other three variants to it with a 301, and use that version everywhere: canonical tags, sitemap, internal links and Search Console.

How do I check if http redirects to https?

Enter your domain above. The two http rows show where they go; both should reach your https canonical URL in one 301 or 308.

Is it a problem if www.example.com does not exist?

Yes, people type it out of habit and some links use it. Without a DNS record they get an error page. Add a record and redirect it to the canonical URL.

Why does the checker show two hops for one variant?

Usually two rules run one after the other: one switches to https, the next adds or removes www. Merge them so the first response already points to the final URL. The exception is HSTS preload, which needs http://example.com to go to https://example.com first.

Does the trailing slash matter?

/page and /page/ are different URLs. If both answer 200 with the same content, you have duplicates. Redirect one to the other, or at least make the canonical tag consistent.

Should I use 301 or 308?

Both are permanent, and search engines treat them the same. 308 also keeps the request method, which matters for forms and APIs. For page redirects 301 is the common choice.

Changelog

Update history

New features, fixes and data refreshes for this tool, newest first.

  1. · v1.0

    LaunchedFirst release.

Data this tool relies on

  • Sample fetches (github.com, apple.com, wikipedia.org, example.com, bbc.com) — checked 2026-11-17, reviewed every 6 months (next review by 2027-05-17)

Missing something or found an error? Tell us — requests that come up often go into the next update. All tool updates

Next step

Write the redirect rules

Generate host and protocol redirects for Apache, Nginx, Cloudflare, Vercel or Netlify, then run this check again.

See your data clearly. Find your growth.

Every click, backed by data. Install one line of code and see your first numbers in a minute.

No credit card · Free plans for analytics and chat · Cookieless analytics