Searching for 104.163.252.180.in-addr.arpa. PTR record at A.ROOT-SERVERS.NET. [198.41.0.4]
...took 6 ms
Searching for 104.163.252.180.in-addr.arpa. PTR record at b.in-addr-servers.arpa. [199.253.183.183] ...took 7 ms
Searching for 104.163.252.180.in-addr.arpa. PTR record at b.in-addr-servers.arpa. [199.253.183.183] ...took 7 ms
Searching for ns3.lacnic.net. A record at D.ROOT-SERVERS.NET. [199.7.91.13]
...took 6 ms
Searching for ns3.lacnic.net. A record at b.gtld-servers.net. [192.33.14.30] ...took 31 ms
Searching for ns3.lacnic.net. A record at ns2.lacnic.net. [200.3.13.11] ...took 193 ms
Searching for 104.163.252.180.in-addr.arpa. PTR record at ns3.lacnic.net. [200.3.13.14]
...took 204 msSearching for ns3.lacnic.net. A record at b.gtld-servers.net. [192.33.14.30] ...took 31 ms
Searching for ns3.lacnic.net. A record at ns2.lacnic.net. [200.3.13.11] ...took 193 ms
Searching for ns4.telkomhosting.com. A record at C.ROOT-SERVERS.NET. [192.33.4.12]
...took 11 ms
Searching for ns4.telkomhosting.com. A record at g.gtld-servers.net. [192.42.93.30] ...took 6 ms
Searching for ns4.telkomhosting.com. A record at ns5.telkomhosting.com. [36.66.2.131] ...took 298 ms
Searching for ns4.telkomhosting.com. A record at g.gtld-servers.net. [192.42.93.30] ...took 6 ms
Searching for ns4.telkomhosting.com. A record at ns5.telkomhosting.com. [36.66.2.131] ...took 298 ms
Searching for ns3.telkomhosting.com. A record at D.ROOT-SERVERS.NET. [199.7.91.13]
...took 7 ms
Searching for ns3.telkomhosting.com. A record at d.gtld-servers.net. [192.31.80.30] Timed out while trying to resolve ns3.telkomhosting.com./A, id=7892
Searching for ns3.telkomhosting.com. A record at j.gtld-servers.net. [192.48.79.30] ...took 12 ms
Searching for ns3.telkomhosting.com. A record at ns8.telkomhosting.com. [36.66.2.134] ...took 298 ms
Searching for ns3.telkomhosting.com. A record at d.gtld-servers.net. [192.31.80.30] Timed out while trying to resolve ns3.telkomhosting.com./A, id=7892
Searching for ns3.telkomhosting.com. A record at j.gtld-servers.net. [192.48.79.30] ...took 12 ms
Searching for ns3.telkomhosting.com. A record at ns8.telkomhosting.com. [36.66.2.134] ...took 298 ms
Searching for ns2.telkom.co.id. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 30 ms
Searching for ns2.telkom.co.id. A record at b.dns.id. [103.19.179.179] ...took 95 ms
Total elapsed query time: 3,492 ms
Searching for ns2.telkom.co.id. A record at b.dns.id. [103.19.179.179] ...took 95 ms
Searching for ns4-34.azure-dns.info. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for ns4-34.azure-dns.info. A record at b2.info.afilias-nst.org. [199.249.121.1] ...took 6 ms
Searching for ns4-34.azure-dns.info. A record at ns4-03.azure-dns.info. [208.84.5.3] ...took 15 ms
Searching for ns2.telkom.co.id. A record at ns4-34.azure-dns.info. [13.107.206.34]
...took 13 msSearching for ns4-34.azure-dns.info. A record at b2.info.afilias-nst.org. [199.249.121.1] ...took 6 ms
Searching for ns4-34.azure-dns.info. A record at ns4-03.azure-dns.info. [208.84.5.3] ...took 15 ms
Searching for ns2.telkom.co.id. AAAA record at C.ROOT-SERVERS.NET. [192.33.4.12]
...took 11 ms
Searching for ns2.telkom.co.id. AAAA record at d.dns.id. [45.126.57.57] ...took 204 ms
Searching for ns2.telkom.co.id. AAAA record at d.dns.id. [45.126.57.57] ...took 204 ms
Searching for ns3-34.azure-dns.org. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for ns3-34.azure-dns.org. A record at d0.org.afilias-nst.org. [199.19.57.1] ...took 12 ms
Searching for ns3-34.azure-dns.org. A record at ns3-01.azure-dns.org. [204.14.183.1] ...took 7 ms
Searching for ns2.telkom.co.id. AAAA record at ns3-34.azure-dns.org. [13.107.222.34]
...took 7 msSearching for ns3-34.azure-dns.org. A record at d0.org.afilias-nst.org. [199.19.57.1] ...took 12 ms
Searching for ns3-34.azure-dns.org. A record at ns3-01.azure-dns.org. [204.14.183.1] ...took 7 ms
Nameserver ns3-34.azure-dns.org. reports: No such host ns2.telkom.co.id.
Total elapsed query time: 3,492 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.