MyWebDNS

Independent DNS observations

Check TXT records across available probe locations.

TXT records publish text used by email authentication, ownership checks and application configuration.

14 probes configured
  • EvidenceAnswer, TTL, probe status and latency
  • Record typesA through CAA, including PTR
  • LocationProbe-reported coordinates, never random markers

QUERY / DNS

Run a DNS check

DNS

Use a hostname for most records. PTR also accepts an IPv4 or IPv6 address.

Native browser record menu.

Lookup requests are protected against cross-site submission and rate limited.

Observation desk

DNS results

Every row is one sampled probe observation. Agreement describes matching answers among probes that returned data; it is not an uptime or country-wide propagation score.

Ready for a lookup

Enter a domain and choose a record type to populate the observation map and result table.

DNS record field guide

How to read a TXT record check

TXT records publish text used by email authentication, ownership checks and application configuration.

When to use this lookup

Use the full owner name, such as _dmarc.example.com or selector._domainkey.example.com, when checking a record below the zone apex.

Example

_dmarc.example.com TXT v=DMARC1; p=none
Answer shape
One or more text values; a DNS library may join multiple quoted character strings into one logical answer.
Common failure
The record was published at the wrong owner name, or multiple conflicting SPF policies exist at one name.
Related checks
MX record

Troubleshooting checklist

  • Query the exact subdomain where the provider asked you to publish the record.
  • Keep SPF within its DNS lookup limit and avoid multiple SPF records at one name.
  • Quoted TXT chunks may be returned separately but represent one logical value.