| 1 |
> |
| 2 |
> Since you know the server IPs, and there's only a small number so you |
| 3 |
> could try connection to each of them and see which one(s) fail. |
| 4 |
> |
| 5 |
> Or tcpdump, or netstat etc. |
| 6 |
> |
| 7 |
|
| 8 |
FWIW i can route to all the v4 addresses; |
| 9 |
|
| 10 |
# for i in 18.9.60.141 18.191.65.131 37.191.226.104 92.43.111.21 |
| 11 |
193.164.133.100 216.66.15.2 ; do nc -zv $i 443; done |
| 12 |
cryptonomicon.mit.edu [18.9.60.141] 443 (https) open |
| 13 |
ec2-18-191-65-131.us-east-2.compute.amazonaws.com [18.191.65.131] 443 |
| 14 |
(https) open |
| 15 |
host-37-191-226-104.lynet.no [37.191.226.104] 443 (https) open |
| 16 |
Warning: forward host lookup failed for oteiza.siccegge.de: |
| 17 |
oteiza.siccegge.de [92.43.111.21] 443 (https) open |
| 18 |
DNS fwd/rev mismatch: mail.b4ckbone.de != beta.b4ckbone.de |
| 19 |
mail.b4ckbone.de [193.164.133.100] 443 (https) open |
| 20 |
zimmermann.mayfirst.org [216.66.15.2] 443 (https) open |
Archives