Privacy
Privacy
The short version: no cookies, no accounts, and nothing you look up is stored by us.
What we don't do
- No cookies and no tracking across sites.
- No accounts — there's nothing to sign up for.
- Lookups aren't stored. Most run straight from your browser to the services below. The ones that go through our server (MAC vendor, Down Checker and Port Checker) aren't logged or saved.
Two things are saved on your device, and neither leaves it: your light/dark theme choice, in local storage, and the app shell — the site's pages, code, styles and icons — in the browser's offline cache, so the site opens without a connection and can be installed as an app. Lookups and their results are never cached; the tool pages are stored blank. Clearing the site's data in your browser removes both.
Analytics
We use Cloudflare Web Analytics to count visits. It doesn't use cookies or local storage, and reports are anonymous and aggregate: which pages are viewed, referring sites, country, browser and device type, and page load speed. Page addresses are recorded without the query string, so the hostnames and IPs you look up are never part of it. See Cloudflare Web Analytics and Cloudflare's privacy policy.
The site is hosted on Cloudflare, which handles every request like any web host does.
Services each tool uses
A lookup has to ask someone. These are the services involved; requests your browser makes directly are seen by that service along with your IP address, like any website visit.
-
Your browser asks ipwho.is about the address (or about your own IP when the box is empty).
-
Your browser sends the domain and record type to dns.google over DNS-over-HTTPS.
-
Your browser queries dns.google for the IP in each blacklist's zone. The blacklist operators see Google's resolvers, not you.
-
Our server forwards the MAC address to api.macvendors.com, so they see our server, not your IP.
-
Your browser sends the target and probe location to api.globalping.io. Globalping keeps measurement results under a random ID, per its own policy.
-
Our server resolves the hostname with dns.google and requests the site from Cloudflare's network. The site sees Cloudflare, not you.
-
Our server resolves the hostname with dns.google, then opens one TCP connection to the port from Cloudflare's network and closes it — nothing is sent. With the host left empty, it tests the IP your request came from. Hosts and ports aren't logged.
- Subnet Calculator None
Calculated entirely in your browser.