checkip.com — DNS network test and history

Compare DNS records, resolvers and response times across locations.

Time 4 ms0 NOERROR●

; <<>> DiG 9.16.50-Debian <<>> -t A checkip.com -p 53 -4 +timeout=5 +tries=2 +nofail +nocookie +nosplit +nsid
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48712
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;checkip.com.			IN	A

;; ANSWER SECTION:
checkip.com.		300	IN	A	172.67.150.14
checkip.com.		300	IN	A	104.21.63.202

;; Query time: 4 msec
;; SERVER: x.x.x.x#53(x.x.x.x)
;; WHEN: Tue Sep 29 18:45:16 UTC 2026
;; MSG SIZE  rcvd: 72

Recent queries

Latest 20 per type

Compare round-trip latency and packet loss from different locations.

Open PING

History opens saved results. Select “Run again” to start a new test.

Inspect route paths, hop addresses and response times from different locations.

Open Traceroute

History opens saved results. Select “Run again” to start a new test.

Compare DNS records, resolvers and response times across locations.

Open DNS

History opens saved results. Select “Run again” to start a new test.

Combine route tracing with repeated probes to inspect hop latency and loss. Intermediate hop rate limiting does not establish destination packet loss.

Open MTR

History opens saved results. Select “Run again” to start a new test.

Inspect HTTP status, response headers and request timings from different locations.

Open HTTP

History opens saved results. Select “Run again” to start a new test.

checkip.com — DNS network test and history

Saved measurement results

Recent queries