Privacy boundary
Observe only what the contract needs.
Browser connection checks use NetOkay’s fixed HTTPS self/stream and WSS endpoints. The separate website check sends a public URL to the NetOkay Worker when you press Check website. Neither feature inspects an Agent runtime or uploads CLI Evidence.
Returned to the self caller
The Control self response may include the complete client IP from Cloudflare's
CF-Connecting-IP header, plus allowlisted protocol and edge fields. It is
returned only to the caller of that request and is not written into CLI Evidence facts.
Deliberately omitted
NetOkay Worker application code does not write client_ip into Evidence facts.
Platform-level logging and retention are outside this application contract and are not
asserted here. Missing fields remain Not obtained.
Pasted comparison data
The environment comparison accepts only the self API response, up to 16 KiB. This is user-provided data whose origin is not independently verified. Pasted content is processed only in the current page’s memory: no upload, browser persistence, or URL encoding. Leaving or refreshing clears it. The full public IP is visible in this page; the CLI’s default IP redaction and Evidence schema are unchanged.
Local connection reports
Report previews stay in the current page memory. Previewing does not upload data. Copy and Download JSON export the same redacted report, omitting full IP addresses, user target URLs, pasted terminal responses, credentials and free-form errors. Leaving or refreshing clears the report. Files you download and text you copy remain under your control. Report analytics contain only the page category, operation and operation status.
IP snapshots and target commands
Before-and-after IP snapshots stay only in the current page’s memory. Leaving, reloading, or returning from page cache clears them. A failed refresh keeps the before snapshot but does not reuse an old successful after result.
Target URLs and generated commands stay in page memory until you leave or reload. Generating a terminal command makes no target request. Copying a value writes it to your clipboard; you control where you use it.
Website checks
Starting a website check sends the URL in a same-origin POST to NetOkay. The Worker sends
the hostname to Cloudflare’s DNS resolver, then makes bounded, read-only requests to the
admitted public target. The target sees requests from the Worker, identified as
NetOkay-Website-Check/2.0 (+https://netokay.net/about/), not a test from your
application. Credentials, query strings, fragments, private destinations and custom ports
are not accepted. The Worker does not forward your cookies or authorization headers.
Only the basic response check runs automatically. Every other check runs when you press its button or “Run all checks”: robots.txt, sitemap and security.txt; all response headers, cookie names and attributes (values are never read), HSTS and firewall fingerprints; MX, SPF, DMARC, DKIM and BIMI records (report mailboxes are redacted); DNSSEC; technology fingerprints from headers and markup. No check opens a connection to the target other than HTTP requests.
The DNS lookup page uses the same POST with only the domain name. The Worker asks Cloudflare’s DNS resolver for its A, AAAA, NS, MX, TXT and CAA records and sends no request to the site itself; answers that point to private or reserved addresses are withheld. The domain is not added to the page URL.
The MX lookup works the same way: the Worker asks the same resolver for the domain’s MX records and the addresses of up to ten mail servers, and opens no connection to them. If you type an email address, only the domain after the @ leaves your browser.
Several checks quote public third-party sources about the target: Tranco, PhishTank and crt.sh. Those services receive the target hostname or URL from the Worker, never your address. Their results are shown as quoted, not verified.
Check only sites you own or are authorised to test. Site owners who do not want NetOkay to check their host can ask for it to be excluded from the contact on the About page; excluded hosts return “owner opt-out” without any request being sent.
NetOkay application code does not persist or log target URLs, results or the requester. Completed results are cached on the Cloudflare edge for up to 10 minutes, keyed by the target URL and check name only, so a shared link or a repeat check does not hit the target again. Platform and destination logging are outside this application contract. Short-lived, approximate rate limits use a hash of the connecting IP, a hash of the target hostname and a shared counter per Cloudflare location; users on one network can share a limit. A local preview runs on the local machine and is labeled separately from Cloudflare production. No target data is sent to analytics or partners. Displayed values stay in page memory; exported reports omit IPs, domains, URLs, DNS values, header values, cookie names and page metadata values. The optional “Copy link” button copies a page URL that contains only the URL you entered.
AI API status pages
Each page under /api-status/ asks the NetOkay Worker, when the page loads, for
its most recent observation of one fixed provider API URL from NetOkay’s own catalog.
Nothing you type is involved and no URL leaves your browser. The Worker contacts the
provider host at most once per minute per Cloudflare location, caches that single result for
60 seconds keyed by the provider name only, and keeps no history. The probe carries a fixed
placeholder token in the provider’s authentication header so that the provider’s API, not
only its edge, produces the answer. The token is public, belongs to no account and is not a
credential; NetOkay holds no provider accounts or keys. Only the HTTP status, timing, the
media type family and a fixed classification of the body (JSON error, JSON, edge block,
empty, other) are kept; no response text is stored or shown. Provider hosts see the same
identified Worker requests as the website check and can opt out the same way.
The “Test from this browser” button sends one request from your browser to the same fixed provider URL, only when you click it, with no credentials and no cookies. The provider then sees your browser exactly as it sees your own application; NetOkay sees nothing of that request. The result shown is limited to reachable, failed or timed out and a duration.
Partner recommendations
Partner recommendations are currently disabled and have no configured affiliate links. No partner card or tracking script is loaded. If enabled in the future, recommendations will disclose commissions next to the link. Links will suppress the referrer and will not include IPs, targets, or pasted results. The partner’s own privacy terms apply after you follow its link.
Website analytics
Local previews do not load Google scripts or send analytics events. Check events
connection_check_start and connection_check_end, and
environment_compare_complete, contain only fixed check categories and statuses.
They do not include IP addresses, targets, or pasted content.
Website events website_check_start and website_check_end, and the
provider probe events reachability_end and
provider_browser_probe_end, contain only fixed states. HTTP codes, timing,
hostnames, paths and result content are omitted.
Scenario events self_lookup_complete, ip_compare_complete,
guide_tool_click, and partner_link_click accept only fixed
statuses, guide/tool IDs, and partner/placement IDs. Disabled recommendations produce no
partner clicks. A command copy is not a completed diagnosis, and a partner click is not a
purchase.
Pages on the production netokay.net HTTPS host load Google Analytics 4 using measurement ID
G-SHBSZQDHH0. The standard Google tag may collect page and session statistics,
approximate geolocation, and browser or device information. Its default implementation may
store a first-party _ga client identifier.
NetOkay also records four named interaction events:
provider_ticket_audit_click, provider_scope_click,
diagnose_command_copy, and agent_install_copy. These interactions
contain only the event name, without the target URL, generated command, EvidenceBundle,
email content, or customer data. Copy events are sent only after the copy succeeds.
Analytics data is sent directly from the browser to Google. NetOkay has no server-side analytics binding and does not receive those Google Analytics payloads. Google Analytics does not enter CLI Evidence, and NetOkay application code does not send the target entered in the command builder, generated command, EvidenceBundle, proxy values, or Control self response to Google Analytics.
Browser privacy controls, content blockers, or cookie settings may limit analytics. For Google's handling of analytics data, read the Google Privacy Policy.