CheckWebsiteNow

Redirect problems

Redirect target could not be checked

The first address redirected, but the next destination failed during our check.

Quick answer

We followed at least one redirect. The next address then failed: its name was not found, it timed out or its secure connection failed. The result shows where the chain stopped.

When to wait: If the destination is temporarily down, try again in a few minutes.

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. Wait and reload Wait a few minutes, then reload the page once. Short problems often fix themselves.

If you run the website

  1. Check the destination directly Test the final address on its own: DNS, certificate and server response.
  2. Point to a working page If the destination was retired, update the redirect to a page that exists.

Likely causes

  • Sometimes The destination server is down or slow. (Website side)
  • Sometimes The destination name has no working DNS record. (Website side)
  • Sometimes The destination has a certificate problem. (Website side)

Is the website down? Check it now

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

Sources

Last reviewed: