Run this tool instantly in your browser. No signup and no server-side processing.
Like this tool?
Install byteflow.tools for faster startup and offline tool access.
Install guideLike this tool?
Install byteflow.tools for faster startup and offline tool access.
Install guideRun live DNS-over-HTTPS lookups and inspect real resolver answers.
| Type | Name | Value | TTL |
|---|
Query DNS records to validate domain resolution, mail setup, and infrastructure changes during deployment and incident troubleshooting.
It resolves DNS record types such as A, AAAA, CNAME, MX, TXT, and NS for a given domain.
It helps verify propagation and detect misconfigured records quickly.
It supports network diagnostics when routing or certificate workflows depend on accurate DNS state.
Domain query
example.com (A, AAAA, NS)
Mail query
example.com (MX, TXT)
Subdomain query
api.example.com (CNAME/A)
Record result
A: 203.0.113.42 ; AAAA: 2001:db8::42
TTL info
TTL 300s observed on authoritative response
Ops note
Compare responses across resolvers when propagation appears inconsistent.
Old records still returned
Account for TTL and resolver cache propagation delays.
CNAME conflict with other records
Do not mix CNAME with incompatible record types at same label.
SPF TXT record invalid syntax
Validate SPF formatting and include chain limits.
Wrong nameserver delegation
Check parent zone NS records and registrar configuration.
DNS Lookup should be treated as a repeatable validation step before merge, release, and handoff.
How long does DNS propagation take?
It depends on TTL and resolver cache behavior, often minutes to hours.
Why do different tools show different answers?
Resolvers, geo-routing, and cache freshness can vary.
Can I test DNSSEC with this workflow?
You can inspect related records, but full DNSSEC validation may need dedicated checks.
Should I lower TTL before migrations?
Yes, lowering TTL in advance helps faster cutovers.