1. Data processed for a DNS lookup
When you run a check, MyWebDNS receives the domain name, hostname or IP address you entered and the selected DNS record type. The service normalizes that input and sends the resulting DNS question to enabled measurement sources. These may include Globalping community probes, private MyWebDNS workers and their resolver paths.
DNS names are generally public infrastructure data, but a private or not-yet-announced hostname can still reveal information. Do not submit a target you are not comfortable sending to Globalping and the DNS infrastructure used by the selected probes.
2. Short-lived caching
MyWebDNS may keep a successful lookup response in server memory for a short period. The actual cache duration is bounded by the active service configuration and the smallest positive TTL returned with the answer. Responses containing a timeout or failed probe are not cached by the lookup orchestrator.
3. Security and operational metadata
The service applies per-IP rate limiting to public DNS lookups. Depending on the web server, reverse proxy and hosting configuration, basic request metadata such as IP address, request time, route, response status and user-agent may also be processed in technical logs for security and reliability.
Probe execution logs include technical node, query and timing identifiers needed to diagnose the distributed lookup workflow. Browser-facing errors do not expose stack traces or worker credentials.
4. Cookies and browser storage
The DNS form uses an HTTP-only, secure antiforgery cookie so the server can reject cross-site submissions. This cookie is necessary for the lookup security control. The current interface does not use local storage, advertising cookies or third-party analytics cookies.
5. Third parties
The browser interface loads its CSS, JavaScript and brand assets from MyWebDNS itself. When global measurements are enabled, the MyWebDNS server sends the normalized DNS target, selected record type and requested country selections to the Globalping API. The selected community probes and their resolver operators may process the DNS question under their own technical and privacy practices.
Private MyWebDNS workers likewise send DNS questions through their configured resolver paths. MyWebDNS does not control the independent processing or retention practices of those external networks.
If you contact MyWebDNS by email, your email provider and the receiving mail provider process that message outside the website application.
6. Retention and control
In-memory DNS cache entries expire automatically. Retention for infrastructure logs depends on the active hosting and operations configuration. MyWebDNS does not expose user accounts or a stored lookup-history feature in this release.
7. Changes and questions
This notice should be reviewed whenever analytics, accounts, new infrastructure providers or a different retention policy are introduced. Questions about this notice can be sent to [email protected].