Trexmi
Network Ready

DNS Lookup

Look up DNS records for a domain, including A, AAAA, MX, TXT, NS, CNAME, SOA, and CAA records.

A and AAAA lookup MX lookup TXT lookup NS lookup
DNS answers come from the resolver available to the Trexmi server and may reflect resolver caching.
INPUT Domain name *
0 chars0 words0 lines

Tool settings

Ctrl / ⌘ + Enter
DNS lookup results Visual DNS summary, grouped records, warnings, and raw JSON.
About the tool

What DNS Lookup does

DNS Lookup checks the public Domain Name System records returned for a hostname by the resolver available to the Trexmi server. Use DNS Lookup to inspect where a domain points, which nameservers are authoritative, where mail is delivered, what TXT policies are published, and whether aliases or certificate authority restrictions exist.

DNS is a distributed naming system. A browser usually begins with A or AAAA records to find an IP address, while mail systems use MX records, administrators publish SPF or verification information in TXT records, and NS records identify the authoritative nameservers for a zone.

DNS Lookup showing domain records IP addresses nameservers and mail servers
DNS Lookup groups public DNS answers into an easy-to-read network report.

How to use

  1. Enter a domain. Use a hostname such as example.com without a URL path.
  2. Select a record type. Choose All common records for a broad overview or select A, AAAA, MX, TXT, NS, CNAME, SOA, or CAA.
  3. Run DNS Lookup. Trexmi asks the server resolver for the selected DNS data.
  4. Review the visual summary. Check IP addresses, nameservers, mail servers, record counts, priorities, and TTL values.
  5. Compare expected configuration. Unexpected records can point to old hosting, stale verification values, or incomplete migrations.
Built for the task

Why use DNS Lookup?

Focused controls, predictable output, and a workflow designed around this exact transformation.

01

Inspect common DNS records

Review A, AAAA, MX, TXT, NS, CNAME, SOA, and supported CAA records in one place.

02

See hosting endpoints

Identify IPv4 and IPv6 addresses returned for the domain.

03

Review mail routing

Inspect MX hosts and priorities when diagnosing email delivery configuration.

04

Check TTL values

See resolver TTL values that influence how long DNS answers can remain cached.

Useful answers

Questions about DNS Lookup

Practical details about input, output, privacy, limits, and the best way to use this tool.

01 What is a DNS lookup?

A DNS lookup queries the Domain Name System for records associated with a hostname, such as IP addresses, mail servers, nameservers, or TXT values.

02 What is an A record?

An A record maps a hostname to an IPv4 address. AAAA records perform the equivalent role for IPv6.

03 What is an MX record?

An MX record identifies a mail server for a domain. Lower preference values normally indicate higher priority.

04 Why can DNS results differ between tools?

Recursive resolvers cache records, geographic DNS can return different answers, and DNS changes propagate according to TTL and provider behavior.

05 Does DNS Lookup show the authoritative source directly?

The current Trexmi lookup uses the DNS resolver available to the server. It is useful for public resolution checks but is not a full iterative authoritative trace.

Learn HTTP & Network Debugging

Read the HTTP Headers Guide

Connect DNS, redirects, HTTP headers, requests, responses, caching, security, and practical web diagnostics.

  • Requests and response headers
  • Redirect and cache diagnostics
  • Security and API debugging
Read guide Practical explanations and examples

How DNS Lookup works

The DNS Lookup tool accepts a domain name and asks the DNS resolver configured for the Trexmi server to return selected records. DNS answers are structured by record type. The same domain may publish several A addresses, multiple MX servers, many TXT values, and several authoritative nameservers.

Because recursive resolvers cache answers, a DNS Lookup represents what the resolver currently sees. During migrations, two users can briefly see different answers if their resolvers cached different versions before a change. TTL values help explain how long an answer may remain cached.

Common DNS record types

A maps a hostname to IPv4. AAAA maps to IPv6. MX identifies mail servers and priority. NS identifies nameservers. CNAME aliases one hostname to another. TXT carries text policies and verification tokens. SOA describes important zone metadata. CAA can restrict which certificate authorities may issue certificates for a domain.

When a website moves to another server, verify the final hostname with DNS Lookup and then use the Redirect Chain Checker to confirm that old public URLs reach the intended HTTPS destination. If you are unsure which hostname was extracted from a complex URL, inspect it first with the URL Parser.

Troubleshooting DNS changes

Start with the exact hostname that fails. Compare A and AAAA addresses with the expected hosting provider. Review CNAME records for aliases, NS records after nameserver migrations, and MX records when email delivery changes unexpectedly. TXT records are often important for SPF, DKIM selectors, site verification, and service ownership checks.

A DNS record can be syntactically valid but operationally wrong. Old IP addresses may still answer, an MX record can target a retired mail platform, or a CNAME can lead to a hostname that no longer resolves. DNS Lookup gives you the returned records; the next step is comparing them with the intended architecture.

DNS security considerations

Public DNS data is designed to be discoverable. Do not put passwords, private API credentials, or secrets into TXT records merely because they are convenient. Verification tokens should be scoped for their intended service and removed when they are no longer required.

DNSSEC adds cryptographic validation to DNS data, but checking DNSSEC chains requires specialized validation beyond a basic record lookup. CAA can complement certificate management by limiting approved certificate authorities, although it does not replace TLS certificate monitoring.

Use WHOIS Lookup for public domain registration and registry data, URL Parser for URL components, HTTP Status Code Lookup for response meanings, and Redirect Chain Checker to inspect the HTTP route after DNS resolution succeeds.

Authoritative DNS references

For protocol and delegation reference material, see the IANA Root Zone Management documentation and the ICANN DNS overview. These are external DoFollow references that provide additional context for DNS delegation and the Domain Name System.

DNS Lookup summary

A reliable DNS check begins with the exact hostname and the record type relevant to the problem. Review A and AAAA for web endpoints, MX for mail, NS for delegation, TXT for policies, and CNAME for aliases. Use TTL values as context during changes and always compare returned data with the configuration you intended to publish.