NetMaster vs Kodura Network Tools

NetMaster helps explain slowdowns, instability, and intermittent dropouts without an account, ads, analytics, or tracking. RUN A COMPLETE NETWORK SCAN • Measure download and upload goodput with parallel HTTPS requests • See HTTPS latency, adjacent response-time variation, request failures, and a second latency vantage point • See confidence ranges and a p95 only when enough observations support it • Check direct UDP DNS response delivery across two providers, including bursts • Check latency under load and receive a bufferbloat grade • Compare everyday and first-time DNS response times • See the DNS transport observed for NetMaster’s measured request and compare resolver performance • Test real IPv4 and IPv6 reachability • Time the router hop and see whether added delay is local or farther upstream • Review public IP, ASN, egress region, TLS, HTTP, Wi-Fi security, captive-portal evidence, and tunnel indicators • Optionally install the bundled NetMaster Shortcut for connected iPhone Wi-Fi channel, standard, RSSI, noise, and RX/TX PHY rates — no compatible router or controller required • Watch live signal/noise, negotiated PHY rates, passive device traffic, and access-point changes • Compare the OS route gateway, Apple, Cloudflare, Google, and selected public-service latency graphs, rotating one probe at a time • Optionally select an M-Lab server for a separate single-flow route cross-check NARROW DOWN CONNECTION PROBLEMS Quick Diagnosis checks the path, router, internet, DNS, and responsiveness in sequence, then gives one likely explanation and a practical next step. INVESTIGATE INTERMITTENT DROPOUTS Run a 5-, 15-, or 30-minute monitor. On iOS 26, a user-started finite session can request lock-screen continuation; earlier versions must keep NetMaster visible. NetMaster records route changes, HTTPS heartbeats, gateway/DNS controls, IPv4/IPv6 evidence, latency changes, unknown gaps, and optional AP-roaming evidence. ESTIMATE ACTIVITY NEEDS Cautious assessments cover calls, 4K streaming, gaming, browsing, and uploads while naming the measured evidence and its limits. Protected history compares the same network over time, with a metrics-only mode. WATCH YOUR MAC FROM IPHONE Pair one iPhone to your Mac through private iCloud. See processor, memory, thermal, battery, and Mac traffic updates, 30-day history, eligible alerts, and PDF/CSV reports. Storage and low-storage findings remain visible only on the Mac. Remote speed tests require confirmation. BUILT FOR HONEST RESULTS A payload budget controls data use. Replenished parallel transfers target a stable window; when the cap ends a fast test too soon, the result is a lower bound, not a claimed maximum. Full-scan HTTPS timing is not ICMP ping; the separate live-latency board uses explicitly labeled ICMP echo. HTTPS adjacent response variation is not packet jitter; HTTPS request failures and UDP DNS response loss are not raw packet loss. PRIVACY BY DESIGN History stays in protected on-device storage. Optional Mac monitoring uses your private CloudKit database and no developer monitoring server. Reports leave only when you choose Share, with address redaction on by default. Important: Direct iOS app APIs omit exact radio values. The optional user-installed Shortcut uses Apple's Get Network Details action for connected RSSI, noise, channel, standard, and PHY rates; derived band can be ambiguous. Channel width, RF spectrum health, and cellular dBm are never invented. Wi-Fi identity needs permission. Balanced allows about 54.5 MB of throughput payload plus small requests and protocol overhead. Results are evidence, not proof that a router, carrier, VPN, or service is defective.

Basic network troubleshooting, all in one place. Ping, traceroute, DNS lookups, port checks and path MTU discovery — the five things you reach for when something is wrong, without five separate apps and five separate subscriptions. NO ADS. NOTHING TO BUY. No banners, no upgrade prompts, no account, no subscription. Every tool is there the moment you open it. ONE TARGET, EVERY TOOL Type a host once and it carries across all five. A real diagnosis moves between them — ping gets nothing back, so you trace the path; the trace stops at hop nine, so you check whether DNS gave you the right address; then you see whether the port is even open. Retyping the hostname at every step is the friction that sends people back to a laptop. RESULTS THAT EXPLAIN THEMSELVES Most tools hand you a column of numbers and leave the interpretation to you. This one tells you what it means: • A hop showing * is usually a router configured not to reply, not a break in the path. If later hops answered, your traffic went straight through. • A host that ignores ping may be perfectly healthy. Plenty of servers and firewalls drop ICMP deliberately, so silence is not proof of anything. • Jitter is judged against the latency it varies around. Thirty milliseconds of variation is fine on a satellite link and terrible on a local one. • A port that refuses a connection is telling you something. A port that stays silent is what a firewall looks like — and those are different problems. PING Loss, round-trip time, and jitter, with the distribution drawn so you can see the shape of the variation rather than reading it out of a list. TRACEROUTE Every hop with its round-trip times and reverse DNS name, and a clear statement of where the path actually ended — as opposed to where a router simply declined to introduce itself. DNS LOOKUP A, AAAA, CNAME, MX, TXT, NS, SOA and PTR, against a resolver you choose — Cloudflare, Google, Quad9 or OpenDNS — rather than whichever one your device happens to be using. Asking two resolvers the same question and getting different answers is often the whole diagnosis. "No such name" and "the server failed" are reported as the different problems they are. PORT CHECK Common services by name, or any ports you type. Refused and silent are reported separately, and anything open that usually should not be — databases, remote desktop, SMB — is called out. PATH MTU The largest packet that survives the whole path, found by probing with the don't-fragment bit set. Worth knowing because an MTU mismatch produces the strangest fault in networking: small requests work and large ones hang. SSH connects then freezes on long output, a page loads but one image never finishes, a tunnelled connection is fine until somebody sends an attachment. It looks like an application problem, and the application is fine. Built by Kodura for network engineers, sysadmins and anyone who has been handed a laptop and asked why the internet is slow.