Security Tools

HTTPS Redirect Checker

Check whether a website properly redirects visitors to HTTPS.

Enter a domain to check whether it redirects visitors to HTTPS.

More Security Tools

Security Headers Checker HSTS Checker Mixed Content Detector Content Security Policy (CSP) Checker CORS Header Checker X-Frame-Options Checker Permissions-Policy Checker X-Content-Type-Options Checker

JustChecker monitors your SSL/HTTPS configuration continuously.

What Is the HTTPS Redirect Checker?

It requests the plain http:// version of a website and checks whether it is redirected to https://. Without that redirect, visitors who type the address or follow old links may browse without encryption.

When to Use It

After installing an SSL certificate.
When Google Search Console shows both http and https versions of pages.

How to Use It

Enter the domain.
Check that HTTP ends on an HTTPS URL, ideally with a single 301.

Understanding the Result

A 301 or 308 redirect to HTTPS is correct. A 302 works but is treated as temporary. If HTTP is served without a redirect, add one at the web server or CDN.

Limitations

After the redirect works, add HSTS so browsers stop trying HTTP at all - check it with the HSTS Checker. See every hop with the Redirect Checker.

Frequently Asked Questions

Without a forced redirect, visitors who type or click a plain http link connect over an unencrypted channel by default, exposing their traffic to interception - a proper redirect ensures every visitor ends up on the secure version regardless of how they arrived.

This tool checks whether the redirect actually happens on each request; HSTS is a header that tells the BROWSER to enforce https automatically on future visits without even needing a redirect round-trip - they work together, not as alternatives.

A browser can silently upgrade a request in ways that mask a missing server-side redirect (cached HSTS state, browser extensions) - this tool tests the raw server response directly, revealing whether the redirect is genuinely configured server-side.

A 301 (permanent) is the standard, recommended choice for an http-to-https redirect, since this is intended to be a permanent characteristic of the site, not a temporary condition.

No - a single, well-configured server-level rule redirecting the entire domain (any path) from http to https covers every page automatically, without needing page-by-page configuration.

Yes, many CDNs and reverse proxies offer a built-in "always use HTTPS" setting that handles this redirect at the edge, which is a common and effective approach.