Where does it fail?
Pick the closest match for a useful next step.
Down checkWebMCP & AI-agent checkOne click, two answers, free steps to fix both.
ERROR MESSAGE LOOKUP
One check from one location — not a worldwide verdict. What this covers
HOW TO FIX IT
We count only yes and no for this kind of result: no IP address, no domain, no text. Privacy
This readable summary includes the result, its limits and your next step.
This check reads response headers, not logins or checkout. We follow up to five safe HTTPS redirects within the check’s time limit. Some sites still restrict automated requests.
Understand every measurementFOR PEOPLE AND AI AGENTS
Every Check Website runs two checks at the same time. First: does the website respond for people? Second: how well is it prepared for AI agents such as ChatGPT, Claude or Perplexity, judged from its public files? The second answer is a speedometer from 0 to 100, with every fix that raises it. This works for your site, any other public site, and ours.
How the score worksOur own transparent score, not an official standard. It checks bot rules, readable text, structure and agent helpers, and shows what each lost point would take to fix.
How AI assistants call tools on servers. Think of one plug that fits many assistants. We look for a published MCP server and API catalog. Advertised, not tested: we never call it.
A new browser standard that lets a website offer its own functions, such as a search form, as tools to AI agents in the page. Experimental; we read the declarations, we do not run them.
IS IT DOWN?
Each page runs a live check from our measurement point and lists common problems with fixes. Official status pages are linked only when we verified them.
All servicesERROR FIXES
ERR_CONNECTION_REFUSEDThe site refused to connect→DNS_PROBE_FINISHED_NXDOMAINThe domain name has no address→ERR_SSL_PROTOCOL_ERRORThe secure connection failed→ERR_NAME_NOT_RESOLVEDThe address could not be found→522Cloudflare timed out reaching the site→503Service unavailable→502Bad gateway between servers→403Access forbidden→429Too many requests→404Page not found→WEBSITE NOT LOADING?
Pick the closest match for a useful next step.
For when your browser gives you a number instead of an answer.
QUESTIONS
Type the website address, for example example.com, into the box at the top and press Check website. We contact the site over HTTPS from one measurement point and tell you in plain words whether it answered. If your browser shows an error code instead, paste that code into the same box. Then follow the free steps for visitors or for site owners.
We cannot answer that for the whole world, because we test from one measurement point, not from all over the world. If our check reaches the site but you cannot, the cause is more likely on your side: try mobile data instead of Wi-Fi, a private window or another device. If our check fails too, the site may have a problem, but only as seen from our location. Some sites also block automated checks, which shows as Restricted or Unclear. What a result covers.
It means the tested response answered successfully from one location. Sign-in, checkout and other countries may behave differently. If it still fails for you, compare a private window and another connection.
Yes. Paste the code or sentence, for example ERR_CONNECTION_REFUSED or “HTTP Error 503”. We match it against our error library and show what it means, with steps for visitors and for site owners.
We follow up to five safe HTTPS redirects within the overall time limit. The result describes the last destination we tested. A loop, private address or unsafe link stops the check with an explanation.
No. The quick check includes finding the address, connecting and reading response headers. It does not inspect page contents. The agent-readability check that runs alongside reads a few bounded public files: the homepage, robots.txt, llms.txt, discovery files, the sitemap and a Markdown version. See what the comparison means.
It shows how easily AI agents can read the website, from 0 to 100: our own transparent CheckWebsiteNow Agent Readability Score, not an official standard. It also says whether we found an MCP server announcement (advertised, not tested) and WebMCP declarations (declared, not verified in a browser). Under “How to raise your score” you find every fix, biggest first. Full method.
That is a regional block (geoblocking). Try the free steps first: the official version for your country, your EU travel rights for paid subscriptions, or asking the website. A VPN can help, but it may break the service’s terms. How to tell a country block from an outage. Free solutions and a VPN comparison on documented facts.
A login, protection rule or request limit can block automated checks. Yellow means that more evidence is needed. Try the website in your own browser before calling it an outage.
No. The five recent domains stay only in this page’s memory. Clear or reload to remove them. Optional usage measurement records step names, never the domain you entered. Read the privacy details.
One location. One observation. No invented outage percentage.
Free troubleshooting for visitors and owners. Partner offers are labelled; no purchase is needed to check a website.
The same results through our HTTP API, MCP and browser-agent tools.