
NetMaster: Network Tester
Speed, DNS & Dropout Tests
About
What's New in NetMaster
1.0.5
August 22, 2026
Measuring satellite and aircraft connections properly, and never grading a connection on half the evidence. • Upload speed on high-latency links. On an aircraft or a satellite connection, a round trip can take three quarters of a second, and the upload test's fixed time limit was being spent establishing connections rather than measuring one — so upload came back blank on exactly the connections people most want to check. The time limit now scales with the round trip the scan has already measured, the sizing probe shrinks on distant links, and transfers are sized to keep a long link genuinely busy rather than waiting on it. • When a measurement cannot be taken, the report says which one and why. An empty field beside a working number is the least useful thing a diagnostic can print. Upload, first-hop timing, and the Wi-Fi standard now each explain their own absence. • The latency-under-load grade no longer treats one direction as two. It has always graded the worst direction it measured, but a download-only grade looked identical to one measured both ways — and upload is usually the worse direction. The grade now says when it saw only one, and counts for less in the headline score. • Fabricated DNS loss on slow connections is fixed. The direct UDP DNS check judged every request against the moment the run ended rather than its own waiting time, so on a link slower than about a second and a half it could report a burst of lost responses, a specific loss percentage, and a critical warning without a single response actually being lost. Requests are now judged individually, and a connection answering slower than the check waits is reported as unmeasurable rather than lossy. • DNS advice that matches what was measured. Some networks degrade ordinary DNS while carrying encrypted DNS to the same providers perfectly — that is a network steering lookups to its own resolver, not a broken one. Where the scan sees exactly that, it now says so and points at encrypted DNS, because switching to a plain public resolver would send more of the traffic already being dropped.
More


