The ICSI Netalyzr
Start » Analysis » Results
Result Summary +/– (help)
188-195-232-104-dynip.superkabel.de / 188.195.232.104
Recorded at 13:59 EST (18:59 UTC), Dec 02 2011. Permalink. Client/server transcript.
Summary of Noteworthy Events –
Minor Aberrations
Certain TCP protocols are blocked in outbound traffic
Fragmented UDP traffic is blocked
The network blocks some or all EDNS replies
Not all DNS types were correctly processed
Address-based Tests +
NAT detection (?): NAT Detected
Local Network Interfaces (?): OK
DNS-based host information (?): OK
NAT support for Universal Plug and Play (UPnP) (?): Not found
Reachability Tests –
TCP connectivity (?): Note
Direct TCP access to remote FTP servers (port 21) is allowed.
Direct TCP access to remote SSH servers (port 22) is allowed.
Direct TCP access to remote SMTP servers (port 25) is allowed.
Direct TCP access to remote DNS servers (port 53) is allowed.
Direct TCP access to remote HTTP servers (port 80) is allowed.
Direct TCP access to remote POP3 servers (port 110) is allowed.
Direct TCP access to remote RPC servers (port 135) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote NetBIOS servers (port 139) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote IMAP servers (port 143) is allowed.
Direct TCP access to remote SNMP servers (port 161) is allowed.
Direct TCP access to remote HTTPS servers (port 443) is allowed.
Direct TCP access to remote SMB servers (port 445) is allowed.
Direct TCP access to remote SMTP/SSL servers (port 465) is allowed.
Direct TCP access to remote secure IMAP servers (port 585) is allowed.
Direct TCP access to remote authenticated SMTP servers (port 587) is allowed.
Direct TCP access to remote IMAP/SSL servers (port 993) is allowed.
Direct TCP access to remote POP/SSL servers (port 995) is allowed.
Direct TCP access to remote OpenVPN servers (port 1194) is allowed.
Direct TCP access to remote PPTP Control servers (port 1723) is allowed.
Direct TCP access to remote SIP servers (port 5060) is allowed.
Direct TCP access to remote BitTorrent servers (port 6881) is allowed.
Direct TCP access to remote TOR servers (port 9001) is allowed.
UDP connectivity (?): Note
Basic UDP access is available.
The applet was able to send fragmented UDP traffic.
The applet was unable to receive fragmented UDP traffic. The most likely cause is an error in your network's firewall configuration or NAT.
The maximum packet successfully received was 1472 bytes of payload.
Direct UDP access to remote DNS servers (port 53) is allowed.
Direct UDP access to remote NTP servers (port 123) is allowed.
Direct UDP access to remote NetBIOS NS servers (port 137) is blocked.
Direct UDP access to remote NetBIOS DGM servers (port 138) is blocked.
Direct UDP access to remote IKE key exchange servers (port 500) is allowed.
Direct UDP access to remote OpenVPN servers (port 1194) is allowed.
Direct UDP access to remote Slammer servers (port 1434) is allowed.
Direct UDP access to remote L2 tunneling servers (port 1701) is allowed.
Direct UDP access to remote IPSec NAT servers (port 4500) is allowed.
Direct UDP access to remote RTP servers (port 5004) is allowed.
Direct UDP access to remote RTCP servers (port 5005) is allowed.
Direct UDP access to remote SIP servers (port 5060) is allowed.
Direct UDP access to remote VoIP servers (port 7078) is allowed.
Direct UDP access to remote VoIP servers (port 7082) is allowed.
Direct UDP access to remote SCTP servers (port 9899) is allowed.
Direct UDP access to remote Steam gaming servers (port 27005) is allowed.
Direct UDP access to remote Steam gaming servers (port 27015) is allowed.
Traceroute (?): OK
It takes 14 network hops for traffic to pass from our server to your system, as shown below. For each hop, the time it takes to traverse it is shown in parentheses.
10.254.184.3 (0 ms)
ip-10-1-14-1.ec2.internal (0 ms)
ip-10-1-15-14.ec2.internal (2 ms)
216.182.224.80 (27 ms)
72.21.222.148 (0 ms)
72.21.220.44 (0 ms)
ash-bb1-link.telia.net (1 ms)
hbg-bb1-link.telia.net (120 ms)
bei-b2-link.telia.net (101 ms)
kabeldeutsch-ic-127486-bei-b2.c.telia.net (101 ms)
88-134-201-118-dynip.superkabel.de (104 ms)
83-169-129-221.static.superkabel.de (109 ms)
88-134-196-194-dynip.superkabel.de (110 ms)
83-169-133-9.static.superkabel.de (116 ms)
Path MTU (?): OK
The path between your network and our system supports an MTU of at least 1500 bytes, and the path between our system and your network has an MTU of 1500 bytes.
Network Access Link Properties +
Network latency measurements (?): Latency: 140ms Loss: 0.0%
TCP connection setup latency (?): 130ms
Network background health measurement (?): no transient outages
Network bandwidth measurements (?): Upload 1.1 Mbit/sec, Download 16 Mbit/sec
Network buffer measurements (?): Uplink 200 ms, Downlink is good
HTTP Tests +
Address-based HTTP proxy detection (?): OK
Content-based HTTP proxy detection (?): OK
HTTP proxy detection via malformed requests (?): OK
Filetype-based filtering (?): OK
HTTP caching behavior (?): OK
JavaScript-based tests (?): OK
DNS Tests –
Restricted domain DNS lookup (?): OK
We can successfully look up a name which resolves to the same IP address as our webserver. This means we are able to conduct many of the tests on your DNS server.
Unrestricted domain DNS lookup (?): OK
We can successfully look up arbitrary names from within the Java applet. This means we are able to conduct all test on your DNS server.
Direct DNS support (?): OK
All tested DNS types were received OK.
Direct EDNS support (?): Note
EDNS-enabled requests for small responses are answered successfully.
EDNS-enabled requests for medium-sized responses are answered successfully.
EDNS-enabled requests for large responses remain unanswered. This suggests that a proxy or firewall is unable to handle large extended DNS requests or fragmented UDP traffic.
DNS resolver address (?): OK
The IP address of your ISP's DNS Resolver is 83.169.184.161, which resolves to 83-169-184-161-isp.superkabel.de.
DNS resolver properties (?): Lookup latency 200ms
Your ISP's DNS resolver requires 200 msec to conduct an external lookup. It takes 160 msec for your ISP's DNS resolver to lookup a name on our server.
Your resolver correctly uses TCP requests when necessary.
Your resolver is using QTYPE=A for default queries.
Your resolver is not automatically performing IPv6 queries.
Your DNS resolver does not use EDNS.
Your DNS resolver can successfully accept large responses.
Your resolver does not use 0x20 randomization, but will pass names in a case-sensitive manner.
Your ISP's DNS server cannot use IPv6.
No transport problems were discovered which could affect the deployment of DNSSEC.
Direct probing of DNS resolvers (?)
Your system is configured to use 1 DNS resolver(s).
The resolver at 192.168.0.1 was unable to process the following tested types:
Large (~3000B) TXT records
Large (~3000B) TXT records fetched with EDNS0
It does not validate DNSSEC. It does not wildcard NXDOMAIN errors. The resolver reports the following properties:
Version: Nominum Vantio 5.0.1.0
DNS glue policy (?): OK
Your ISP's DNS resolver does not accept generic additional (glue) records — good.
Your ISP's DNS resolver does not accept additional (glue) records which correspond to nameservers.
Your ISP's DNS resolver does not follow CNAMEs.
DNS resolver port randomization (?): OK
Your ISP's DNS resolver properly randomizes its local port number.
The following graph shows DNS requests on the x-axis and the detected source ports on the y-axis.

DNS lookups of popular domains (?): OK
90 of 90 popular names were resolved successfully. Show all names.
15 popular names have a mild anomaly. The ownership suggested by the reverse name lookup does not match our understanding of the original name. The most likely cause is the site's use of a Content Delivery Network. Show all names.
3 popular names have a mild anomaly: we are unable to find a reverse name associated with the IP address provided by your ISP's DNS server. This is most likely due to a slow responding DNS server or misconfiguration on the part of the domain owner. Show all names.
DNS external proxy (?): OK
Your host ignores external DNS requests.
DNS results wildcarding (?): OK
Your ISP correctly leaves non-resolving names untouched.
DNS-level redirection of specific sites (?): OK
Your ISP does not appear to be using DNS to redirect traffic for specific websites.
IPv6 Tests +
DNS support for IPv6 (?): OK
IPv4, IPv6, and your web browser (?): No IPv6 Support
IPv6 connectivity (?): No IPv6 Support
Host Properties +
System clock accuracy (?): OK
Browser properties (?): OK
Uploaded data (?): OK
Feedback
Please take a moment to tell us about your network. All fields are optional. If you would like to contact us with questions about your results, please contact us with your session ID, or get in touch on the mailing list.
How is your machine connected to the network?
Wireless Wired
Where are you right now?
At home
At work
In a public setting (wifi hotspot, Internet cafe, etc.)
Other (please describe in comments below)
Feel free to leave additional comments below.

Your email address:
ID 43ca208a-24468-a321ad6b-55b2-4f6b-af55 FAQs + Blog + Links + ICSI