IP Tools
Local test ready · production pending

DNS Lookup

Create one bounded network job and inspect only validated worker evidence.

Method:
Same-origin API → isolated network worker; explicit create, refresh and cancel only
Status:
idle

Input

Result

Ready

No job has been created. Complete the bounded form to begin.

One target and one bounded operation per job. No URL fetch, port range, custom resolver or browser-side probe is available.

Tool guide

Clear input, result, and evidence boundaries

Look up one selected DNS record type for a domain through the configured resolver.

01

Input and method

One domain and one A, AAAA, CNAME, MX, TXT, or NS record type.

02

Reading the result

Record values, TTL, priority or weight where applicable, resolver, status, and query time are shown.

03

Boundary and privacy

No-record, NXDOMAIN, SERVFAIL, and timeout remain distinct; PTR belongs to Reverse DNS and resolver exposure belongs to DNS Leak Test.

FAQ

Frequently asked questions

What does DNS Lookup check?

Look up one selected DNS record type for a domain through the configured resolver.

What input does DNS Lookup accept?

One domain and one A, AAAA, CNAME, MX, TXT, or NS record type.

How should I interpret DNS Lookup results?

Record values, TTL, priority or weight where applicable, resolver, status, and query time are shown.

What can DNS Lookup not prove?

No-record, NXDOMAIN, SERVFAIL, and timeout remain distinct; PTR belongs to Reverse DNS and resolver exposure belongs to DNS Leak Test.

How does DNS Lookup handle input and results?

Input is used only for this explicit check. No-record, NXDOMAIN, SERVFAIL, and timeout remain distinct; PTR belongs to Reverse DNS and resolver exposure belongs to DNS Leak Test.

When should I run DNS Lookup again?

Run it again after the relevant network, address, browser environment, or target changes. Record values, TTL, priority or weight where applicable, resolver, status, and query time are shown.

Continue checking