Issue
Sign In
StepCodex FeaturedStepCodex Reviews
Notion Docs

Query domain DNS records. Free online tool, no login, no sign-up.

LocalPersonal data security

Loading Tool Engine

Usage Guide & Tech FAQ

Usage Guide

  1. Enter a domain and select record type (A/AAAA/CNAME/MX/TXT...).
  2. Run the query to view results and TTL.
  3. Compare against your DNS settings to debug reachability issues.
  4. Export findings if you need further team analysis.
  5. Separate authoritative lag vs resolver cache by trying public DNS and `dig +trace`.
  6. Avoid mixing CNAME with other records on the same owner name—many resolvers reject it.
  7. TXT for SPF/DKIM must follow RFC concatenation rules or verification fails.
  8. For IDN, compare punycode forms to avoid visual spoofing vs resolver reality.
  9. CDN troubleshooting should follow the CNAME target, not only the final A record.
  10. Record change timestamps and TTL to estimate global propagation windows.
  11. Read the title and description first to confirm this utility matches your task (avoid using the wrong tool and misinterpreting output).
  12. Paste or type input in the editor; if a sample/template is provided, load it first to learn the expected output shape.

Related Tech Knowledge

  • DNS resolution depends on resolvers and authoritative records.
  • TTL controls cache duration and affects update speed.
  • Different record types represent different meanings.
  • Network restrictions may return incomplete results.
  • DoH/DoT vs UDP/53 may take different paths and show different ECS behavior.
  • NXDOMAIN negative caching has TTL—short TTL churn can look like flaky resolution.
  • Browser DoH may differ from OS resolver—state clearly which layer you tested.
  • DNSSEC failures often surface as SERVFAIL until DS/DNSKEY chains are fixed.
  • Third-party DoH APIs may rate-limit or vary by egress region.
  • Core parsing and computation run in your browser; by default your raw business payload is not persisted to this site’s servers (see on-page privacy notes).
  • The pipeline is typically: read input → parse (lexical/syntactic/structured) → transform → render; failures aim to be diagnosable.
  • Assume UTF-8; mixing legacy encodings may look like “mojibake”—normalize in your editor before pasting.