In addition to the existing answers, you can also use the standard traceroute
command with the -P
and -p
flags. This option requires root privileges.
Actually, while using tcpdump
to confirm this, it seems that you actually have to use -T
instead of -P tcp
. I tried with -P 6
as well but that didn't cause traceroute
to use TCP. -M tcp
does work.
$ sudo traceroute -T -p 22 79.125.0.4
traceroute to 79.125.0.4 (79.125.0.4), 30 hops max, 60 byte packets
1 rbx-5-m1.fr.eu (91.121.21.253) 0.708 ms 0.690 ms 0.583 ms
2 rbx-1-6k.fr.eu (213.251.191.1) 0.951 ms * 0.765 ms
3 rbx-g1-a9.fr.eu (94.23.122.106) 1.325 ms 1.485 ms 1.047 ms
4 * * *
5 195.66.237.175 (195.66.237.175) 5.894 ms 6.812 ms 4.083 ms
6 178.236.3.57 (178.236.3.57) 16.493 ms 16.813 ms 16.393 ms
7 178.236.3.155 (178.236.3.155) 16.600 ms 16.479 ms 16.422 ms
8 178.236.0.75 (178.236.0.75) 16.337 ms 16.384 ms 16.333 ms
9 178.236.0.58 (178.236.0.58) 17.786 ms 16.171 ms 16.957 ms
10 ec2-79-125-0-4.eu-west-1.compute.amazonaws.com (79.125.0.4) 18.493 ms 18.672 ms 18.244 ms
11 * * *
12 * * *
13 * * *