HTTPS & certificate details
A successful HTTPS response indicates a TLS connection completed. It does not establish trust. The Worker cannot expose certificate expiry or chain fields; use your browser’s certificate viewer for manual review.
Review links, inspect public DNS, assess website signals, and run authorized network diagnostics in one focused workspace.
Enter a URL to start an on-page inspection.
URL structure, HTTPS use, risky formatting hints, and public DNS. This is a signal review—not a malware verdict.
Latest URL analyses stored in this browser.
Detailed URL inspection and DNS checks.
Use the Quick analysis form on Overview to inspect a link. Results include URL parsing, HTTPS status, user-info and encoding hints, known shortener domains, and public DNS records.
Query public DNS-over-HTTPS for common record types.
DNS queries are sent to Cloudflare's public DNS-over-HTTPS endpoint. The DNS provider can see the hostname you query.
Stored locally in this browser profile.
See your connected Wi-Fi, nearby access points, and devices observed on your authorized local network.
A Fing-inspired scan workflow built around facts your Windows laptop can observe. It reads the current connection, lists nearby access points, checks selected TCP ports on your private subnet, and adds MAC addresses from the Windows ARP cache when available.
Ready. A scan runs only when you start it.
Networks visible to this Windows adapter.
Only devices seen in the local ARP cache or accepting one of the selected TCP ports appear.
GitHub Pages cannot inspect local Wi-Fi. The authenticated local Windows API is required. MAC addresses come from the local ARP table and may be absent or cached; NetScope does not guess vendor, model, operating system, or device name. A device that does not appear may still be connected if it blocks these checks.
Unauthenticated HTTPS, redirects, security headers, and cookie-flag checks for an explicitly authorized allowlisted host.
The Worker follows up to four redirects only while they stay on the exact authorized hostname. TLS certificate expiry and chain details are not exposed by this Worker runtime. Scores reflect these observed controls only, not overall security.
Saved locally in this browser. Adding a profile does not scan or authorize the host on the Worker.
How to interpret observed signals and choose a safe next step.
A successful HTTPS response indicates a TLS connection completed. It does not establish trust. The Worker cannot expose certificate expiry or chain fields; use your browser’s certificate viewer for manual review.
Missing CSP, HSTS, frame protection, or nosniff headers are configuration signals. Review the site’s needs and deploy changes in a test environment before production.
SPF lists permitted email senders; DMARC tells receivers how to handle mail that fails alignment. DNS answers vary by resolver and time. Missing records are not proof of compromise.
An open port only shows that a TCP handshake succeeded from the Worker’s network. It does not prove a vulnerability. Closed or filtered is inconclusive.
Use a host you own or a dedicated lab target, add it to the Worker’s exact allowlist, confirm written scope, then select only approved ports. Never test third-party systems.
A hosted browser cannot inspect Wi-Fi, capture packets, reliably traceroute, enumerate LAN devices, or expose raw TLS certificate chains. No results are simulated.
Bounded TCP checks for an explicitly authorized public target. No EXE or local installation.
Set your Cloudflare Worker URL once, then choose an approved target.
No scan has been run.
Saved only in this browser profile. History is not uploaded to the API.
What a website can—and cannot—check without a local agent or backend.
Available: query A, AAAA, MX, NS, TXT, CAA, and other public DNS record types for a hostname.
Available: parse URL, identify HTTP, punycode, user-info, unusual ports, IP literal, and known shortener domains.
Real Windows adapter details, nearby access points, and authorized private-LAN TCP discovery run through the authenticated local Python service—not GitHub Pages.
Start NetScope Pro locally first. Setup guide
Use the authorized LAN scanner in the authenticated local workspace.
TCP connect checks only · 350 ms timeout · max 32 connections · two scans per minute.
Open authenticated local Network ToolsLimited: cross-origin browser rules prevent dependable inspection of arbitrary sites' response headers or TLS certificate details.
Available: copy findings to clipboard or use your browser's Print / Save PDF feature. History stays in local browser storage.