Hostname or IP
Type
Searching for 74.64.28.120.in-addr.arpa. PTR record at F.ROOT-SERVERS.NET. [192.5.5.241] ...took 1 ms
Searching for 74.64.28.120.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 190 ms
Searching for tinnie.arin.net. A record at F.ROOT-SERVERS.NET. [192.5.5.241] ...took 1 ms
Searching for tinnie.arin.net. A record at h.gtld-servers.net. [192.54.112.30] ...took 86 ms
Searching for tinnie.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 101 ms
Searching for 74.64.28.120.in-addr.arpa. PTR record at tinnie.arin.net. [199.212.0.53] ...took 93 ms
Searching for dns1.globenet.com.ph. A record at M.ROOT-SERVERS.NET. [202.12.27.33] ...took 143 ms
Searching for dns1.globenet.com.ph. A record at 1.ns.ph. [206.51.255.1] ...took 1 ms
Searching for dns1.globenet.com.ph. A record at g-net1.globe.com.ph. [203.127.225.11] ...took 217 ms
Searching for 74.64.28.120.in-addr.arpa. PTR record at dns1.globenet.com.ph. [203.177.255.10]
Query timed out (interrupted after 2,002 milliseconds)
Retrying...
Searching for 74.64.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 217 ms
Searching for 74.64.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 209 ms
REFUSED
Searching for 74.64.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 218 ms
Searching for 74.64.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 208 ms
REFUSED
Searching for 74.64.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 218 ms
Searching for 74.64.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 253 ms
Searching for 74.64.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 217 ms
Searching for 74.64.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 216 ms
Searching for 74.64.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 208 ms
REFUSED
Searching for 74.64.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 254 ms
Searching for 74.64.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 219 ms
Searching for 74.64.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 217 ms
Searching for 74.64.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 218 ms
REFUSED
Searching for 74.64.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 254 ms
Searching for 74.64.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 255 ms
REFUSED
Searching for 74.64.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 254 ms
Searching for 74.64.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 244 ms
REFUSED
Searching for 74.64.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 253 ms
Searching for 74.64.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 244 ms
REFUSED
Searching for 74.64.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 258 ms
Searching for 74.64.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 218 ms
Searching for 74.64.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 218 ms
Searching for 74.64.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 254 ms
REFUSED
Searching for 74.64.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 218 ms
Searching for 74.64.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 219 ms
REFUSED
Searching for 74.64.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 256 ms
Too many delegations to other servers. Probably a loop.



Total elapsed query time: 8,852 ms
Dear Guest,
DNSWatch.info is available to anybody for free. This is only possible since we display ads to cover our expenses.
An ad blocker installed on your browser is blocking ads on DNSWatch.info.
Please turn off your ad blocker or use a different browser to access this page.