NHCheck

NHCheck Lite

Documentation

Five checks run in order, about thirty seconds in all. The speed test is last because it saturates the connection and would corrupt the figures before it. Two of the rows open into a page of their own: the radio you are on — the air around you, or the mobile link — and the devices on your network.

The checks

CheckWhat it does
Wi-Fi statusReads signal, noise, channel, band, standard and security, then scans the neighbours and names the clearest channel in the band. Off Wi-Fi the row becomes Link status and judges the other radio instead: the operator, the generation, the signal and its quality, the band, and the cells in range
LAN gatewayEight echoes to your router — latency, loss and jitter of the Wi-Fi link itself — then a sweep of the network behind it, counting what answered
ISP gatewayFinds the first public router past yours and measures it with six echoes
DNS lookupResolves a name through your network's resolver and times it
Speed testDownload then upload, eight seconds each over parallel streams, measured after a warm-up
NHCheck Lite mid-run: the path diagram above a Stop button, Wi-Fi status already passed at −52 dBm on 5 GHz channel 36, and the LAN gateway row sweeping the network — 350 of 508 addresses asked, 42 found.
A run in progress — each check reports as it finishes

Verdicts

PASSMeasured, and inside every target
WARNMeasured, and outside at least one — the recommendation says which
FAILNothing answered, the name did not resolve, or no data moved
SKIPNot measured, and not a fault — the network's policy prevented it

Thresholds

CheckWARN whenFAIL when
Wi-Fi Signal below −67 dBm · signal-to-noise below 25 dB · another network on your channel · three overlapping · radar-shared channel · open or outdated security Not connected
Mobile link RSRP below −110 dBm · signal-to-interference-and-noise below 0 dB · still on 2G or 3G RSRP below −120 dBm
LAN gateway Loss 1% or more · average over 100 ms · jitter over 60 ms, or larger than the link's own average No reply
ISP gateway Loss 1% or more · average over 150 ms · jitter over 60 ms —
DNS Slower than 300 ms Did not resolve
Speed Download below 5 Mbps · upload below 1 Mbps A direction moved nothing

A silent ISP gateway is reported as SKIP, not FAIL: those routers ignore probes as routine policy. A direction that moves nothing is reported as a failure with its reason, never as 0.00 Mbps.

Behind two of the rows

The Wi-Fi row, on Wi-Fi, opens an analyser. Every network in range is drawn as an arc over the spectrum it occupies, so two networks nominally on different channels are visibly on top of each other when they overlap. Beside it, every radio ranked by strength, and your own link traced second by second — signal as bars, signal-to-noise as a red line over them — so a sag shows as a shape rather than disappearing into an average.

The same row on mobile data opens the mobile link instead: the operator and the generation, the signal with its quality, the band and frequency, and every cell the phone can hear — each with its own signal, so the one you are registered to can be read against the rest. It is traced second by second like the Wi-Fi link. Android gates the cell identities behind the Location permission, for the same reason it gates the Wi-Fi scan; see the privacy policy.

The LAN row opens the list of what is on your network: every address that answered the sweep, with the name it publishes — a hostname, a UPnP name, or the service it advertises — your router and this phone marked. The names come from the announcements those devices already broadcast, over mDNS, SSDP and Bonjour. They are read on your device, shown on it, and held only while the app is open; see the privacy policy.

The LAN page: 47 answered the sweep, listed by address — some naming themselves, others marked as having given no name, one tagged Android TV and This device, another tagged web page — above an Ask again button.
The LAN page — what answered, and what it calls itself

Permission

Android requires a location permission before an app may read the connected Wi-Fi network's name or scan for neighbours. NHCheck Lite asks for it for that alone: it never requests a location fix, never touches GPS, and never reads location in the background. The same permission gates the identities of the mobile cells in range, which is the other thing it is used for. Decline it and every check still runs — you lose the network name, the channel advice, the analyser's neighbour list and the detail of the mobile link. See the privacy policy.

Requirements

PlatformAndroid phone or tablet — on Google Play
PriceFree — no subscription, no advertising
LanguagesEnglish, العربية, Español, اردو, Português and Français — switched in place, with Arabic and Urdu laid out right to left
AppearanceDark, light, or whatever the phone is set to
AccountNone