How to Check That http Redirects to https on Many Websites at Once

Typing http:// in front of a domain should end up on HTTPS, and a list of domains can be tested for exactly that. The check requests each plain http address, follows the redirects and reads where it ends. The bulk HTTP to HTTPS redirect checker does this for up to 100 domains at once (500 after a free Google sign-in). Each row says Redirects to HTTPS with the status code, Stays on HTTP, or HTTPS only, and lists the hops.

A good result is a permanent redirect (301 or 308) in one or two hops.

Why the status code matters

A permanent status tells clients the move is lasting. A temporary one such as 302 or 307 says it may be undone, so it is flagged. The codes are defined in RFC 9110. Stays on HTTP means the plain address answered without moving to HTTPS.

The by-hand way

1. Run curl -sIL http://example.com and read each HTTP/ line and location header.
2. Note the first status code and the final address.
3. Repeat per domain.

Step 1: paste the domains

One per line, or a CSV.

Step 2: run it

Each http address is requested once and its redirects followed, five at a time.

Step 3: filter and download

Read where each address ends, the first status and the hops. Filter to the flagged rows and download the CSV. To see a whole redirect chain, use the bulk redirect checker; for the www side, see checking www and non-www redirects.

What this check cannot do

• Only the root address of each domain is requested.
• Up to five redirects are followed.
• Certificates and HSTS aren't checked; those have the bulk SSL checker and the bulk HSTS checker.

Next: contact emails

For emails on the same list, verify them: the first 100 checks are free with a Google sign-in.

Try it now

Paste your domains into the bulk HTTP to HTTPS redirect checker.