HTTP/HTTPS Look Up
Related tools
What this is
This check connects to your site over both HTTPS and plain HTTP, verifying that HTTPS answers and that HTTP redirects visitors to the secure site rather than serving content (or nothing) in the clear.
How to read your result
Healthy: HTTPS responds (2xx/3xx) and HTTP answers with a 301 redirect to the https:// URL. HTTP timing out entirely is acceptable but loses visitors who type the bare address.
Common problems and how to fix them
HTTP serves the site without redirecting
How it shows up: Visitors who type the domain or follow old http:// links browse unencrypted; search engines may index both variants.
How to fix it: Add a permanent (301) redirect from http:// to https:// at the server or CDN — a one-line change in most configurations — and pair it with HSTS.
HTTPS not responding
How it shows up: The site is effectively down for modern users and browsers.
How to fix it: Check certificate validity, that the server listens on 443, and that firewalls/security groups permit it. If the certificate expired, renew it and fix the automation that should have renewed it.
Redirect loop or redirect to the wrong host
How it shows up: Browsers show "too many redirects", or visitors end up on an unexpected domain.
How to fix it: A common cause is a CDN and origin both redirecting each other (e.g. flexible-SSL setups). Set the origin to accept HTTPS from the CDN, and make each layer redirect only http→https, never the reverse.
Related reading
- llms.txt: Writing the File AI Crawlers Read First, and Checking YoursWhat to put in an llms.txt file, how it differs from robots.txt and sitemap.xml, the habits worth keeping, and exactly what the ServerRecords check confirms.
- HSTS: Closing the One HTTP Connection That Can Still Get You StrippedEven with HTTPS and a redirect, the first plain HTTP request is a weak spot. Here is how HSTS closes it, what each directive does, and how to check yours.
- What a Domain Health Check Actually Tells YouOne scan covers registration, DNS, HTTPS redirects and security headers. Learn what a domain health check surfaces and why each result matters.
Frequently asked questions
- What does the HTTP/HTTPS Check tool do?
- It checks whether your site redirects insecure HTTP requests to HTTPS and confirms that HTTPS is reachable. This tells you if visitors are automatically sent to the encrypted version of your website.
- How do I use this tool?
- Enter your domain or URL and run the check; our server requests the site over both HTTP and HTTPS and reports the redirect behavior and HTTPS availability. All requests run server-side and nothing you enter is stored.
- Why does HTTP-to-HTTPS redirection matter?
- Without a redirect, visitors who type your address without "https://" may land on an unencrypted page, exposing their data and hurting SEO and browser trust. A proper redirect ensures everyone reaches the secure version automatically.
- How do I fix a site that doesn't redirect to HTTPS?
- Configure your web server or hosting panel to send a 301 redirect from HTTP to HTTPS, and make sure a valid TLS certificate is installed. After the change, re-run the check to confirm the redirect and HTTPS both respond correctly.
- What are the limits of this check?
- It verifies redirection and basic HTTPS reachability, not the full validity or expiry of your TLS certificate or the strength of your cipher suites. Use a dedicated SSL/TLS inspection tool for a deeper certificate audit.