Debug your Internet.

I ran across this today, an interesting tool to debug your internet connection (Thanks Dr Stewart)

this is a project of Berkeley.edu, and according to the about us page.

The Netalyzr analyzes various properties of your Internet connection that you should care about — including blocking of important services, HTTP caching behavior and proxy correctness, your DNS server’s resilience to abuse, NAT detection, as well as latency & bandwidth measurements — and reports its findings in a detailed report. You can check out an example report from a real network to get a better idea of our tests.

To perform these tests, the Netalyzr runs a Java applet on your computer. You may be asked to confirm network-related activities that your system’s applet security policy or firewall considers sensitive. We hope that you will permit any such activity, as it will ensure more comprehensive test results. For details on the tests that will be performed please visit the FAQ section.

to try it today, click the link below and let me know what you think by commenting on this post:

http://netalyzr.icsi.berkeley.edu/index.html

here are my results:

Summary of Noteworthy Events+  –

Major Abnormalities–

• Your DNS resolver returns IP addresses for names that do not exist 

Minor Aberrations–

• Certain UDP protocols are blocked in outbound traffic 
• The network measured bursts of packet loss 
• Network packet buffering may be excessive 
• Not all DNS types were correctly processed 
• Your computer’s clock is slightly slow 

Address-based Tests+  –

NAT detection (?): NAT Detected+

Local Network Interfaces (?): OK+

DNS-based host information (?): OK+

NAT support for Universal Plug and Play (UPnP) (?): Yes+

Reachability Tests+  –

TCP connectivity (?): OK+

UDP connectivity (?): Note–

Basic UDP access is available.The applet was able to send fragmented UDP traffic.

The applet was able to receive fragmented UDP traffic.

UDP access to remote DNS servers (port 53) appears to pass through a firewall or proxy. The applet was unable to transmit an arbitrary request on this UDP port, but was able to transmit a legitimate DNS request, suggesting that a proxy, NAT, or firewall intercepted and blocked the deliberately invalid request.

Direct UDP access to remote NTP servers (port 123) is allowed.

Direct UDP access to remote NetBIOS NS servers (port 137) is allowed.

Direct UDP access to remote NetBIOS DGM servers (port 138) is allowed.

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+

Path MTU (?): OK+

Network Access Link Properties+  –

Network latency measurements (?): Latency: 68ms Loss: 0.0%+

TCP connection setup latency (?): 66ms+

Network background health measurement (?): 1 transient outages, longest: 0.6 seconds–

During most of Netalyzr’s execution, the applet continuously measures the state of the network in the background, looking for short outages. During testing, the applet observed 1 such outages. The longest outage lasted for 0.6 seconds. This suggests a general problem with the network where connectivity is intermittent. This loss might also cause some of Netalyzr’s other tests to produce incorrect results.

Network bandwidth (?): Upload 1.8 Mbit/sec, Download 3.9 Mbit/sec+

Network buffer measurements (?): Uplink 51 ms, Downlink 2100 ms–

We estimate your uplink as having 51 msec of buffering. This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic.

We estimate your downlink as having 2100 msec of buffering. This is quite high, and you may experience substantial disruption to your network performance when performing interactive tasks such as web-surfing while simultaneously conducting large downloads. With such a buffer, real-time applications such as games or audio chat can work quite poorly when conducting large downloads at the same time.

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+

Unrestricted domain DNS lookup (?): OK+

Direct DNS support (?): OK+

Direct EDNS support (?): OK+

DNS resolver address (?): OK+

DNS resolver properties (?): Lookup latency 64ms+

Direct probing of DNS resolvers (?)–

Your system is configured to use 2 DNS resolver(s).

The resolver at 192.168.1.1 could not process the following tested types:

• Medium (~1300B) TXT records
• Large (~3000B) TXT records
• Large (~3000B) TXT records fetched with EDNS0

It does not validate DNSSEC. It wildcards NXDOMAIN errors. Instead of an error it returns the following IP address(es): 63.251.179.13, 8.15.7.117. The resolver reports a number of additional properties. Show them.

The resolver at 68.238.96.12 can process all tested types. It does not validate DNSSEC. It wildcards NXDOMAIN errors. Instead of an error it returns the following IP address(es): 63.251.179.13, 8.15.7.117. The resolver reports a number of additional properties. Show them.

DNS glue policy (?): OK+

DNS resolver port randomization (?): OK+

DNS lookups of popular domains (?): OK+

DNS external proxy (?): OK+

DNS results wildcarding (?): Warning–

Your ISP’s DNS server returns IP addresses even for domain names which should not resolve. Instead of an error, the DNS server returns an address of 63.251.179.13, which does not resolve. You can inspect the resulting HTML content here.

There are several possible explanations for this behavior. The most likely cause is that the ISP is attempting to profit from customer’s typos by presenting advertisements in response to bad requests, but it could also be due to an error or misconfiguration in the DNS server.

The big problem with this behavior is that it can potentially break any network application which relies on DNS properly returning an error when a name does not exist.

The following lists your DNS server’s behavior in more detail.

• www.{random}.com is mapped to 63.251.179.13.
• www.{random}.org is mapped to 8.15.7.117.
• fubar.{random}.com is correctly reported as an error.
• www.yahoo.cmo [sic] is mapped to 63.251.179.13.
• nxdomain.{random}.netalyzr.icsi.berkeley.edu is correctly reported as an error.

DNS-level redirection of specific sites (?): OK+

Direct probing of DNS roots (?):+

IPv6 Tests+  –

DNS support for IPv6 (?): OK+

IPv4, IPv6, and your web browser (?): No IPv6 support+

IPv6 connectivity (?): No IPv6 support+