Check Whether the HTTPS Redirect Is Configured

Confirm in minutes that every HTTP address leads directly to the correct HTTPS version of the website.

Order
the fix

Do it
yourself

Check
manually

Manual verification methods

For those who want to see for themselves

Methodology: This check follows wSEO methodology 1.1. How the assessment works

Independent manual verification

Confirm that HTTP redirects to HTTPS correctly

Check the first server response, not only the final page displayed by the browser. The correct result is one permanent 301 or 308 hop to the same page over HTTPS.

one hop instead of a chain;
the same path and query string;
the correct primary hostname.

Verifying an HTTP redirect with a browser, online checker and terminal — Three independent methods should confirm the same secure final address.

How to read the result

Codes and situations you may see during the check
Result	Assessment	Meaning
`301` or `308`	Correct	A permanent redirect to the corresponding HTTPS URL.
`302`, `303` or `307`	Review	A temporary redirect instead of a permanent one.
`200` over HTTP	Error	The insecure copy is still directly accessible.
`404/500`, loop or another domain	Error	The redirect is broken or leads to the wrong destination.

Quick browser check

Enter a full URL such as http://example.com/catalog?item=1.
It should become https://example.com/catalog?item=1.
Confirm that the path and parameters after ? remain intact.
Repeat for the home page and two or three internal pages.

Test all four domain variants

HTTP without WWW

http://example.com/

HTTP with WWW

http://www.example.com/

Both HTTPS variants

https://example.com/
https://www.example.com/

The primary HTTPS URL should return 200. Every existing additional variant should lead directly to it, without a separate intermediate hop between WWW and non-WWW.

Online checker

Open httpstatus.io.
Enter the full HTTP URL of an internal page.
Run the test and expand the chain.
The first response is 301/308 and the final address is the correct HTTPS URL.

Terminal

First response and Location header:

curl -I "http://example.com/catalog?item=1"

Complete chain and final URL:

curl -IL "http://example.com/catalog?item=1"
curl -Ls -o /dev/null -w "%{http_code} %{url_effective}\n" \
"http://example.com/catalog?item=1"

Expected first response

HTTP/1.1 301 Moved Permanently
Location: https://example.com/catalog?item=1

If your result differs, save the checker link or a screenshot. It will help the person doing the work confirm and repair the issue faster.

How to fix it Order the configuration

Sources and documentation

MDN — Redirections in HTTP (link checked 2026-07-22) Supports: Official definition, expected result and limitations of the described diagnostic method.
IETF — RFC 9110 — HTTP Semantics (link checked 2026-07-22) Supports: Official definition, expected result and limitations of the described diagnostic method.

An Automatic check is available at the top of this page. You can independently confirm its result using the manual verification instructions, then fix the issue yourself or order a professional fix.