Hostname or IP
Type
Searching for 151.161.28.120.in-addr.arpa. PTR record at I.ROOT-SERVERS.NET. [192.36.148.17] ...took 1 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at b.in-addr-servers.arpa. [199.253.183.183] ...took 88 ms
Searching for ns2.lacnic.net. A record at F.ROOT-SERVERS.NET. [192.5.5.241] ...took 2 ms
Searching for ns2.lacnic.net. A record at a.gtld-servers.net. [192.5.6.30] ...took 121 ms
Searching for ns2.lacnic.net. A record at ns.lacnic.net. [200.3.13.10] ...took 220 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at ns2.lacnic.net. [200.3.13.11] ...took 219 ms
Searching for g-net1.globe.com.ph. A record at C.ROOT-SERVERS.NET. [192.33.4.12] ...took 2 ms
Searching for g-net1.globe.com.ph. A record at sns-pb.isc.org. [192.5.4.1] ...took 9 ms
Searching for g-net1.globe.com.ph. A record at g-net.globe.com.ph. [203.127.225.10] ...took 339 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 352 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 352 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 342 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 350 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 340 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 354 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 341 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 353 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 346 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 352 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 342 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 352 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 354 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 351 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 340 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 353 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 340 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 350 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 351 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 342 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 352 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 341 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 353 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 342 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 352 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 352 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 352 ms
Too many delegations to other servers. Probably a loop.



Total elapsed query time: 10,402 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.