Hostname or IP
Type
Searching for 151.161.28.120.in-addr.arpa. PTR record at L.ROOT-SERVERS.NET. [199.7.83.42] ...took 16 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at b.in-addr-servers.arpa. [199.253.183.183] ...took 8 ms
Searching for ns1.apnic.net. A record at B.ROOT-SERVERS.NET. [192.228.79.201] ...took 154 ms
Searching for ns1.apnic.net. A record at j.gtld-servers.net. [192.48.79.30] ...took 303 ms
Searching for ns1.apnic.net. A record at ns3.apnic.net. [202.12.28.131] ...took 249 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at ns1.apnic.net. [202.12.29.25] ...took 326 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 sec4.apnic.net. [202.12.31.141] ...took 311 ms
Searching for g-net1.globe.com.ph. A record at g-net1.globe.com.ph. [203.127.225.11] ...took 279 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 280 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 280 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 281 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 281 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 281 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 281 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 281 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 281 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 285 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 280 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 287 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 283 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 283 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 282 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 281 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 282 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 282 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 281 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 283 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 282 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 280 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 280 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 281 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 281 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 281 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 280 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 281 ms
Too many delegations to other servers. Probably a loop.



Total elapsed query time: 9,249 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.