CheckWebsiteNow

CheckWebsiteNow results

Result: The check was restricted

The server answered but refused or limited our check.

Quick answer

The website replied with 401, 403 or 429. That means it is online, but it wants a login, blocks this kind of request, or limits how often it is asked. Many websites block automated checks like ours while still working fine for people.

When to wait: If it is a rate limit, wait a few minutes. A login or block rule will not change by waiting.

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 before checking again If the reason is rate limiting, repeated checks can make the block last longer.

If you run the website

  1. Review your security rules Check firewall, bot protection and rate limit settings. Make sure real visitors are not blocked.
  2. Check access logs Look for refused requests in your logs to see which rule triggered.

Likely causes

  • Common A security or anti-bot rule blocks automated requests. (Website side)
  • Sometimes The page needs a login. (Website side)
  • Sometimes Too many requests reached the site in a short time (rate limiting). (Either side)

What to avoid

  • Do not disable your whole firewall to test this; adjust single rules and test again.

Is the website down? Check it now

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

Sources

Last reviewed: