NHCheck

Last updated 31 October 2026

NHCheck Lite collects nothing

No account, no analytics, no crash reporting, no advertising, no third-party SDKs. Nothing you do in the app is sent anywhere, and there is no server behind it to send anything to.

What is collected

Nothing. NHCheck Lite does not ask you to sign in, does not collect or transmit personal information, does not upload results, does not read your contacts, photos, files or position, and does not track you across apps or websites.

What stays on the device

Your language and appearance choices, whether you said the router is yours, and the plan speed you typed on the Speed page so results can be judged against it. Also, for the last few Wi-Fi networks you joined: what answered for each the last time — the router’s address, the maker of its access point, its hardware address where the phone is allowed to read it, and the DNS servers it handed out. It is kept under a scrambled form of the network’s name rather than the name, and it is only used to tell you when a network name is suddenly answered by something else. That is all. Results are held only while the app is open.

Both settings go when you uninstall the app. They are also small enough to be eligible for Android's own backup to your Google account — a platform feature, switched on or off in your device settings, not something this app operates. Nothing reaches us either way: there is no server behind the app.

What a run sends

The app measures your connection, so a run puts traffic on the network. Only when you press Run, and only this:

Your routerEcho requests that never leave your own network
The first public router past itProbes to find it, then echo requests to measure it
A DNS resolverOne name lookup, to time it. No page is fetched.
CloudflareFiller data down and up for eight seconds each, to measure throughput. While it runs, a short connection to the same server and an echo to your router every few hundred milliseconds, to see whether latency rises under load
Cloudflare, over IPv6 and IPv4One connection attempt to its resolver address over each, to tell whether IPv6 works here. Only when your network has given this device an IPv6 address; nothing is sent past the handshake

Any server you contact sees the public address the request came from — that is true of every app on your phone. Nothing identifying you is attached: no identifier, no device name, no account, no results.

Looking at your own network

When you open the LAN page, the app sends a probe to every address on your local network and asks whatever answers what it is called, over mDNS, SSDP and Bonjour — the same announcements those devices already broadcast to the network. The names and addresses it finds are shown to you and held only while the app is open. They are never sent anywhere: there is no server behind this app.

A device name is often a person's name with a machine after it, so it is the most personal thing the app ever reads. It is read on your device, shown on your device, and gone when you close the app.

Comparing resolvers

The DNS page can time your resolver against four public ones — Cloudflare, Google, Quad9 and OpenDNS — so a slow one is something you can see rather than guess at. It runs only when you open that page and ask for it, never as part of a run.

This is the one thing in the app that contacts a company you did not choose, so it is worth being exact. It sends each of those four a handful of ordinary lookups for well-known sites — wikipedia.org, github.com and the like — which are ours, not yours: the app never sends a name you looked up. Each of them sees the public address the request came from, as any site you open does. The timings are shown on your screen and kept nowhere.

Measuring the route

The ISP page can trace the route to a public resolver you pick — Cloudflare, Google, Quad9 or OpenDNS — and send a handful of echoes to every router that answers along it — the ones inside your provider’s network and the few beyond. It runs only when you open that page and ask for it, never as part of a run. Each router sees that the echo came from your public address, as it does for every packet you send; nothing else goes with it. The timings are drawn on your screen and kept nowhere.

Comparing content networks

The Speed page can pull a real public file from each of five content networks — Cloudflare, Google, Fastly, Akamai and Amazon CloudFront — on one connection and then on four at once, so a line that is fast to one network and slow to another is something you can see rather than guess at. The Akamai file is a Microsoft installer that Akamai serves; the Amazon file is an AWS installer. It runs only when you open that page and ask for it, never as part of a run.

The page can also show which of those networks serves each part of X, TikTok, Snapchat or YouTube. That is a handful of name lookups through your own resolver, the same ones your phone makes when it opens those apps; nothing is fetched from the sites themselves.

Each of the five sees the public address the request came from, as any site you open does; nothing identifying goes with it, and the files are theirs, not yours. It moves real data — up to a few hundred megabytes on a fast line — so it is worth knowing about on a metered plan. The figures are drawn on your screen and kept nowhere.

Line tests and two-phone speed

Some tests the app does not run by itself. Stability and speed between two phones start only when you tap them. Packet size also starts when you open the ISP page or run it again there. Each stops when you leave the page.

Stability sends an echo four times a second for a minute to your router, to the first public router past it, and to 8.8.8.8 — the same address the route walk already uses — and draws what came back. Packet size sends echoes of growing size, flagged not to be split, to 8.8.8.8 and to your router, to find the largest that crosses. Nothing but the echoes is sent, and nothing identifying goes with them.

Is DNS rewritten runs on the DNS page, alongside the comparison. It asks your own resolver and each of the four public ones for one random name under google.com that cannot exist, and reads whether any of them invents an address for it. It then asks each of them for two names, whoami.akamai.net (run by Akamai) and whoami.ultradns.net (run by UltraDNS), which are built to reply with the address of whoever asked. Two resolvers that give the same reply were answered by the same machine. Those two companies’ name servers see the address of the resolver that passed the question on, and not your phone’s own address. Nothing real is looked up, and your own lookups are never sent.

Speed between two phones never touches the internet. One phone listens and announces itself on your local network as “NHCheck” and four random characters — not your phone’s name — and the other finds it and sends filler data for a few seconds in each direction, once its owner has typed the four-digit code that the listening phone shows. The listening phone accepts one device at a time, at most four connections, ten seconds each, and only while that page is open. Both phones see each other’s address on your network, as any two devices on it can; nothing leaves the network.

On mobile data

With Wi-Fi off, the app reads what your phone already knows about its own mobile link: the operator, the radio, the signal and its quality, the band and frequency, and the identities of the cells it can hear. Android gates the cell identities behind the same Location permission as the Wi-Fi scan, for the same reason — a list of nearby towers can be used to infer position. All of it is read on your device and shown on your device. None of it is stored, and none of it is sent anywhere.

The location permission

Android requires the Location permission before any app may read the Wi-Fi network name, scan for nearby networks, or identify the mobile cells in range — because a list of what is nearby, whether networks or towers, can be used to infer position. It is used for those alone — your position is never read, stored or sent. The app never requests a location fix, never touches GPS, and never accesses location in the background. Nothing is asked at launch: the app explains why before the system prompt appears. Decline it and every check still runs; you lose the network name, the channel advice and the mobile link details. You can withdraw it at any time in Settings → Apps → NHCheck Lite → Permissions.

Your rights

Rights of access, correction, deletion and portability apply to personal data that has been collected. None is, so there is nothing to disclose, export or erase.

Changes

If a future version changes what the app contacts or keeps, this page is updated before that version is released, and the date above changes with it.

Contact

NHCheck · Jeddah, Saudi Arabia · info@nhcheck.net