CheckWebsiteNow

Redirect problems

Redirect to an insecure or unsupported address

The website tried to send us to an address that is not secure HTTPS, so we stopped.

Quick answer

We only follow redirects to standard HTTPS addresses. This redirect pointed to plain HTTP or another kind of link. Plain HTTP is not encrypted, so others on the network could read or change the traffic.

When to wait: Waiting will not fix this; the redirect has to be changed.

If you are visiting the website

  1. Compare in your own browser Open the website yourself. Our check comes from one measuring point and may see something different from you.
  2. Watch the address bar If your browser ends up on an http:// address, do not enter passwords or payment details there.

If you run the website

  1. Use HTTPS everywhere Update redirect rules so every step points to an https:// address.
  2. Get a free certificate if needed If HTTPS is missing, many hosts set it up for you, or you can use a free certificate from a provider such as Let's Encrypt.

Likely causes

  • Common A redirect rule still points to an old http:// address. (Website side)
  • Rare The site redirects to another protocol or an unusual address format. (Website side)

What to avoid

  • Do not enter passwords or payment details on a page reached over plain http://.

Is the website down? Check it now

One measurement point. Results explain what we saw, not a worldwide verdict.

Sources

Last reviewed: