PRIVACY & DATA

A clear tool. A clear data policy.

Zonebeam has no accounts or ads. It stores your theme preference in your browser and uses Vercel Web Analytics for traffic statistics.

What a check sends

The domain or DNS name and selected record types are sent from Zonebeam to Globalping. Globalping distributes the request to geographic probes. Each probe queries its local resolver. CAA checks use Google Public DNS over HTTPS from each probe. Do not enter secrets or private internal host names.

Zonebeam also sends the DNS name and its parent domains to Google Public DNS to find the name servers and identify the DNS provider. This request comes from the server and disables client subnet data. Provider details are cached for up to five minutes and included in the saved check result.

Temporary results

Zonebeam stores check results in Neon for 24 hours of access. Check handles are random. Anyone with a handle or result link can read that check until it expires. Expired rows are deleted when the service next processes a new check.

Globalping retains its own public measurement records. Its API documentation states that measurements are typically available for up to six months. A Zonebeam expiry does not delete the provider record.

Request limits and hosting

The service uses a daily, salted hash of the client network address for shared request limits. It does not store the raw address in its application database. Vercel, Neon, Globalping, and DNS resolver operators can process connection information under their own policies. Vercel may retain infrastructure request logs.

Agent access

The JSON API, remote MCP, and browser tools use the same DNS service. Browser tool access depends on your browser and agent permissions. DNS record text is external data and must not be treated as instructions.

Website analytics

Vercel Web Analytics counts page visits and provides statistics about referrers, browsers, devices, and approximate locations. It uses a temporary visitor hash instead of tracking cookies.

Zonebeam removes query parameters and URL fragments from analytics page URLs. It does not send domain inputs, DNS answers, or check handles as analytics events.