Is the website responding?

Check a public website or API from the NetOkay Worker. See the HTTP status and response time, then compare with your own device.

Worker → website. This checks a response from the Worker, not from your device or application. The URL is sent to NetOkay only when you start a check.

Check from my device Terminal or Agent

The Worker may reach a service that your app cannot. Run the CLI in the environment where the problem occurs. Generating or copying a command does not run a diagnosis.

Target URL Example: https://example.com HTTP/HTTPS · ports 80/443

Syntax is checked here; the CLI will fail closed for private or sensitive targets.

Run mode Terminal Agent

npm exec --yes
                  --package=https://github.com/flreey/netokay-cli/releases/download/v0.3.0/netokay-0.3.0.tgz
                  -- netokay diagnose 'https://example.com/'

Target URL accepted. Copy ready.

Run the check

Use the environment that needs to connect

Enter the full HTTP or HTTPS URL, including its path. This command supports public HTTP on port 80 and HTTPS on port 443. Leave out credentials, query strings, and fragments.
Copy the command into the terminal where the problem occurs. It uses the GitHub v0.3.0 prerelease package and requires Node 24 and npm. Review the command before running it.
Read the terminal result. The CLI applies the final target policy and performs the diagnosis. A generated or copied command has not yet tested anything.

What does this result mean?

A 2xx response means this HTTP request succeeded. A 3xx response may point to another location, which is not followed. A 4xx or 5xx response means a server replied with an error; it does not mean the network connection failed. A timeout or unavailable result does not identify a unique cause.

If your app still fails, check the same URL from its environment using the terminal option above. Compare proxy, DNS, certificates and authentication settings, then retry the original operation. Neither the Worker nor a separate CLI process verifies the application’s internal client.

Read Evidence Compare browser and terminal Application still fails?

Try these free steps first

Check the exact URL and port, retry in the failing environment, and compare that environment’s network, proxy, and certificate settings. Use the application’s own logs to investigate what the CLI could not observe.

Starting a web check sends the URL to the NetOkay Worker and its hostname to Cloudflare DNS. The target receives a request from the Worker. NetOkay application code does not store the URL or result, or send them to analytics or partners. Page memory is cleared when you leave or reload; copying a command writes it to your clipboard.