What Find DNS Record does
Find DNS Record sends a typed DNS query for the submitted hostname. The response can include record value, time to live, and priority, depending on the selected type and the data returned by the resolver. Up to one hundred normalized records are shown.
Each record type answers a different operational question: A and AAAA map hosts to addresses, MX directs mail, NS identifies name servers, CAA restricts certificate issuers, CNAME aliases names, SOA describes zone authority, and TXT carries policy or verification text. A successful lookup describes published DNS, not whether the associated service is configured correctly.
How to use Find DNS Record
- Enter a public hostname or domain name.
- Choose the DNS type that matches the record you need to inspect.
- Select Find records and review the normalized values, TTLs, and priorities.
- Compare important results with the authoritative DNS provider before making a production change.
Important details
TTL and priority are type-dependent
A resolver may expose a TTL for cached records, while MX records can include a priority and SOA contains several zone values. A null field means that value was not supplied in the normalized answer.
TXT answers may be split
DNS servers can represent one TXT record as multiple character strings. Read joined policy values carefully, especially for SPF, DKIM, DMARC, and ownership-verification records.
Address answers must be public
For A and AAAA queries, PagesTools rejects a response containing private, local, or reserved addresses. The tool is intended for public DNS inspection rather than internal zone discovery.
Practical uses
- Check MX and TXT records while diagnosing email authentication.
- Review A, AAAA, and CNAME answers after a DNS deployment.
- Inspect CAA, NS, or SOA data during certificate and delegation work.
Privacy and limitations
The hostname and selected record type are sent to PagesTools and its configured DNS resolver. The resolver can observe the query, no website page is fetched, and the JSON response uses no-store cache headers.
Results reflect the server's resolver and cache, are capped at one hundred records, and can differ from another network. This is not a DNSSEC validator, propagation monitor, or historical DNS database.