Skip to main content
Networking tools is a collection of in-browser network diagnostics that doesn’t require installing anything locally. Everything runs from our infrastructure, which is occasionally what you want when troubleshooting “is it me or is it the destination” questions. Open it at betworkingtools.net ↗.

​
What’s in there

  • DNS lookup. A, AAAA, CNAME, MX, TXT, SRV, CAA, NS records for any hostname. Optional check against multiple resolvers so you can see where caching is stale.
  • Traceroute / MTR. Path from our network to a destination, with per-hop latency. Useful when a customer reports “slow from my place” and you want to rule out the route from another perspective.
  • Ping. Plain ICMP from our edge.
  • Port check. Is TCP port <n> open on <host>? Returns connect / refused / timeout.
  • HTTP header viewer. GETs the URL and shows the response headers, status, and timing. Good for verifying CDN, cache, and security headers.
  • Whois lookup. RDAP-style lookup for domains and IP allocations.

​
When to use it

  • A customer reports an issue and you want a second opinion from outside their network.
  • You’re verifying DNS propagation after a change. Run the lookup against multiple resolvers; if our resolver returns the new value but Google’s still serves the old, it’s caching downstream and there’s nothing to do but wait the TTL.
  • You’re diagnosing intermittent connectivity. Traceroute and MTR help isolate whether the problem is on the customer’s first hop or somewhere in transit.
  • You need to confirm a port is reachable from outside the firewall. Local-machine nc or telnet won’t tell you anything if the firewall lets you out but blocks inbound.
Output from these tools is text. If you’re escalating to support, paste the relevant block into the ticket — it’s faster than describing the symptom in prose.

​
Need a hand?

Open a ticket

Best for anything that needs an account check or a config change on our end.

Live chat

Faster for quick questions during business hours.