No document uploads
These are network diagnostics, not file tools. Nothing here uploads PDFs or local files.
Use this hub to reach the network checks that sit alongside the PDF catalogue: public IP lookup, DNS-over-HTTPS inspection, browser-side status checks, and WebSocket latency measurement. These tools do not upload documents or require an account, but they do contact the target endpoint or public API needed for the check.
Start here when you need quick diagnostics before escalating: verify resolver output, confirm what public IP is exposed, test whether a URL answers a HEAD request, or compare WebSocket latency across public echo endpoints.
This category page is designed as the main network entry point for Plain Tools. Use it when the job is operational rather than document-based: checking whether a website is reachable, confirming resolver output, measuring simple latency, or verifying what public IP is visible from your current connection. Unlike the PDF workflows, these tools do make direct requests to the endpoint or public API needed for the result, but they still avoid unnecessary account friction and keep the workflow lightweight. The aim is to help you move from a quick symptom such as “site not loading” or “Discord feels down” to a clearer diagnosis without jumping between unrelated pages.
Each card opens a dedicated tool page with the live checker, a static explanation of what the result means, and links to the next network step if the first check does not answer the problem.
View your public IP and browser-reported connection context with a direct public endpoint request.
Query Cloudflare DNS-over-HTTPS for A, AAAA, and MX records without a Plain Tools proxy.
Run a direct browser HEAD check and review status code plus response timing.
Measure WebSocket connect and echo timing through public echo endpoints from your browser.
example.com, a full URL for HEAD checks, or a WebSocket endpoint for latency tests.These are network diagnostics, not file tools. Nothing here uploads PDFs or local files.
Checks run from your browser against the public IP, DNS, HTTP, or WebSocket endpoint required for the result.
Browser CORS rules and endpoint policies can block some checks. When that happens, the tool reports the limitation instead of inventing a result.
Work through the difference between a global outage and a local connectivity problem.
Understand what a resolver check tells you before you blame the target service.
Interpret slow responses versus hard failures when reading status output.
Use browser tooling to inspect what a page or checker is sending over the network.