What Is a DNS Record Lookup and What Does It Show?
A DNS Record Lookup is an essential networking inspection tool that queries the Domain Name System (DNS) to expose the distributed database entries that govern how a domain directs web traffic, routes corporate emails, and validates security parameters.
Rather than relying on unencrypted, legacy UDP port 53 packets—which shared web hosting platforms often block to mitigate outbound DDoS amplification attacks—our tool issues cryptographically signed HTTP requests to Cloudflare's global DNS-over-HTTPS (DoH) edge network. This guarantees maximum uptime, eliminates local ISP DNS cache tampering, and reveals authentic, real-time records as announced by authoritative nameservers.
How to Use This Tool
- Enter Domain Name: Type any active domain name (such as
github.comornytimes.com) into the search bar. Do not enter protocols likehttps://or subfolder paths. - Select Record Type: Leave the selector on ALL to inspect every major record family simultaneously, or choose a specific record type (such as MX for mail servers or TXT for SPF verification).
- Execute Query: Click "Lookup Records" to initiate the secure DoH interrogation.
- Inspect & Copy Data: Examine the resulting table displaying record types, Time to Live (TTL) expiration counters, and target IP addresses or text payloads. Click "Copy" to capture any record for your configuration files.
Why DNS Record Inspection Is Essential for Webmasters & Engineers
DNS records form the invisible plumbing of the global internet. Auditing them is essential for numerous operational requirements:
- Website Migration & DNS Propagation Tracking: When moving a website to a new server or cloud provider, administrators update their A or CNAME records. Because caching resolvers worldwide refresh at different intervals determined by TTL, running a DoH lookup confirms whether the global authoritative root has successfully published the new target IP.
- Email Deliverability & Spam Mitigation: If transactional or marketing emails land in recipients' spam folders, missing or corrupted DNS authentication records are almost always the culprit. Verifying SPF (Sender Policy Framework), DKIM (DomainKeys Identified Mail), and DMARC records published inside TXT records is the first diagnostic step.
- Mail Server Redundancy: Verifying MX record priority values ensures that secondary or backup mail exchange servers take over seamlessly if a primary corporate mail server experiences downtime.
- SSL/TLS Certificate Domain Validation: Many Certificate Authorities (such as Let's Encrypt or Sectigo) require administrators to add specific CNAME or TXT challenge records to confirm domain ownership before issuing SSL certificates.
Comprehensive DNS Record Reference Table
| Record | Full Name | Core Function | Example Output |
|---|---|---|---|
| A | Address Mapping | Resolves a hostname to a 32-bit IPv4 address | 198.51.100.25 |
| AAAA | IPv6 Address Mapping | Resolves a hostname to a 128-bit IPv6 address | 2606:4700::6811:d209 |
| MX | Mail Exchanger | Directs domain email to responsible mail servers | 10 aspmx.l.google.com |
| NS | Name Server | Delegates a DNS zone to authoritative nameservers | ns1.cloudflare.com |
| TXT | Text Record | Carries SPF, DKIM, DMARC, and verification tokens | v=spf1 include:_spf.google.com ~all |
| CNAME | Canonical Name | Aliases one domain name to another domain | app.example.com → alb.aws.com |
| SOA | Start of Authority | Contains zone admin details, serial, and refresh timers | dns1.p01.nsone.net hostmaster... |
Frequently Asked Questions
DNS-over-HTTPS (DoH) sends standard DNS queries encrypted over an HTTPS session (port 443) rather than plaintext UDP (port 53). We use DoH because shared hosting providers frequently block outbound UDP 53, preventing native PHP DNS functions from operating reliably. DoH also ensures lookups are immune to ISP eavesdropping, hijacking, or censorship.
MX records indicate the mail servers responsible for accepting incoming emails on behalf of a domain. Each MX record includes a priority preference number; lower priority numbers indicate higher precedence. When sending emails, remote mail transfer agents (MTAs) attempt delivery to the lowest-number server first.
TXT records allow domain owners to associate arbitrary text with a domain name. Today, they are predominantly used for email authentication protocols (SPF, DKIM, and DMARC) to prevent spam spoofing, as well as domain ownership verification for Google Search Console, SSL certificates, and cloud services.
TTL (Time to Live) is a numerical value expressed in seconds that tells recursive DNS resolvers and web browsers how long they can cache a DNS record locally before querying the authoritative name server again for fresh data.
An A record maps a domain name directly to a 32-bit IPv4 address (e.g. 192.0.2.1). A CNAME (Canonical Name) record aliases one domain name to another domain name (e.g. www.example.com to example.com), requiring the resolver to perform an additional lookup to find the ultimate IP address.