MyWebDNS

Measurement methodology

Know what ran, where it ran and what it can prove.

MyWebDNS separates the location of the probe that ran an observation from the behavior of the resolver it queried. That distinction prevents an anycast IP address from becoming a false country claim.

Input
Normalized domain or IP plus record type
Unit of evidence
One sampled probe observation
Transport
Global community, local or signed worker
Output
Status, values, TTL, latency and resolver

Collection path

How a MyWebDNS lookup is assembled.

  1. 1

    Normalize the query

    The server validates the record type, trims the name, converts internationalized domains to their ASCII DNS form and builds a reverse name for PTR input when required.

  2. 2

    Freeze the measurement plan

    Available Globalping locations and enabled private nodes are selected for that lookup. The response keeps the actual probe location, provider and execution mode with each observation.

  3. 3

    Run with bounded concurrency

    Nodes execute in parallel up to the configured limit. Each lookup is bounded by a node timeout and an overall request timeout so one slow probe cannot hold the page indefinitely.

  4. 4

    Classify the DNS response

    Returned data, no-data responses, NXDOMAIN, timeout and execution failure remain distinct. MyWebDNS does not manufacture an empty answer to make a failed probe look complete.

  5. 5

    Compare complete answer sets

    Agreement is calculated among probes that returned answers by comparing their full normalized value sets. It does not include timed-out or empty nodes as agreeing answers.

Location integrity

The marker belongs to the probe.

The country, city, latitude and longitude shown by MyWebDNS describe the probe that actually ran that sampled query.

What it means

A community probe selected in Istanbul or a private worker operating there can accurately be described as an Istanbul observation. Its result shows the view available to the resolver reached from that execution environment, not every resolver in Türkiye.

What it does not mean

A resolver address such as a public anycast service does not have one reliable physical country. MyWebDNS therefore does not geolocate the resolver IP and present that result as the measurement origin.

Source integrity

Probe sources are identified, not assumed.

Global measurements use the country, city, network and coordinates returned for the selected Globalping community probe. Private MyWebDNS workers use centrally configured metadata and signed transport.

Community measurements

Globalping supplies the actual probe metadata and structured DNS response. A missing or unavailable probe remains unavailable instead of becoming a false propagation result.

Signed private workers

The worker identity, request body and route are covered by HMAC-SHA256. Stale timestamps and repeated nonces are rejected, and credentials never reach the browser.

Interpretation limits

What this measurement cannot settle on its own.

  • It does not prove that every resolver or user in a country receives the same answer.
  • An unavailable or timed-out probe does not prove that a DNS record is missing or has not propagated.
  • It does not distinguish intentional GeoDNS policy from a stale cache without authoritative context.
  • Response time includes the configured resolver path and is not a website latency measurement.
  • A successful DNS answer does not prove that the application behind the address is healthy.