TToolbox
DNS

DNS Lookup

Query A, MX, TXT and other records

About this tool

The Domain Name System (DNS) is the global routing phonebook of the Internet, translating human-friendly domain names into machine-routable IPv4/IPv6 addresses and mail server destinations within milliseconds. During website deployment, SSL certificate issuance, CDN onboarding, and DNS propagation auditing, querying records accurately is a vital workflow. This tool queries authoritative global DNS over HTTPS (DoH) nodes for tamper-proof resolution.

How to Use This Tool (Step-by-Step)

1

Enter Target Domain Name

Type your naked domain or subdomain into the search box. The tool automatically sanitizes any accidental `https://` prefixes.

2

Select DNS Record Type

Pick desired record types to retrieve: A (IPv4), AAAA (IPv6), CNAME (Aliases), MX (Mail), TXT (Domain Verification), or NS/SOA.

3

Inspect Results & TTL Lifespans

Resolves records via authoritative global anycast nodes (Cloudflare/Google DoH), displaying target IP records and TTL cache expiries.

Full Resource Record Coverage

Comprehensive coverage of A, AAAA, CNAME, MX, TXT, NS, SOA, CAA, and SRV records for server deployments and mail setups.

Encrypted DoH Anti-Pollution

Queries global root resolvers over encrypted HTTPS (DoH), bypassing ISP caching delays and DNS poisoning for true global results.

Sub-Second Live Resolution

Fetches multiple record types concurrently with exact TTL cache durations, helping you evaluate global propagation timelines.

DNS Operations & Migration Best Practices

  • •Lower TTLs 24 hours before migration: If your TTL is 86400s (1 day), drop it to 300s (5m) the day before migrating. This ensures new IPs propagate globally in 5 minutes.
  • •Configure SPF and DMARC TXT records: Sending corporate mail without SPF/DMARC TXT records causes Gmail and Outlook spam filters to flag or reject your messages.
  • •CNAME exclusivity rule: RFC 1034 specifies that if a CNAME exists for a node, no other data records (MX, A, TXT) may coexist at that same node.

Code & Transformation Examples

Standard DNS Record Configuration Benchmark

Record Types
• A 记录     : 域名指向具体的 IPv4 地址 (如 104.21.55.1)
• AAAA 记录  : 域名指向新一代 IPv6 地址 (如 2606:4700::...)
• CNAME 记录 : 别名指向另一个域名 (如指向 cdn.cloudflare.net)
• MX 记录    : 指定收发邮件的邮局服务器 (优先级数值越小越高)
• TXT 记录   : 纯文本配置,用于 SPF 防钓鱼、Google 站长所有权验证
TTL Meaning
TTL (Time to Live,单位:秒) 决定了全球各级递归缓存服务器保存该解析结果的最长有效时间(如 300 秒代表 5 分钟后必须重新向权威服务器同步)。

* Standard RFCs prohibit CNAME records on root apex domains unless DNS providers support CNAME Flattening.

Terminal DNS Command Line Cheat Sheet

dig Command
dig example.com A +short
dig example.com MX
dig @1.1.1.1 example.com ANY
nslookup Command
nslookup -type=A example.com
nslookup -type=TXT example.com 8.8.8.8

* Targeting public resolvers (1.1.1.1, 8.8.8.8) bypasses local router cache corruption.

Frequently Asked Questions

Q: Why do some users see the new site while others see the old?

A: This is standard DNS propagation latency. Thousands of ISPs across countries cache records locally until their countdown TTL expires before querying your new nameserver.

Q: What is the difference between Recursive and Authoritative DNS?

A: Authoritative DNS (Cloudflare, AWS Route53) holds the definitive master records. Recursive resolvers (1.1.1.1, Google 8.8.8.8) query authoritative servers on behalf of clients.

Q: Why are web tool results more up-to-date than my local command prompt?

A: Local machines cache results in Windows memory and home routers. Our tool connects directly to global edge anycast resolvers over encrypted DoH, bypassing stale ISP caches.

Related Tools

All processing happens locally in your browser. Your data is never uploaded to a server.
/