NetMaster: Network Testerv1.0.3
Released August 14, 2026Major
iOS
What changed
- New featureIntroduced a new multi-gigabit test profile supporting up to 2.5 Gbps with increased payload and parallel connections.
- UXRenamed the 'Maximum' profile to 'Gigabit' to accurately reflect its measurement capacity.
- SocialAdded encrypted-DNS availability and resolver verdicts to exported and shared reports.
- UXUpdated tunnel-active DNS reporting to be informational rather than a warning, providing clearer context on encryption.
- PerformanceImplemented dynamic test payload sizing based on link speed to improve measurement reliability and prevent timeouts.
Original release notes
Multi-gigabit measurement, and the DNS privacy findings now travel with your shared reports. • Multi-gigabit test profile: a 2 Gb or 2.5 Gb line — or Wi-Fi fast enough to carry one — spent the previous budget before the connection reached a steady rate, so it could only ever be reported as a floor rather than judged against your plan. The new profile measures to roughly 2.5 Gbps over a settled window, using a much larger payload budget and eight parallel connections instead of four. It moves well over a gigabyte on a link that quick, so it is a deliberate choice made on Wi-Fi rather than a routine scan. • The profile previously called Maximum is now called Gigabit: the same budget, named for what it actually measures. Settings still states the fastest link each budget can measure before you scan, so you can pick one that can reach your plan. • DNS privacy in shared reports: the encrypted-DNS availability result and the expected-resolver verdict now appear in the exported report as well as on screen. The copy you send to a provider, or keep for your own records, carries the whole DNS picture instead of the transport line alone. • Classic DNS seen while a tunnel is active is now reported as information rather than a warning, and says what the tunnel actually covered. A VPN encrypts your lookups as far as its exit; whether they stay encrypted past that point depends on the resolver at the far end, which no app on the device can see. The report says so plainly rather than implying nothing was protected. • Measurement reliability on fast connections: test payloads are now sized from the link itself, staying large enough to be efficient on a quick connection while remaining small enough to finish on a slow one, so a result is not discarded for arriving too late.