Hostname or IP
Type
Searching for 151.161.28.120.in-addr.arpa. PTR record at A.ROOT-SERVERS.NET. [198.41.0.4] ...took 16 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.212.0.73] ...took 100 ms
Searching for tinnie.arin.net. A record at A.ROOT-SERVERS.NET. [198.41.0.4] ...took 15 ms
Searching for tinnie.arin.net. A record at m.gtld-servers.net. [192.55.83.30] ...took 124 ms
Searching for tinnie.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 157 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at tinnie.arin.net. [199.212.0.53] ...took 93 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 251 ms
Searching for g-net1.globe.com.ph. A record at g-net1.globe.com.ph. [203.127.225.11] ...took 370 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 364 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 343 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 366 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 374 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 355 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 338 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 348 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 374 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 732 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 338 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 374 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 357 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 363 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 338 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 355 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 357 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 374 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 356 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 366 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 355 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 343 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 344 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 357 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 342 ms
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net.globe.com.ph. [203.127.225.10] ...took 357 ms
REFUSED
Searching for 151.161.28.120.in-addr.arpa. PTR record at g-net1.globe.com.ph. [203.127.225.11] ...took 373 ms
Too many delegations to other servers. Probably a loop.



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