Skip to main content

nslookup

Inspect name resolution the way nslookup presents it.

Instructions, guides and related tools

Enter a hostname (www.example.jp, 例え.jp or its xn-- form). To reverse a public IP, select PTR and enter the IP (e.g. 1.1.1.1 or 2606:4700:4700::1111). Do not enter a URL or port.

Recent DNS queries Saving off

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.

Result

ok

Geo: — (restricted)

xn--wgv71a119e.jp

Checks

CheckVerdictDetail
nslookupok
Query type: A
Server:  doh-google
Name:    xn--wgv71a119e.jp
Address:  117.104.133.183

Query type: AAAA
Server:  doh-google
Name:    xn--wgv71a119e.jp
Address:  2001:218:3001:7::110

Query type: MX
Server:  doh-google
Name:    xn--wgv71a119e.jp
MX:  40 off-mx42.tyo.jprs.co.jp.
MX:  20 off-mx42.osa.jprs.co.jp.
MX:  30 off-mx41.tyo.jprs.co.jp.
MX:  10 off-mx41.osa.jprs.co.jp.

Query type: TXT
Server:  doh-google
Name:    xn--wgv71a119e.jp
*** No records

Query type: NS
Server:  doh-google
Name:    xn--wgv71a119e.jp
NS:  ns4.jprs.co.jp.
NS:  ns1.jprs.co.jp.
NS:  ns3.jprs.co.jp.
NS:  ns2.jprs.co.jp.

Query type: CNAME
Server:  doh-google
Name:    xn--wgv71a119e.jp
*** No records
dns_detailsok
;; RESOLVER: doh-google
;; DoH request elapsed: 197 ms (includes HTTPS transport)
;; Finished at: 2026-10-12T05:49:38.365Z
;; status: NOERROR (0)
;; flags: TC=false; RD=true; RA=true; AD=false; CD=false
;; QUERY SENT:
;xn--wgv71a119e.jp. IN A
;; QUESTION SECTION:
;xn--wgv71a119e.jp. IN A

;; ANSWER SECTION:
xn--wgv71a119e.jp. 300 IN A 117.104.133.183

;; AUTHORITY SECTION:
;; Not returned by resolver

;; ADDITIONAL SECTION:
;; Not returned by resolver

;; RESOLVER: doh-google
;; DoH request elapsed: 173 ms (includes HTTPS transport)
;; Finished at: 2026-10-12T05:49:38.538Z
;; status: NOERROR (0)
;; flags: TC=false; RD=true; RA=true; AD=false; CD=false
;; QUERY SENT:
;xn--wgv71a119e.jp. IN AAAA
;; QUESTION SECTION:
;xn--wgv71a119e.jp. IN AAAA

;; ANSWER SECTION:
xn--wgv71a119e.jp. 300 IN AAAA 2001:218:3001:7::110

;; AUTHORITY SECTION:
;; Not returned by resolver

;; ADDITIONAL SECTION:
;; Not returned by resolver

;; RESOLVER: doh-google
;; DoH request elapsed: 164 ms (includes HTTPS transport)
;; Finished at: 2026-10-12T05:49:38.702Z
;; status: NOERROR (0)
;; flags: TC=false; RD=true; RA=true; AD=false; CD=false
;; QUERY SENT:
;xn--wgv71a119e.jp. IN MX
;; QUESTION SECTION:
;xn--wgv71a119e.jp. IN MX

;; ANSWER SECTION:
xn--wgv71a119e.jp. 300 IN MX 40 off-mx42.tyo.jprs.co.jp.
xn--wgv71a119e.jp. 300 IN MX 20 off-mx42.osa.jprs.co.jp.
xn--wgv71a119e.jp. 300 IN MX 30 off-mx41.tyo.jprs.co.jp.
xn--wgv71a119e.jp. 300 IN MX 10 off-mx41.osa.jprs.co.jp.

;; AUTHORITY SECTION:
;; Not returned by resolver

;; ADDITIONAL SECTION:
;; Not returned by resolver

;; RESOLVER: doh-google
;; DoH request elapsed: 316 ms (includes HTTPS transport)
;; Finished at: 2026-10-12T05:49:39.018Z
;; status: NOERROR (0)
;; flags: TC=false; RD=true; RA=true; AD=false; CD=false
;; QUERY SENT:
;xn--wgv71a119e.jp. IN TXT
;; QUESTION SECTION:
;xn--wgv71a119e.jp. IN TXT

;; ANSWER SECTION:
;; Not returned by resolver

;; AUTHORITY SECTION:
xn--wgv71a119e.jp. 1800 IN SOA ns1.jprs.co.jp. postmaster.jprs.jp. 1791171004 3600 900 1814400 86400

;; ADDITIONAL SECTION:
;; Not returned by resolver

;; RESOLVER: doh-google
;; DoH request elapsed: 178 ms (includes HTTPS transport)
;; Finished at: 2026-10-12T05:49:39.196Z
;; status: NOERROR (0)
;; flags: TC=false; RD=true; RA=true; AD=false; CD=false
;; QUERY SENT:
;xn--wgv71a119e.jp. IN NS
;; QUESTION SECTION:
;xn--wgv71a119e.jp. IN NS

;; ANSWER SECTION:
xn--wgv71a119e.jp. 10800 IN NS ns4.jprs.co.jp.
xn--wgv71a119e.jp. 10800 IN NS ns1.jprs.co.jp.
xn--wgv71a119e.jp. 10800 IN NS ns3.jprs.co.jp.
xn--wgv71a119e.jp. 10800 IN NS ns2.jprs.co.jp.

;; AUTHORITY SECTION:
;; Not returned by resolver

;; ADDITIONAL SECTION:
;; Not returned by resolver

;; RESOLVER: doh-google
;; DoH request elapsed: 174 ms (includes HTTPS transport)
;; Finished at: 2026-10-12T05:49:39.370Z
;; status: NOERROR (0)
;; flags: TC=false; RD=true; RA=true; AD=false; CD=false
;; QUERY SENT:
;xn--wgv71a119e.jp. IN CNAME
;; QUESTION SECTION:
;xn--wgv71a119e.jp. IN CNAME

;; ANSWER SECTION:
;; Not returned by resolver

;; AUTHORITY SECTION:
xn--wgv71a119e.jp. 1800 IN SOA ns1.jprs.co.jp. postmaster.jprs.jp. 1791171004 3600 900 1814400 86400

;; 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--wgv71a119e.jp A
nslookup -type=A xn--wgv71a119e.jp

When expected records are missing

  1. Check the exact name and type. A www host and the zone apex are different names; reverse DNS uses PTR.
  2. Check the delegated name servers with NS, then inspect records in the corresponding control panel. The SOA serial helps compare zone revisions.
  3. After a change, caches may retain data for the previous TTL. TTL does not guarantee a worldwide completion time.
  4. 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.

Share This Page

Need help? Find your solution here.