Weblog created by Anton Bayer
RSS News von collabor
 
Sonntag, 25. Juni 2006
Netzwerktools & Verschlüsselung einsetzen
C:\>ping www.heise.de

Ping www.heise.de [193.99.144.85] mit 32 Bytes Daten:

Antwort von 193.99.144.85: Bytes=32 Zeit=47ms TTL=236
Antwort von 193.99.144.85: Bytes=32 Zeit=38ms TTL=236
Antwort von 193.99.144.85: Bytes=32 Zeit=45ms TTL=236
Antwort von 193.99.144.85: Bytes=32 Zeit=42ms TTL=236

Ping-Statistik für 193.99.144.85:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 38ms, Maximum = 47ms, Mittelwert = 43ms

C:\>

C:\>tracert www.heise.de

Routenverfolgung zu www.heise.de [193.99.144.85] über maximal 30 Abschnitte:

1 <1 ms <1 ms <1 ms balin.mshome.net [192.168.0.1]
2 2 ms 2 ms 2 ms 192.168.25.254
3 4 ms 3 ms 3 ms 193.170.138.225
4 62 ms 68 ms 82 ms vcampus.sth.ac.at [192.76.244.5]
5 11 ms 20 ms 16 ms Wien2.ACO.net [193.171.13.5]
6 16 ms 24 ms 6 ms Wien1.ACO.net [193.171.23.33]
7 7 ms 17 ms 6 ms vix2.above.net [193.203.0.45]
8 8 ms 6 ms 7 ms ge-2-4.mpr1.vie4.at.above.net [212.69.169.10]
9 58 ms 208 ms 210 ms po-20.mpr1.fra1.de.above.net [64.125.23.145]
10 21 ms 26 ms 20 ms ge-1-1.er2b.fra1.de.above.net [64.125.23.222]
11 38 ms 37 ms 37 ms plusline.fra1.de.above.net [62.4.64.54]
12 37 ms 38 ms 44 ms heise1.f.de.plusline.net [213.83.46.195]
13 37 ms 43 ms 37 ms www.heise.de [193.99.144.85]

Ablaufverfolgung beendet.


Ergebnis: traceroute to www.heise.de

1 fwsrv2.ces.uta.at (213.90.2.3) 0.487 ms 0.442 ms 0.330 ms
2 213.90.1.17 (213.90.1.17) 0.918 ms 0.949 ms 0.599 ms
3 wat1-15-21.net.uta.at (62.218.15.21) 0.853 ms 0.686 ms 0.795 ms
4 c76wmode1-tengigE4-1.net.uta.at (212.152.192.206) 0.830 ms 0.895 ms 0.798 ms
5 vie3-core.gigabiteth1-0.swip.net (130.244.205.57) 1.014 ms 1.052 ms 1.216 ms
6 shu1-core.pos2-0.swip.net (130.244.205.50) 1.513 ms 1.424 ms 1.416 ms
7 vix2.above.net (193.203.0.45) 1.262 ms 1.241 ms 1.250 ms
8 ge-2-7.mpr1.vie4.at.above.net (212.69.169.6) 1.667 ms 1.325 ms 1.450 ms
9 po-20.mpr1.fra1.de.above.net (64.125.23.145) 34.384 ms 34.399 ms 34.568 ms
10 ge-1-2.er2b.fra1.de.above.net (64.125.23.218) 34.935 ms 34.625 ms 34.525 ms
11 plusline.fra1.de.above.net (62.4.64.54) 34.569 ms 34.577 ms 34.535 ms
12 heise1.f.de.plusline.net (213.83.46.195) 35.187 ms 35.281 ms 35.184 ms
13 www.heise.de (193.99.144.85) 76.392 ms 36.129 ms 35.620 ms

-------------------------------------------
-------------------------------------------

C:\>ping www.heise.de

Ping www.heise.de [193.99.144.85] mit 32 Bytes Daten:

Antwort von 193.99.144.85: Bytes=32 Zeit=41ms TTL=236
Antwort von 193.99.144.85: Bytes=32 Zeit=51ms TTL=236
Antwort von 193.99.144.85: Bytes=32 Zeit=35ms TTL=236
Antwort von 193.99.144.85: Bytes=32 Zeit=51ms TTL=236

Ping-Statistik für 193.99.144.85:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 35ms, Maximum = 51ms, Mittelwert = 44ms

C:\>

C:\>tracert www.heise.de

Routenverfolgung zu www.heise.de [193.99.144.85] über maximal 30 Abschnitte:

1 <1 ms <1 ms <1 ms balin.mshome.net [192.168.0.1]
2 2 ms 2 ms 2 ms 192.168.25.254
3 4 ms 4 ms 4 ms 193.170.138.225
4 8 ms 13 ms 6 ms vcampus.sth.ac.at [192.76.244.5]
5 11 ms 9 ms 8 ms Wien2.ACO.net [193.171.13.5]
6 243 ms 157 ms 63 ms Wien1.ACO.net [193.171.23.33]
7 132 ms 55 ms 15 ms vix2.above.net [193.203.0.45]
8 36 ms 29 ms 16 ms ge-2-4.mpr1.vie4.at.above.net [212.69.169.10]
9 39 ms 22 ms 35 ms po-20.mpr1.fra1.de.above.net [64.125.23.145]
10 21 ms 22 ms 20 ms ge-1-1.er2b.fra1.de.above.net [64.125.23.222]
11 59 ms 40 ms 46 ms plusline.fra1.de.above.net [62.4.64.54]
12 39 ms 48 ms 38 ms heise1.f.de.plusline.net [213.83.46.195]
13 38 ms 52 ms 52 ms www.heise.de [193.99.144.85]

Ablaufverfolgung beendet.

C:\>


Ergebnis: traceroute to www.heise.de

1 fwsrv2.ces.uta.at (213.90.2.3) 0.768 ms 0.405 ms 0.339 ms
2 213.90.1.17 (213.90.1.17) 1.352 ms 1.314 ms 1.138 ms
3 wat1-15-21.net.uta.at (62.218.15.21) 1.027 ms 0.983 ms 0.647 ms
4 c76wmode1-tengigE4-1.net.uta.at (212.152.192.206) 0.983 ms 1.302 ms 1.160 ms
5 vie3-core.gigabiteth1-0.swip.net (130.244.205.57) 1.365 ms 1.267 ms 1.163 ms
6 shu1-core.pos2-0.swip.net (130.244.205.50) 1.406 ms 1.693 ms 1.582 ms
7 vix2.above.net (193.203.0.45) 1.387 ms 1.724 ms 1.550 ms
8 ge-2-7.mpr1.vie4.at.above.net (212.69.169.6) 1.405 ms 1.703 ms 1.567 ms
9 po-20.mpr1.fra1.de.above.net (64.125.23.145) 34.334 ms 34.611 ms 34.882 ms
10 ge-1-2.er2b.fra1.de.above.net (64.125.23.218) 35.079 ms 40.008 ms 34.870 ms
11 plusline.fra1.de.above.net (62.4.64.54) 62.611 ms 49.169 ms 75.838 ms
12 heise1.f.de.plusline.net (213.83.46.195) 357.616 ms 184.416 ms 35.282 ms
13 www.heise.de (193.99.144.85) 35.716 ms 35.793 ms 35.701 ms

-------------------------------------------
-------------------------------------------

Your system ports are now being scanned and the results will be
returned shortly...
Results from quick scan at TCP/IP address:
193.170.138.226


Ideally your status should be "Blocked". This indicates that your ports
are not only
closed, but they are completely hidden (stealthed) to attackers.

Service
Ports
Status
Additional Information
FTP DATA
20
BLOCKED
This port has not responded to any of our probes. It appears to
be completely stealthed.
FTP
21
BLOCKED
This port has not responded to any of our probes. It appears to
be completely stealthed.
SSH
22
BLOCKED
This port has not responded to any of our probes. It appears to
be completely stealthed.
TELNET
23
BLOCKED
This port has not responded to any of our probes. It appears to
be completely stealthed.
SMTP
25
BLOCKED
This port has not responded to any of our probes. It appears to
be completely stealthed.
DNS
53
BLOCKED
This port has not responded to any of our probes. It appears to
be completely stealthed.
DCC
59
BLOCKED
This port has not responded to any of our probes. It appears to
be completely stealthed.
FINGER
79
BLOCKED
This port has not responded to any of our probes. It appears to
be completely stealthed.
WEB
80
BLOCKED
This port has not responded to any of our probes. It appears to
be completely stealthed.
POP3
110
BLOCKED
This port has not responded to any of our probes. It appears to
be completely stealthed.
IDENT
113
BLOCKED
This port has not responded to any of our probes. It appears to
be completely stealthed.
Location Service
135
BLOCKED
This port has not responded to any of our probes. It appears to
be completely stealthed.
NetBIOS
139
BLOCKED
This port has not responded to any of our probes. It appears to
be completely stealthed.
HTTPS
443
BLOCKED
This port has not responded to any of our probes. It appears to
be completely stealthed.
Server Message Block
445
BLOCKED
This port has not responded to any of our probes. It appears to
be completely stealthed.
SOCKS PROXY
1080
BLOCKED
This port has not responded to any of our probes. It appears to
be completely stealthed.
UPnP
5000
BLOCKED
This port has not responded to any of our probes. It appears to
be completely stealthed.
WEB PROXY
8080
BLOCKED
This port has not responded to any of our probes. It appears to
be completely stealthed.

Results from scan of commonly used trojans
at TCP/IP address: 193.170.138.226

Service
Ports
Status
Possible Trojans
Trojan
1243
BLOCKED
This port has not responded to any of our probes. It appears to
be completely stealthed.
Trojan
1999
BLOCKED
This port has not responded to any of our probes. It appears to
be completely stealthed.
Trojan
6776
BLOCKED
This port has not responded to any of our probes. It appears to
be completely stealthed.
Trojan
7789
BLOCKED
This port has not responded to any of our probes. It appears to
be completely stealthed.
Trojan
12345
BLOCKED
This port has not responded to any of our probes. It appears to
be completely stealthed.
Trojan
31337
BLOCKED
This port has not responded to any of our probes. It appears to
be completely stealthed.
Trojan
54320
BLOCKED
This port has not responded to any of our probes. It appears to
be completely stealthed.
Trojan
54321
BLOCKED
This port has not responded to any of our probes. It appears to
be completely stealthed.

Results from scan of ICMP at TCP/IP
address: 193.170.138.226


Protocol
Type
Status
Additional Information
ICMP
8
BLOCKED
An ICMP ping request is usually used to test Internet access.
However, an attacker can use it to determine if your computer is available and
what OS you are running. This gives him valuable information when he is
determining what type of attack to use against you.

link (0 comments)   comment