A host name such as www.example.jp, 例え.jp, or an xn-- label. Do not add spaces or https://.

Which type should I select for an IP input?

Select PTR for reverse DNS. A and AAAA resolve a hostname to an IP; they do not take an IP as their input.

How do NXDOMAIN and NODATA differ?

NXDOMAIN means the name is absent. NODATA means the name exists but not that record type.

Where does the query go?

Public DNS over HTTPS (Google, then Cloudflare on failure). The host name is part of the query.

Can this differ from dig on my machine?

Yes, while TTL is still valid, cache and resolver path can differ. Confirm the authority for a final check.

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.

Check DNS records

Enter a host name to inspect its published DNS records.

Instructions, guides and related tools

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.

Saved query

Result

Geo: — (restricted)

xn--wgv71a119e.jp

Checks

Check	Verdict	Detail
records	ok	A 300 117.104.133.183 AAAA 300 2001:218:3001:7::110 MX 300 10 off-mx41.osa.jprs.co.jp. MX 300 20 off-mx42.osa.jprs.co.jp. MX 300 30 off-mx41.tyo.jprs.co.jp. MX 300 40 off-mx42.tyo.jprs.co.jp. NS 10800 ns1.jprs.co.jp. NS 10800 ns3.jprs.co.jp. NS 10800 ns2.jprs.co.jp. NS 10800 ns4.jprs.co.jp.
rcode	ok	NOERROR
dns_details	ok	;; RESOLVER: doh-google ;; DoH request elapsed: 170 ms (includes HTTPS transport) ;; Finished at: 2026-10-12T05:48:52.344Z ;; 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: 321 ms (includes HTTPS transport) ;; Finished at: 2026-10-12T05:48:52.665Z ;; 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: 166 ms (includes HTTPS transport) ;; Finished at: 2026-10-12T05:48:52.831Z ;; 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 10 off-mx41.osa.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 40 off-mx42.tyo.jprs.co.jp. ;; AUTHORITY SECTION: ;; Not returned by resolver ;; ADDITIONAL SECTION: ;; Not returned by resolver ;; RESOLVER: doh-google ;; DoH request elapsed: 172 ms (includes HTTPS transport) ;; Finished at: 2026-10-12T05:48:53.003Z ;; 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: 174 ms (includes HTTPS transport) ;; Finished at: 2026-10-12T05:48:53.177Z ;; 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 ns1.jprs.co.jp. xn--wgv71a119e.jp. 10800 IN NS ns3.jprs.co.jp. xn--wgv71a119e.jp. 10800 IN NS ns2.jprs.co.jp. xn--wgv71a119e.jp. 10800 IN NS ns4.jprs.co.jp. ;; AUTHORITY SECTION: ;; Not returned by resolver ;; ADDITIONAL SECTION: ;; Not returned by resolver ;; RESOLVER: doh-google ;; DoH request elapsed: 166 ms (includes HTTPS transport) ;; Finished at: 2026-10-12T05:48:53.343Z ;; 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

Check

Verdict

Detail

records

A 300 117.104.133.183
AAAA 300 2001:218:3001:7::110
MX 300 10 off-mx41.osa.jprs.co.jp.
MX 300 20 off-mx42.osa.jprs.co.jp.
MX 300 30 off-mx41.tyo.jprs.co.jp.
MX 300 40 off-mx42.tyo.jprs.co.jp.
NS 10800 ns1.jprs.co.jp.
NS 10800 ns3.jprs.co.jp.
NS 10800 ns2.jprs.co.jp.
NS 10800 ns4.jprs.co.jp.

rcode

NOERROR

dns_details

;; RESOLVER: doh-google
;; DoH request elapsed: 170 ms (includes HTTPS transport)
;; Finished at: 2026-10-12T05:48:52.344Z
;; 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: 321 ms (includes HTTPS transport)
;; Finished at: 2026-10-12T05:48:52.665Z
;; 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: 166 ms (includes HTTPS transport)
;; Finished at: 2026-10-12T05:48:52.831Z
;; 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 10 off-mx41.osa.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 40 off-mx42.tyo.jprs.co.jp.

;; AUTHORITY SECTION:
;; Not returned by resolver

;; ADDITIONAL SECTION:
;; Not returned by resolver

;; RESOLVER: doh-google
;; DoH request elapsed: 172 ms (includes HTTPS transport)
;; Finished at: 2026-10-12T05:48:53.003Z
;; 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: 174 ms (includes HTTPS transport)
;; Finished at: 2026-10-12T05:48:53.177Z
;; 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 ns1.jprs.co.jp.
xn--wgv71a119e.jp. 10800 IN NS ns3.jprs.co.jp.
xn--wgv71a119e.jp. 10800 IN NS ns2.jprs.co.jp.
xn--wgv71a119e.jp. 10800 IN NS ns4.jprs.co.jp.

;; AUTHORITY SECTION:
;; Not returned by resolver

;; ADDITIONAL SECTION:
;; Not returned by resolver

;; RESOLVER: doh-google
;; DoH request elapsed: 166 ms (includes HTTPS transport)
;; Finished at: 2026-10-12T05:48:53.343Z
;; 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.

Find a domain Create a One account

What this tool does

Inspect A, AAAA, NS, CNAME, MX, TXT, SOA, PTR and CAA in public DNS. SOA describes zone administration, PTR is reverse DNS, and CAA controls certificate issuance. The common six types can be queried together. This page does not query authorities directly or transfer zones.

How to read the result

Each row is type, TTL, and value. A & AAAA are addresses, MX is the mail exchanger, TXT is published text, NS is the delegated name server, and CNAME is an alias. TTL is how long that answer may be reused.

Glossary

DNS: A lookup that maps a host name to public records. This page uses DNS over HTTPS.
FQDN: A name written with every label, such as www.example.jp.
TTL: How many seconds that answer may be reused before asking again.
NXDOMAIN: A response meaning the name itself does not exist.
NODATA: A response meaning the name exists but has no record of the asked type.

FAQ

What should I enter?: A host name such as www.example.jp, 例え.jp, or an xn-- label. Do not add spaces or https://.
Which type should I select for an IP input?: Select PTR for reverse DNS. A and AAAA resolve a hostname to an IP; they do not take an IP as their input.
How do NXDOMAIN and NODATA differ?: NXDOMAIN means the name is absent. NODATA means the name exists but not that record type.
Where does the query go?: Public DNS over HTTPS (Google, then Cloudflare on failure). The host name is part of the query.
Can this differ from dig on my machine?: Yes, while TTL is still valid, cache and resolver path can differ. Confirm the authority for a final check.
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: 2026-09-16

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

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.