Difference between `Tracert` and `Traceroute`

They should be the same. Here is what I found:

Both commands are basically the same thing. The main difference is of the Operating System and how the command is implemented in the background.On the foreground you see the same kind of information in both cases. Traceroute is a computer network diagnostic tool, displaying the route and measuring transitdelays of packets across the network.

The command is available in Unix OS as ‘traceroute’, while it is available as ‘tracert’ in Windows NT based OS. For IPv6 it is often known as ‘tracert6’. In Linux the command sends sequence of User Data-gram Protocol tothe destination host by default. While in the case of Windows it sends ICMP echo requests instead of UDP packets.

https://www.quora.com/What-is-the-difference-between-traceroute-and-tracert

• Ping command, ping ^[1],[2], is the basic tool that sends a package to the destination and waits for the answer. In the output it shows the delays ( min/avg/max/mdev ). You can ping different ports too. You can ping different port too with other programs (see below). Among the many options you can select -p to specify the packet you send, useful for diagnosing data-dependent problems in a network.

• Tracert and traceroute give you for each node between origin and destination the delay time. Some servers reserve a different amount of bandwidth to different services (udp,http...) so testing different ports (-p option udp,tcp,icmp...) gives different info.
  It is useful to understand where you spend more time. It is useful when you can change your routing to avoid those bottlenecks. It is slower than ping because will try, as said, to ask to each node between origin and destination.

• For what I know pop is a protocol for email and it is possible there is a set of command to test the speed of this service too...

• To ping a specific port (it is not really pinging) you can use tools as tcping ^[3] or tcpping ^[4].

  A common way to measure network latency to a remote host is by using ping utility which uses ICMP echo request and reply packets. In some cases, however, ICMP traffic is blocked by firewalls, which renders ping utility useless with hosts behind restrictive firewalls. In such case, you will need to rely on layer-3 measurement tools that use TCP/UDP packets since these layer-3 packets are more likely to bypass common firewall rules.