Skip to content
Webify
Ping & Traceroute

Ping & Traceroute

Shows DNS, TCP 80/443 and traceroute hops.

Target

Shows DNS, TCP 80/443 and traceroute hops. Ping uses TCP 80/443; traceroute hops are listed separately.

Guide

Ping & Traceroute — Common searches and answers

Ping and traceroute show whether a target answers and which hops packets take. Searches like “slow site”, “timeout” and “where it breaks” land here. Webify uses DNS and TCP 80/443 instead of ICMP; many networks drop ICMP so classic ping lies. Only your own or authorised target.

Why TCP instead of ICMP?

Home ISPs and cloud security groups drop echo requests. The server can be up and still look like “no ping”. TCP 80/443 is closer to what a browser does: if the site opens, 443 should answer. If DNS fails you get a name error before any hop list.

The hop list is the path from where we run. A * * * row means that step hid ICMP time-exceeded; it may not be a break. If the last hop is the target and 443 is open, the path is complete. A break on the first hop is your network.

Where to look for slowness

Slow DNS delays the first byte. A long 443 handshake points to the certificate chain or a distant region. A sudden RTT jump on hops is backbone or a sea cable, not application code. Code and database delay do not show on traceroute; that needs APM and slow-query logs.

Permission

A constant ping tires a network and, without permission, is harassment. The tool uses a hop limit and one target. Do not flood someone else’s infrastructure “as a test”.

Outage scenarios and search intent

People type “site down ping timeout”, “where traceroute stops”, “slow from Turkey fast from abroad”. Split three cases: DNS fails (name error), 443 times out (service or firewall), * * * in the middle (a hop hides ICMP). The last one alone is not an outage. Regional slowness is anycast or a distant origin; look at hop RTT before blaming code.

A CDN shortens the hop list and makes the last hop an anycast IP. Traceroute to origin and traceroute to the site name are different paths; compare them on purpose. Webify measures from the server location, not your last mile. Repeat the same check on your LAN for home slowness. If hosting or the line is yours, open a ticket; we lock DNS, SSL and MX together in the office on a cutover.

Related services

More tools

Frequently asked questions

These are the queries people type for this tool. Answers match the visible text.

A check that the target answers and a rough latency. Here we use TCP 80/443.

The intermediate hops. A * row can mean that hop is hidden, not that the path is broken.

ICMP is blocked. If TCP 443 is open the site works. That is why the tool uses TCP.

No answer in the allotted time. The service may be down, filtered or the path too long.

Your network, modem or VPN. The target server is not in play yet.

Backbone, undersea cable or a distant region. Application code does not create traceroute RTT.

If the name does not resolve, hops never start. Use the DNS tool first.

No. From the Webify server. Your last mile is invisible; test locally for home slowness.

No. Quota and courtesy want one run. A loop without permission is harassment.

Diagnosis is on this page. If hosting or the line is yours, open a ticket; we lock DNS+SSL+MX together in the office for a cutover.