Is Site Down? Website Status Checker
Check whether a public website is responding from the ORVITech server and view its HTTP status code when one is returned.
Use this free website status checker to test whether a public website responds to a request from the ORVITech server. The result indicates whether the site appears reachable and displays its HTTP status code when the server returns one.
What Does “Site Is Up” Mean?
A site is reported as up when its server returns an HTTP response below 500. This means the website responded to the check, but it does not guarantee that a particular page contains the expected content or that every feature is working correctly.
How HTTP Responses Are Interpreted
Successful responses, redirects, and client-facing responses such as 401, 403, 404, and 429 indicate that a web server was reached. Responses from 500 through 599 indicate that the server responded with an error and the site appears unavailable or unhealthy. A DNS, connection, TLS, or timeout failure produces a down result without an HTTP status code.
Redirects Are Reported but Not Followed
For security, the checker does not follow redirects. If the requested URL returns a redirect such as 301, 302, 307, or 308, that redirect response is reported as evidence that the website is responding. The destination URL is not checked automatically.
The Check Comes From the ORVITech Server
The URL is sent to ORVITech, and the website request is made from the ORVITech server rather than from your browser or local internet connection. The target website may therefore respond differently based on the server’s location, IP address, network, or automated-request rules.
Why a Website May Work for You but Fail the Check
A website may block automated requests, restrict specific networks or locations, require authentication, experience temporary routing problems, or take longer than the checker’s 10-second timeout. A failed check does not prove that the website is unavailable to every visitor.
Why a Website May Appear Up but Not Work for You
The ORVITech server may be able to reach a website that is blocked by your network, affected by a regional outage, unavailable through your DNS provider, or experiencing a problem specific to your browser or device.
Public Website Checks Only
The checker accepts public HTTP and HTTPS websites using standard web ports. Localhost, private networks, internal addresses, link-local destinations, reserved address ranges, embedded URL credentials, and custom ports are blocked for security.
How to Check Whether a Website Is Down
Enter a domain such as example.com or a complete HTTP or HTTPS URL and select Check Website. The tool will wait up to 10 seconds for a response and report whether the site appears to be up or down from the ORVITech server.
Website Status Check Example
Enter example.com and select Check Website. The utility checks https://example.com. If the server returns HTTP 200, the result reports that the site is up and displays status code 200. If the connection times out or cannot be established, the site appears down from the checker’s location.
Frequently Asked Questions
How can I check if a website is down?
Enter its public website address and select Check Website. ORVITech will request the URL from its server and report whether it receives a response.
Does “site is up” mean the page is working correctly?
Not necessarily. It means the web server returned an HTTP response below 500. A page can still be missing, restricted, rate-limited, or otherwise unusable.
Why is HTTP 404 considered up?
A 404 response means the website server was reached and responded, although the requested page was not found. The site is reachable even though that particular URL does not exist.
Why is HTTP 403 considered up?
A 403 response means the server was reached but refused access to the request. The website is responding, although it may be blocking the checker or restricting that page.
What do HTTP 500, 502, 503, and 504 mean?
They are server-error responses. The checker reports the site as appearing down or unhealthy because the server could not successfully handle the request.
Does the checker follow website redirects?
No. It reports the redirect status code without visiting the destination. This prevents the checker from being redirected toward private or unsafe network addresses.
How long does a website check wait?
The server allows up to 10 seconds for the request. If no usable response is received within that period, the site appears down from the checker’s location.
Does a failed check prove that the website is down for everyone?
No. The result reflects one request from the ORVITech server. Location, routing, security rules, rate limits, authentication, and temporary network conditions can produce different results for different visitors.
Do I need to include https://?
No. If you enter a domain such as example.com, the utility automatically checks it using HTTPS. To test HTTP explicitly, include http:// in the address.
Can I check a website running on a custom port?
No. The utility accepts standard HTTP and HTTPS ports only. Custom ports are blocked to prevent the checker from being used as a general-purpose port scanner.
Can I check localhost or a private network address?
No. Local, private, link-local, reserved, documentation, and other non-public IP ranges are blocked for security.
Why might I be temporarily prevented from running more checks?
To prevent automated abuse, each IP address can perform up to 20 website checks within a 15-minute period. Additional requests must wait until the limit resets.
Does the check come from my own internet connection?
No. ORVITech performs the website request from its server, so the result may differ from what you experience through your own network or location.
Is the website status checker free?
Yes. The checker is free to use and does not require creating an account.