How accessible is your website?Start free check
Documentation

When a check fails

See where allyWay tells you that a check failed, what each reason means, how to fix the cause and check again – your earlier results stay.

Updated October 27, 2026

When our check can't read your website, allyWay tells you why. This page explains each reason and how to get your website checked again.

Where you see it

  • Report: the reason shows under the numbers at the top. If an earlier check worked, it adds "The results below are from your last successful check." – those results stay.
  • History tab: the check says Didn’t work, with the same reason.
  • Overview: "The last check didn’t finish" with Check again.
  • Free trial: the card on the Report says "We couldn’t check shop.com", with the reason and Try again.
  • A check of one page: if it fails after a good website check, you only see a note under the Report's numbers, like "Your check of /contact didn’t work: …" – your website's results stay.

Our scanner only gives up when your homepage can't be checked – or, for a check of one page, that page. Other pages that fail are simply skipped.

Get your website checked again

  1. Read the reason

    It's under the Report's numbers. Each one is explained below.

  2. Fix the cause

    Fix it on your website, or ask your hosting provider or web designer.

  3. Start the check again

    Click Check now on the Report or Check again on the Overview – during the free trial, Try again on the card. See Run a check.

What the reasons mean

"The website couldn’t be reached"

Our scanner couldn't connect: the address doesn't exist or doesn't point to a server yet, the server refused the connection, or the website was offline. Open exactly the address shown in the Report in a browser. If it doesn't open, check that your domain hasn't expired and that its DNS settings (the internet's address book) point to your hosting – changes can take a few hours. If it opens for you but not for us, your firewall or hosting may block unknown visitors or other countries – see Allow our checker in your firewall.

A website on your own computer, in a company network or behind a VPN can't be checked.

"The website took too long to load"

Your homepage didn't load in time: each page has 30 seconds, and every check has an overall time limit. See whether your website loads slowly or hangs, then try again in a few minutes or at a quieter time. If it keeps happening, ask your hosting provider or web designer about its loading speed.

"The website responded with an error"

Your server answered with an error code instead of the page. The number in brackets tells which: 404 or 410 – the page doesn't exist; 401 – a login or password is needed; 403 – access forbidden; 429 – too many requests; 500 – server error; 503 – maintenance or overload. Open exactly that address in a private browser window and look for a maintenance or "coming soon" mode, a password prompt, or a page that was moved or deleted. A homepage that isn't a web page at all, like a file download, ends with this message too.

"Your website’s security settings blocked our scanner"

A firewall or bot protection stopped our scanner. Allow our scanner there – click How to allow our scanner under the message, or see Allow our checker in your firewall.

"The website’s security certificate isn’t valid"

Your HTTPS certificate – what gives your address the padlock – is expired, invalid or doesn't match the address, so browsers warn your visitors too. Renew or fix it, usually in your hosting control panel, and make sure it covers the address with and without "www.".

"Your website sends visitors to another address"

Your homepage forwards to a different website – for example from shop.at to shop.de. We only check the website you added. If the other address is your real website, add it as a new website – see Add a website. If the forwarding is a mistake, fix it. Forwarding between the address with and without "www.", or from http to https, is fine.

Reasons that aren't caused by your website

  • "Our scanner wasn’t available, so this check couldn’t run …" A problem on our side. Start the check again in a few minutes.
  • "Your plan wasn’t active when this check was due, so it didn’t run." Once your plan is active, start it again or wait for the next automatic check. See Why your account is locked.
  • "This website was paused when the check was due, so it didn’t run." Make it one of your active websites again, then check it. See Paused websites.
  • "Something went wrong during the check. Please try again." An unexpected error stopped the check – for example, our scanner stopped several times. Try again in a few minutes.

Failed checks and your limits

A failed check doesn't count toward your monthly checks. You can start up to 10 checks a day that fail or that you cancel – then you see "Too many failed checks today. Please try again tomorrow." Checks that couldn't run because our scanner wasn't available, your plan wasn't active or the website was paused don't count here.

Check that it works

Once a check finishes, the reason under the Report's numbers is gone, and History lists the check with its score. If a check keeps failing and you don't know why, contact our support with your website address and the time of the check – see Get help from our team.

Still stuck?

Our support team replies within a few hours.

Contact support

Installation helper

Step-by-step setup guides for your platform.

Open the helper