Skip to main content
RECURSIVE DOH RECORD LOOKUP & DIG INSPECTOR
🔍

DNS Record Lookup

Query comprehensive DNS records (A, AAAA, MX, TXT, SPF, DMARC, NS, SOA, CAA) via recursive DNS-over-HTTPS (DoH) with visual breakdown and dig format output.

✓SPF, DMARC, and CAA policy parsing with syntax validation
✓Dig-format terminal export, Visual card mode, and raw JSON
Lookup StatusReady
Target Host
shrtx.in
Query Time
0 ms
DoH Resolver:cloudflare DoH

DNS Record Query Console

0 answers resolved
No DNS records found for this domain.

Authoritative DNS Record Analysis and Diagnostics

The DNS Record Lookup utility queries and parses comprehensive Domain Name System records for any fully qualified domain name. By utilizing secure DNS-over-HTTPS (DoH) transport, the lookup retrieves resource records directly from recursive resolvers, parsing complex security and routing configurations into structured, readable diagnostics.

Modern domain configurations extend far beyond simple IP address mapping. Today's DNS ecosystem enforces critical security, authentication, and routing policies via specialized record types. This tool incorporates specialized semantic parsers that deconstruct SPF (Sender Policy Framework) mechanisms, DMARC (Domain-based Message Authentication) policy rules, and CAA (Certification Authority Authorization) restrictions to assist email and infrastructure engineers.

To bridge web convenience with sysadmin workflows, the tool generates terminal-formatted dig (Domain Information Groper) command outputs alongside structured UI tables. Users can inspect query execution times, TTL countdown counters, raw response status codes (RCODE), and authoritative nameserver responses directly in their browser without installing command-line utilities.

Core Tool Capabilities

  • Comprehensive RR Querying: Retrieves standard record types including A (IPv4), AAAA (IPv6), MX (Mail), TXT, CNAME, NS, SOA, CAA, PTR, and SRV.
  • Specialized SPF Record Parsing: Deconstructs TXT SPF records to display authorized sending mechanisms, IP prefixes, includes, and default fail policies.
  • DMARC Policy Extraction: Evaluates DMARC records to identify enforcement levels (none, quarantine, reject), percentage rules, and reporting mailboxes.
  • CAA Policy Validation: Parses Certification Authority Authorization tags (issue, issuewild, iodef) to inspect permitted SSL/TLS certificate issuers.
  • Simulated Terminal Dig Output: Generates syntactically accurate dig command output blocks with query headers, flags, and timing statistics.
  • Browser-Direct DoH Transport: Dispatches queries using RFC 8484 DNS-over-HTTPS directly to secure resolvers without intermediate server proxies.

Local Browser Privacy

Your files are processed locally on your device. Files are not uploaded, transmitted, or stored on remote servers.

Once the page has loaded, you can disconnect your network connection and continue using this tool offline.

Target Use Cases

  • • Email Deliverability and Anti-Spoofing Audits
  • • Web Infrastructure and DNS Management
  • • SSL/TLS Certificate Troubleshooting
  • • Quick Terminal Dig Access

Technical Specifications & Platform Limits

Query Types Supported
ALL, A, AAAA, MX, TXT, NS, CNAME, SOA, CAA

Full spectrum of standard internet resource record types.

Parsing Engines
SPF, DMARC, and CAA parsers

Specialized semantic parsers for domain security and mail authentication.

Terminal Compatibility
Standard BIND dig syntax

Generates terminal-ready dig query output blocks with flags.

Protocol Standard
RFC 8484 (DoH) and RFC 1035

Encrypted DNS-over-HTTPS protocol standard.

Execution Boundary
Browser-direct resolver queries

Queries originate from client browser without server proxy hops.

Step-by-Step Workflow

1

Enter Target Domain

Type the domain or hostname you wish to inspect into the search input. Clean domain formatting is handled automatically.

2

Choose Record Query Type

Select an individual record type such as MX, TXT, or CAA, or select ALL to query all standard record sets. Specific query filters reduce noise.

3

Execute Lookup

Click the Lookup DNS button to dispatch the DNS-over-HTTPS query and fetch the resource records. Raw answers and TTLs load in milliseconds.

4

Inspect Parsed Policies and Dig Output

Examine the parsed policy summaries in the visual cards or switch to the terminal view to copy the raw dig text. Verify all records match expectations.

Practical Real-World Use Cases

Email Deliverability and Anti-Spoofing Audits

Mail server administrators inspecting SPF mechanisms and DMARC enforcement policies to prevent domain spoofing and phishing attacks.

Web Infrastructure and DNS Management

Systems engineers verifying that new hostnames, CNAME aliases, and round-robin A records are correctly published and responding.

SSL/TLS Certificate Troubleshooting

Security engineers validating that CAA records allow specific certificate authorities like Let's Encrypt or DigiCert to issue certificates.

Quick Terminal Dig Access

Developers working on Chromebooks, tablets, or restricted environments who need rapid dig terminal output without shell access.

Frequently Asked Questions

What is DNS-over-HTTPS (DoH) and why is it used for lookups?
DNS-over-HTTPS (DoH) is an internet security standard (RFC 8484) that encrypts DNS queries using the HTTPS protocol. Using DoH allows web browsers to perform secure, encrypted DNS lookups directly against trusted public resolvers, preventing local network eavesdropping, DNS hijacking, and ISP content tampering.
How does the tool parse SPF and DMARC records?
The tool searches for specific TXT records starting with v=spf1 and v=DMARC1. It then breaks down the directives into structured components, identifying authorized mail servers, IP ranges, include directives, fail policies, and DMARC enforcement settings like quarantine or reject.
What does the TTL number in DNS records mean?
TTL stands for Time-to-Live, measured in seconds. It instructs recursive resolvers and client computers how long they may cache the record before they must discard it and request fresh information from the authoritative nameservers. Lower TTLs allow faster updates during migrations, while higher TTLs reduce DNS query traffic.
Why do I see an NXDOMAIN or SERVFAIL response?
An NXDOMAIN (Non-Existent Domain) response means the authoritative nameserver confirmed that the queried domain name does not exist. A SERVFAIL (Server Failure) response indicates that the resolver could not obtain an authoritative answer, often caused by misconfigured nameservers, DNSSEC validation failures, or network timeouts.
Is my lookup history or domain query recorded on your server?
No. All queries are sent directly from your client browser to the chosen public DoH resolver. SHRTX does not proxy your requests, does not record the domains you look up, and maintains zero server logs of your DNS queries.

Share this tool

Help others discover this utility. No login or registration required.