Network utilities

Network Diagnostics Suite

Run DNS lookup, ping, traceroute, reverse DNS, TCP port checks, RDAP and IP checks from one place. For connection performance, use our Internet & WiFi Speed Test.

DNS & RDAP lookup Bounded diagnostics Public targets only
How this suite works

Browser-based network troubleshooting

The Network Diagnostics Suite brings together DNS lookup, ping, traceroute, reverse DNS, RDAP registration checks, TCP port testing and bandwidth unit conversion in one workflow-friendly page. Each tool answers a different question, so you can narrow down connectivity, naming, routing or service-access problems without installing desktop software.

These checks are intended for public domains and IP addresses you own or are authorised to test. Private, reserved and local-network targets are blocked for safety. For headline connection speed, latency and upload measurement, use the dedicated Internet Speed Test after basic reachability checks pass.

Step-by-step paths

Recommended troubleshooting order

Start with the narrowest check that matches the symptom, then move outward only if the earlier step does not explain the problem.

Website does not open

  1. Run a DNS lookup for the domain and confirm A or AAAA records exist.
  2. If DNS resolves, run ping to the published address to test reachability.
  3. If ping fails intermittently, use traceroute to see where the path changes.
  4. If the site should be public but still fails, test authorised TCP ports such as 80 and 443.

Email delivery problems

  1. Look up MX records and confirm the listed mail hosts match your provider.
  2. Check TXT records for SPF or verification entries required by your mail platform.
  3. Ping or traceroute the MX hostname only if you are authorised to test that infrastructure.
  4. Use RDAP if you need to confirm which network range owns a sending IP.

Slow or unstable connection

  1. Begin with the speed test on WiFi and Ethernet under similar conditions.
  2. Run ping to a stable public resolver such as your ISP gateway or a known public DNS address.
  3. If latency spikes, compare traceroute results at different times of day.
  4. Convert plan speeds with the bandwidth converter to compare expected and measured throughput.
Need connection performance results? Measure latency, download and upload on the dedicated speed test.
Open Speed Test

TCP Port Check

Check whether common TCP service ports respond on a public domain or IP address you are authorized to test.

DNS Lookup

Ping, Traceroute and Reverse DNS

Run these diagnostics only for infrastructure you own or are authorized to test.

IP Lookup (RDAP)

Bandwidth Parameter Converter

Enter a positive bandwidth value to convert between BPS, KBPS, MBPS and GBPS.

Diagnostic guide

Choose the right network check

Each test answers a different troubleshooting question. Begin with the narrowest check that matches the problem.

DNS lookup

Confirm the addresses, mail routes and name-server records published for a domain.

Ping

Check basic reachability and round-trip response to a public destination.

Traceroute

Inspect the routed path when latency or reachability changes between networks.

RDAP

Review public registration details for an IP range or domain.

Port check

Test an authorized public TCP service such as web, mail or remote access.

Bandwidth conversion

Translate line-rate units without confusing bits and bytes.

Helpful answers

Network diagnostics questions

What is the difference between DNS lookup and RDAP?

DNS lookup shows live name records such as website addresses, mail servers and text verification entries. RDAP shows public registration metadata for a domain or IP range, such as status, country and registration dates.

When should I use ping instead of traceroute?

Use ping when you only need to know whether a destination responds and how stable the round-trip time is. Use traceroute when ping works but performance is poor and you need to see which network hops add delay.

Why does reverse DNS matter?

Reverse DNS maps an IP address back to a hostname. It is commonly checked by mail servers and some security systems, and it can help confirm whether an address belongs to the provider you expect.

Can I test any IP address or port from this page?

Only test public systems you own or have permission to assess. Private, reserved and local-network targets are blocked, and port checks should never be used for unauthorised scanning.

Why can DNS results differ from what I see on my computer?

DNS answers depend on resolver caching, TTL values and recent record changes. A record that was updated recently may appear at one resolver before another.

What does a filtered or closed port result mean?

A closed port usually means nothing is listening on that service at the target. A filtered result often indicates a firewall or network policy is blocking the probe before it reaches the service.

Is server-side ping always identical to ping from my PC?

No. This page runs diagnostics from the website server path, which can differ from your home or office route. Use it for quick checks, then compare with local tools when the path matters.

Which tool should I use after fixing DNS or routing?

After naming and reachability look correct, run the speed test to measure throughput, then use the dedicated port checker or IP tools if a specific service still fails.

Using network diagnostics with Zerolink business links

Combine DNS, ping and port checks when troubleshooting offices on Zerolink broadband or leased lines across Panipat, Karnal and Gharaunda.

Leased line Enterprise solutions Panipat broadband

Link copied