Optional. Save up to 20 host/IP and record-type pairs on this site's browser storage. Entries older than 30 days are removed when you next open a DNS tool. DNS answers are not saved in this history. Other people using this browser may see it. Turning saving off removes this history; it does not erase browser navigation history or diagnostic service records.
nslookup
Inspect name resolution the way nslookup presents it.
Instructions, guides and related tools
Recent DNS queries Saving off
Result
ok
Checks
| Check | Verdict | Detail |
|---|---|---|
| nslookup | ok | Query type: A Server: doh-google Name: xn--bcher-kva.de Address: 104.21.33.153 Address: 172.67.146.137 Query type: AAAA Server: doh-google Name: xn--bcher-kva.de Address: 2606:4700:3036::ac43:9289 Address: 2606:4700:3033::6815:2199 Query type: MX Server: doh-google Name: xn--bcher-kva.de *** No records Query type: TXT Server: doh-google Name: xn--bcher-kva.de TXT: v=spf1 -all TXT: v=DMARC1; p=quarantine; Query type: NS Server: doh-google Name: xn--bcher-kva.de NS: sasha.ns.cloudflare.com. NS: ken.ns.cloudflare.com. Query type: CNAME Server: doh-google Name: xn--bcher-kva.de *** No records |
| dns_details | ok | ;; RESOLVER: doh-google ;; DoH request elapsed: 44 ms (includes HTTPS transport) ;; Finished at: 2026-10-12T05:48:52.926Z ;; status: NOERROR (0) ;; flags: TC=false; RD=true; RA=true; AD=false; CD=false ;; QUERY SENT: ;xn--bcher-kva.de. IN A ;; QUESTION SECTION: ;xn--bcher-kva.de. IN A ;; ANSWER SECTION: xn--bcher-kva.de. 300 IN A 104.21.33.153 xn--bcher-kva.de. 300 IN A 172.67.146.137 ;; AUTHORITY SECTION: ;; Not returned by resolver ;; ADDITIONAL SECTION: ;; Not returned by resolver ;; RESOLVER: doh-google ;; DoH request elapsed: 34 ms (includes HTTPS transport) ;; Finished at: 2026-10-12T05:48:52.960Z ;; status: NOERROR (0) ;; flags: TC=false; RD=true; RA=true; AD=false; CD=false ;; QUERY SENT: ;xn--bcher-kva.de. IN AAAA ;; QUESTION SECTION: ;xn--bcher-kva.de. IN AAAA ;; ANSWER SECTION: xn--bcher-kva.de. 300 IN AAAA 2606:4700:3036::ac43:9289 xn--bcher-kva.de. 300 IN AAAA 2606:4700:3033::6815:2199 ;; AUTHORITY SECTION: ;; Not returned by resolver ;; ADDITIONAL SECTION: ;; Not returned by resolver ;; RESOLVER: doh-google ;; DoH request elapsed: 46 ms (includes HTTPS transport) ;; Finished at: 2026-10-12T05:48:53.006Z ;; status: NOERROR (0) ;; flags: TC=false; RD=true; RA=true; AD=false; CD=false ;; QUERY SENT: ;xn--bcher-kva.de. IN MX ;; QUESTION SECTION: ;xn--bcher-kva.de. IN MX ;; ANSWER SECTION: ;; Not returned by resolver ;; AUTHORITY SECTION: xn--bcher-kva.de. 1800 IN SOA ken.ns.cloudflare.com. dns.cloudflare.com. 2415556846 10000 2400 604800 1800 ;; ADDITIONAL SECTION: ;; Not returned by resolver ;; RESOLVER: doh-google ;; DoH request elapsed: 45 ms (includes HTTPS transport) ;; Finished at: 2026-10-12T05:48:53.051Z ;; status: NOERROR (0) ;; flags: TC=false; RD=true; RA=true; AD=false; CD=false ;; QUERY SENT: ;xn--bcher-kva.de. IN TXT ;; QUESTION SECTION: ;xn--bcher-kva.de. IN TXT ;; ANSWER SECTION: xn--bcher-kva.de. 300 IN TXT v=spf1 -all xn--bcher-kva.de. 300 IN TXT v=DMARC1; p=quarantine; ;; AUTHORITY SECTION: ;; Not returned by resolver ;; ADDITIONAL SECTION: ;; Not returned by resolver ;; RESOLVER: doh-google ;; DoH request elapsed: 30 ms (includes HTTPS transport) ;; Finished at: 2026-10-12T05:48:53.081Z ;; status: NOERROR (0) ;; flags: TC=false; RD=true; RA=true; AD=false; CD=false ;; QUERY SENT: ;xn--bcher-kva.de. IN NS ;; QUESTION SECTION: ;xn--bcher-kva.de. IN NS ;; ANSWER SECTION: xn--bcher-kva.de. 21600 IN NS sasha.ns.cloudflare.com. xn--bcher-kva.de. 21600 IN NS ken.ns.cloudflare.com. ;; AUTHORITY SECTION: ;; Not returned by resolver ;; ADDITIONAL SECTION: ;; Not returned by resolver ;; RESOLVER: doh-google ;; DoH request elapsed: 32 ms (includes HTTPS transport) ;; Finished at: 2026-10-12T05:48:53.113Z ;; status: NOERROR (0) ;; flags: TC=false; RD=true; RA=true; AD=false; CD=false ;; QUERY SENT: ;xn--bcher-kva.de. IN CNAME ;; QUESTION SECTION: ;xn--bcher-kva.de. IN CNAME ;; ANSWER SECTION: ;; Not returned by resolver ;; AUTHORITY SECTION: xn--bcher-kva.de. 1800 IN SOA ken.ns.cloudflare.com. dns.cloudflare.com. 2415556846 10000 2400 604800 1800 ;; ADDITIONAL SECTION: ;; Not returned by resolver |
Sources
doh-google
Related checks and services
Explore a domain for your next website or business email. Check available names and registration terms on the domain search page.
What this tool does
Public DNS answers arranged like nslookup Server / Name / Address. There is no interactive mode and no arbitrary server pin.
How to read the result
Server is the DoH source that answered. Name is the host that was asked. Address lists A / AAAA; other types follow with their type label.
Glossary
- nslookup
- A classic presentation of name resolution as Server / Name / Address.
- A
- An IPv4 address record.
- AAAA
- An IPv6 address record.
- TTL
- How long that answer may be reused. This layout may omit the number on a line.
FAQ
- Is this the same as nslookup on my computer?
- The layout is similar, but the query goes to public DoH. Interactive mode and set type=ANY are not reproduced.
- What is the Server line?
- The identifier of the DNS-over-HTTPS source that was used.
- What if the result is empty?
- Either the name is missing (NXDOMAIN) or that type is absent (NODATA). See the resolve row.
- Where is the query sent?
- Public DNS over HTTPS. The host name is the question.
- Is personal data sent?
- Only the host name you enter. No account or contact data is used.
- How do I find a hostname from an IP?
- Select PTR and enter a public IPv4 or IPv6 address. We construct its reverse name and query public DNS. Private IPs are excluded. Missing PTR records do not necessarily indicate a web connection problem.
Updated:
Check from your own device
Use dig on macOS or Linux, or nslookup on Windows. Each command queries one record type. Your device uses its own DNS settings and cache, so its results may differ from this page.
dig xn--bcher-kva.de A
nslookup -type=A xn--bcher-kva.de
When expected records are missing
- Check the exact name and type. A www host and the zone apex are different names; reverse DNS uses PTR.
- Check the delegated name servers with NS, then inspect records in the corresponding control panel. The SOA serial helps compare zone revisions.
- After a change, caches may retain data for the previous TTL. TTL does not guarantee a worldwide completion time.
- SERVFAIL and transport failures do not mean a record is absent. Investigate delegation, DNSSEC and resolver availability.
Response details and sources
Details come from DNS-over-HTTPS JSON responses. Omitted sections and flags are marked as not reported. AD reports the resolver's DNSSEC validation; these are not direct connections from your browser to an authoritative DNS server.