CheckWebsiteNow

Redirect problems

Redirect destination could not be read safely

The redirect destination was malformed, so we did not follow it.

Quick answer

The next address was broken, ambiguous or listed more than once. Examples are spaces, odd characters, embedded login details or an unusual port. We stop rather than guess where the redirect should go.

When to wait: Waiting will not fix a malformed redirect.

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. Do not paste odd addresses If the site sends you to a strange-looking address, do not copy it into your browser.

If you run the website

  1. Correct the redirect address Use one clean, absolute https:// address per redirect.
  2. Remove duplicate rules Check that only one layer (server, app or CDN) adds the redirect.

Likely causes

  • Common A typo or unencoded characters in the redirect rule. (Website side)
  • Sometimes Several conflicting Location headers from different layers. (Website side)

Is the website down? Check it now

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

Sources

Last reviewed: