Test a public IP address or domain from the Zerolink server using ping, traceroute or reverse DNS.
Ping, traceroute and reverse DNS are basic reachability checks used to see whether a public destination responds from the network and how traffic is routed toward it. They are often the next step after DNS lookup confirms that a hostname resolves to the expected address.
This tool runs diagnostics from the Zerolink server, not from your home or office connection. That makes it useful for quick external checks, but results can differ from what you see locally because routing and latency depend on where the test originates.
Only test destinations you own or are authorised to diagnose. For a fuller workflow with DNS, port checks and bandwidth conversion, use the Network Diagnostics Suite.
Start with the simplest check that matches the symptom, then add traceroute or reverse DNS only if needed.
Choose one diagnostic and enter a public destination.
Ping sends 10 ICMP packets from the Zerolink server. Test only destinations you own or are authorised to diagnose.
Read the result correctly
Checks ICMP reachability and can reveal round-trip latency and packet loss when the destination responds.
Shows up to 12 network hops from our server. Asterisks often mean a router is filtering diagnostic replies.
Finds the PTR hostname published for the destination IP. Missing PTR data does not mean the host is offline.
This tool measures from Zerolink’s hosting server. For your own connection quality, use the Internet and WiFi Speed Test.
Ping sends small ICMP requests and reports whether the destination responds, along with round-trip time and packet loss when the server provides those values.
Some hosts and firewalls block ICMP traffic while still allowing web, email or application connections. A failed ping alone does not prove that a service is offline.
Traceroute displays network hops between the Zerolink diagnostic server and the destination. Missing hops can occur when routers suppress diagnostic responses.
A reverse DNS lookup asks for the PTR hostname associated with an IP address. Not every public IP has a PTR record.
No. Ping and traceroute run from the Zerolink web server, so latency and routing can differ from results produced on your own connection.
Both are valid. A domain is convenient, but ping ultimately tests the resolved address. If DNS recently changed, compare with a direct IP test as well.
Packet loss means some ICMP replies did not return within the timeout. It can indicate congestion, filtering or an unstable path, but a small amount may appear even on healthy links.
No. Only diagnose public systems you own or have permission to test. Private, local and reserved targets are blocked.
Separate local Wi-Fi issues from upstream routing when latency spikes on lines serving Gharaunda, Panipat and Karnal. Share repeated results with support if the path stays unstable after a reboot.