What the records are
A/AAAA map names to IP addresses, MX describes mail routing, NS identifies authoritative name servers, CNAME aliases a name and TXT carries arbitrary published text.
TEST / DNS0BPS / MODULE
DNS LOOKUP
Inspect public A, AAAA, MX, NS, CNAME and TXT records — individually or as a combined summary — using the server DNS resolver.
ADVERTISEMENT
ADVERTISEMENT
RESULT / EXPLAINED
Read DNS records without confusing one resolver with the whole internet.
The result is the record set returned through the server resolver at query time. It answers what this resolver can currently see.
Empty is meaningful
No returned records can mean the requested type is not published, the name does not exist, or the resolver cannot currently obtain an answer. It is not automatically proof of an outage.
Not propagation testing
A single server resolver cannot prove worldwide DNS propagation. Caches, TTLs and resolver paths can make other locations see a different answer temporarily.
Verify changes
For a DNS change, compare authoritative DNS configuration and multiple independent resolvers or regions before concluding propagation is complete.
0BPS SHOWS MEASURED OR CALCULATED FACTS SEPARATELY FROM INTERPRETATION. WHERE A RESULT IS ADVISORY, ESTIMATED OR DESTINATION-SPECIFIC, THE LIMIT IS STATED IN THE TOOL.
REFERENCE / FAQ
COMMON QUESTIONS
What does a DNS lookup show?
A DNS lookup asks the server resolver for public DNS records such as A, AAAA, MX, NS, CNAME or TXT. Results reflect the resolver and DNS state visible at the time of the query.
Why can DNS results differ between tools?
Resolvers can use different caches, geographic routing and DNS providers. Record changes can also take time to propagate according to TTL and resolver behavior.
Does 0bps scan the target server?
No. This module performs DNS record resolution only. It does not connect to arbitrary service ports or attempt to bypass access controls.
The module requests public DNS records through the server resolver. It does not scan ports or fetch arbitrary web pages.
Resolver cache, TTL, geography and provider behavior can make answers differ between locations or change over time.
PRACTICAL / EXAMPLES
PUT THE NUMBER IN CONTEXT.
Short examples using the same units and assumptions as this module.
Looking up example.com with type A returns IPv4 addresses published in DNS.
An MX lookup shows mail-routing targets and their priorities when the domain publishes them.