Frequently Asked Questions

It checks if a website responds from our side. If we get a valid response, we mark it as up. If the request fails or times out, we mark it as down.

It means the server answered our request. The site is reachable, but some pages or features could still have issues.

It means we couldn't get a normal response. The server may be offline, overloaded, timed out, or returning errors.

That usually points to a local issue on your side. Common causes include:

• Old DNS cache
• ISP or local network filtering
• Firewall, antivirus, or VPN routing issues
• Regional blocking by the website

Sometimes sites block datacenter requests or limit traffic. It can also be a temporary routing issue between our server and the target website.

These are server response codes that explain what happened:

• 200 - Request succeeded
• 301/302 - Redirect to another URL
• 403 - Access denied
• 404 - Page not found
• 500 - Server-side error
• 502/503 - Gateway or temporary service issue

It is how long the server takes to answer, measured in milliseconds (ms). Lower is better. High response time can mean server load or network delay.

For safety and abuse prevention, we block some domain types and private/internal addresses like localhost.

You can check as often as you need. Recent checks may use short-term cache to reduce load and speed up results.

Yes. Country checks can help you see whether an issue is global or limited to certain regions.