PRIVACY
& DATA.
What stays in your browser, what must leave it, and when data may be retained.
Local tools
Hash/Checksum, JSON, UUID, URL/Base64 and other tools marked LOCAL run in your browser. Text and files used by those utilities are not sent to the Bit Happens backend.
External queries
DNS, RDAP, Email Health, Domain Health, domain inventory, HTTP/HTTPS and similar tools must send the technical target you entered — such as a domain, hostname or IP — to the Bit Happens Worker and, where required, public upstream services. Do not enter passwords, tokens or other secrets.
The technical target and parameters required for the requested query.
Run the requested diagnostic and return its result.
Normal queries do not create an account-level query history. Infrastructure providers may keep operational request metadata under their own policies.
Port Check and authorized Nmap
Active tests send the target, applicable ports/profile and a Turnstile token to the backend. Turnstile is verified by Cloudflare. Advanced Nmap may also require DNS TXT proof and additional operational authorization. Use these features only on assets you own or are explicitly authorized to test.
Aggregate measurements
Network Pulse may retain scheduled technical measurements of infrastructure observed by Bit Happens to build availability history. These measurements are not a personal history of visitor-entered queries.
Google Analytics only after consent
The external Google Analytics script is not loaded until Analytics has been explicitly accepted. Advertising storage and ad personalization remain disabled.
Necessary technical metadata
Like any web service, infrastructure providers may process connection and security metadata such as IP address, time, User-Agent and network information. Bit Happens uses abuse controls, rate limiting and private/reserved-target blocking for external tests.