Berkeley's Netalyzer Diagnostic Tool

[FlyingPenguin]

Run the tool here: http://netalyzr.icsi.berkeley.edu/

Cool diagnostic tool that Steve Gibson discussed last week. Among the many things it does, it will show you exactly how much buffer upload & download latency you have, which is often caused by "buffer bloat" in the gateway router (this was the topic of his Security Now podcast last week and was VERY interesting).

In my case I have a substantially high upload buffer latency. Apparently this is common among Comcast users, and not necessarily due to my router (I'm using DD-WRT) which is why I can't play an online while downloading a file, even if that download isn't saturating the bandwidth.

Also helped diagnose an issue I've had with DNS. The TCP/IP stack on my workstation thought I had 4 DNS servers (2 for OpenDNS which is what it's supposed to be) and 2 for Google. Turned out it was due to the network connection for EasyTether (which I have installed on my workstation so I can tether to my phone in case the cable goes out).

Lots of cool info you get from this diagnostic tool about your Internet connection. You can ignore the warnings about Ports 135, 139 & 445 as these ports SHOULD be blocked on the WAN.

On my results, I have a high upload buffer latency of 490msec.

I'd be curious if those of you on Comcast ALSO have a high upload latency.

[FlyingPenguin]

Hmmm... looks like DD-WRT allows you to change the size of your upload buffer. I'll have to experiment with this:

http://www.embracingchaos.com/2011/01/f ... d-wrt.html

[DaMaN]

upload buffer latency of 1100 ms, Downlink 120 ms. no bueno

[FlyingPenguin]

Ouch!

[wvjohn]

the only red stuff I get seems to be related to using open DNS which I switched to because the Frontier DNS servers blew dead rats.

any ideas from the gurus?



You appear to be using OpenDNS. OpenDNS, by default, deliberately returns addresses even for domain names which should not resolve. Instead of an error, the DNS server returns an address of 67.215.65.132, which resolves to hit-nxdomain.opendns.com. You can inspect the resulting HTML content here.

This is central to OpenDNS's business model. In order to support an otherwise free service, OpenDNS presents the users with advertisements whenever they make a typo in their web browser. You can disable this behavior through the OpenDNS Dashboard.

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 67.215.65.132.
* www.{random}.org is mapped to 67.215.65.132.
* fubar.{random}.com is mapped to 67.215.65.132.
* http://www.yahoo.cmo [sic] is mapped to 67.215.65.132.
* nxdomain.{random}.netalyzr.icsi.berkeley.edu is mapped to 67.215.65.132.

Another problem with the DNS server is its response to a server failure. Instead of properly returning an error when it cannot contact the DNS authority, the DNS server returns an address of 67.215.66.132. Since transient failures are quite common this can be significantly disruptive, turning a transient failure into a wrong answer without any notification to the application doing the name lookup.

The DNS resolver you are using deliberately manipulates results. This can prove problematic, as you will be unable to contact an IPv6-only site: the DNS resolver is giving incorrect results for a system which has only an IPv6 address. We expected the applet to only receive cafe:babe:66:0:0:0:0:1 (an IPv6 address), instead it received the following address: 67.215.65.132.
Your DNS resolver is not on Google's IPv6 "whitelist", which means that Google does not enable IPv6 access to their services for you.

Edit: I switched over to the Frontier DNS servers and all the red stuff went away. Still got some brown stuff, and my clock is 37 seconds slow.lol. I'll see how it goes with the frontier dns.

[FlyingPenguin]

JOHN: I use OpenDNS and I didn't get that error. I think it's because I actually have a free account with OpenDNS and have disabled that feature. I don't get redirected when I enter an non-existent domain name - I get a normal browser error when a name doesn't exist.

HOWEVER I also think the authors are being overly critical. Almost ALL ISPs now redirect you when you try to go to a non-existent domain name. I'm not aware of anything that will be broken by that. ALL my clients use OpenDNS.

I wouldn't worry about it but if it concerns you, setup a free account with them and dig into the settings to disable that feature. You could also use Google's DNS servers which are also fast and also give you some protection from malicious web sites. Those DNS servers are 8.8.8.8 and 8.8.4.4

I also wouldn't worry about IPv6-only sites. In all likelihood there never will be an IPv6 only site. The transition to IPv6 will involve sites have both IPv4 and IPv6 addresses, or it just won't work. We're also still a LONG way off from that... assuming it ever actually happens. For one thing, there are practically no consumer grade IPv6 routers or modems yet.

[renovation]

Summary of Noteworthy Events + + – – Minor Aberrations –
Certain TCP protocols are blocked in outbound traffic
Network packet buffering may be excessive

Minor Aberrations +
Address-based Tests + + – – NAT detection (?): NAT Detected +
Your global IP address is 107.5.200.92 while your local one is 192.168.1.100. You are behind a NAT. Your local address is in unroutable address space.

Your machine numbers TCP source ports sequentially. The following graph shows connection attempts on the X-axis and their corresponding source ports used by your computer on the Y-axis.



TCP ports are not renumbered by the network.

NAT detection (?): NAT Detected +
Local Network Interfaces (?): OK +
Your computer reports the following network interfaces, with the following IP addresses for each one:
eth0: (an ethernet interface)
192.168.113.1 [MICHAELS-SVADFA] (a private IPv4 address)
eth1: (an ethernet interface)
192.168.203.1 [MICHAELS-SVADFA] (a private IPv4 address)
eth2: (an ethernet interface)
192.168.1.100 (a private IPv4 address)
lo: (a local loopback interface)
127.0.0.1 [localhost] (an IPv4 loopback address)

Local Network Interfaces (?): OK +
DNS-based host information (?): OK +
You are not a Tor exit node for HTTP traffic. You are listed on the Spamhaus Policy Based Blacklist, meaning that your provider has designated your address block as one that should only be sending authenticated email, email through the ISP's mail server, or using webmail. The SORBS DUHL believes you are using a statically assigned IP address.
DNS-based host information (?): OK +
NAT support for Universal Plug and Play (UPnP) (?): Yes +
We received UPnP responses from one device:
192.168.1.1: this device provided a valid device description via its UPnP URL. This description, viewable here, contains the following information about this gateway:
Name: appletree
Manufacturer: Cisco
Manufacturer URL: http://www.myciscohome.com
Model name: Linksys Series Router E1500
Model number: E1500
Model URL: http://www.linksys.com/support/E1500
Model Description: Internet Access Server

NAT support for Universal Plug and Play (UPnP) (?): Yes +
Reachability Tests + + – – TCP connectivity (?): Note –
Direct TCP connections to remote FTP servers (port 21) failed.

This is commonly due to how a NAT or firewall handles FTP traffic, as FTP causes unique problems when developing NATs and firewalls.
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 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 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.
TCP connectivity (?): Note +
UDP connectivity (?): OK +
Basic UDP access is available.
The applet was able to send fragmented UDP traffic.

The applet was able to receive fragmented UDP traffic.
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 blocked. 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.
UDP connectivity (?): OK +
Traceroute (?): OK +
It takes 16 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.2 (0 ms)
ip-10-1-8-1.ec2.internal (0 ms)
ip-10-1-9-14.ec2.internal (0 ms)
216.182.232.48 (0 ms)
72.21.222.146 (50 ms)
72.21.220.124 (2 ms)
xe-7-0-0.edge2.Washington1.Level3.net (2 ms)
vlan80.csw3.Washington1.Level3.net (21 ms)
ae-81-81.ebr1.Washington1.Level3.net (3 ms)
ae-5-5.ebr2.Washington12.Level3.net (7 ms)
ae-2-52.edge2.Washington12.Level3.net (2 ms)
COMCAST-IP.edge2.Washington12.Level3.net (3 ms)
pos-0-14-0-0-ar01.taylor.mi.michigan.comcast.net (17 ms)
te-9-1-ur02.walledlake.mi.michigan.comcast.net (18 ms)
68.85.218.146 (33 ms)
*

Traceroute (?): OK +
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.
Path MTU (?): OK +
Network Access Link Properties + + – – Network latency measurements (?): Latency: 18ms Loss: 0.0% +
The round-trip time (RTT) between your computer and our server is 18 msec, which is good. We recorded no packet loss between your system and our server.
Network latency measurements (?): Latency: 18ms Loss: 0.0% +
TCP connection setup latency (?): 33ms +
The time it takes your computer to set up a TCP connection with our server is 33 msec, which is good.
TCP connection setup latency (?): 33ms +
Network background health measurement (?): no transient outages +
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 no such outages.
Network background health measurement (?): no transient outages +
Network bandwidth (?): Upload 540 Kbit/sec, Download 14 Mbit/sec +
Your Uplink: We measured your uplink's sending bandwidth at 540 Kbit/sec. This level of bandwidth works well for many users. Your Downlink: We measured your downlink's receiving bandwidth at 14 Mbit/sec. This level of bandwidth works well for many users.
During this test, the applet observed 27 reordered packets.
Network bandwidth (?): Upload 540 Kbit/sec, Download 14 Mbit/sec +
Network buffer measurements (?): Uplink 650 ms, Downlink is good –
We estimate your uplink as having 650 msec of buffering. This level can in some situations prove somewhat high, and you may experience degraded performance when performing interactive tasks such as web-surfing while simultaneously conducting large uploads. Real-time applications, such as games or audio chat, may also work poorly when conducting large uploads at the same time. We were not able to produce enough traffic to load the downlink buffer, or the downlink buffer is particularly small. You probably have excellent behavior when downloading files and attempting to do other tasks.
Network buffer measurements (?): Uplink 650 ms, Downlink is good +
HTTP Tests + + – – Address-based HTTP proxy detection (?): OK +
We detected no explicit sign of HTTP proxy via IP address changes.
Address-based HTTP proxy detection (?): OK +
Content-based HTTP proxy detection (?): OK +
No HTTP header or content changes hint at the presence of a proxy.
Content-based HTTP proxy detection (?): OK +
HTTP proxy detection via malformed requests (?): OK +
Deliberately malformed HTTP requests arrive at our server unchanged. We are not able to detect a proxy along the path to our server using this method.
HTTP proxy detection via malformed requests (?): OK +
Filetype-based filtering (?): OK +
We did not detect file-content filtering.
Filetype-based filtering (?): OK +
HTTP caching behavior (?): OK +
We detected no signs of a transparent HTTP cache in your network path.
HTTP caching behavior (?): OK +
JavaScript-based tests (?): OK +
The applet did not execute within a frame. Your web browser reports the following cookies for our web page:
netAlizEd = BaR (set by our server)
netalyzrStatus = running (set by our server)
Your web browser was unable to fetch an image using IPv6.
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.
Restricted domain DNS lookup (?): OK +
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.
Unrestricted domain DNS lookup (?): OK +
Direct DNS support (?): OK +
All tested DNS types were received OK.
Direct DNS support (?): OK +
Direct EDNS support (?): OK +
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 are answered successfully.
Direct EDNS support (?): OK +
DNS resolver address (?): OK +
The IP address of your ISP's DNS Resolver is 68.87.77.141, which resolves to detr-dnssec01b.westlandrdc.mi.michigan.comcast.net. Additional nameservers observed for your host: 76.96.17.155, 76.96.17.152, 76.96.17.153.
DNS resolver address (?): OK +
DNS resolver properties (?): Lookup latency 150ms +
Your ISP's DNS resolver requires 150 msec to conduct an external lookup. It takes 100 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 requests DNSSEC records. Your DNS resolver advertises the ability to accept DNS packets of up to 4000 bytes. Your DNS resolver can successfully receive a smaller (~1400 byte) DNS response. Your DNS resolver can successfully receive a large (>1500 byte) DNS response. 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 is capable of fetching records using IPv6. No transport problems were discovered which could affect the deployment of DNSSEC.
DNS resolver properties (?): Lookup latency 150ms +
Direct probing of DNS resolvers (?) +
Your system is configured to use 2 DNS resolver(s). The resolver at 75.75.76.76 can process all tested types. It validates DNSSEC. It does not wildcard NXDOMAIN errors. The resolver reports a number of additional properties. Show them.
Version: Nominum Vantio 4.4.1.1
The resolver at 75.75.75.75 can process all tested types. It validates DNSSEC. It does not wildcard NXDOMAIN errors. The resolver reports a number of additional properties. Show them.
Version: Nominum Vantio 4.4.1.1

Direct probing of DNS resolvers (?): +
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 glue policy (?): OK +
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 resolver port randomization (?): OK +
DNS lookups of popular domains (?): OK +
90 of 90 popular names were resolved successfully. Show all names.
In the following table reverse lookups that failed but for which a Start Of Authority (SOA) entry indicated correct name associations are shown using an "X", followed by the SOA entry. Absence of both IP address and reverse name indicates failed forward lookups. Name IP Address Reverse Name/SOA
6park.com 74.55.98.186 ba.62.374a.st[...]theplanet.com
http://www.6park.com 74.55.98.186 ba.62.374a.st[...]theplanet.com
http://www.abbey.co.uk 165.160.15.20 X (pdns1.cscdns.net)
ad.doubleclick.net 74.125.225.60 ord08s06-in-f28.1e100.net
http://www.amazon.com 72.21.214.128 X (dns-external-master.amazon.com)
http://www.ameritrade.com 216.105.251.222 kcg.tdameritrade.com
appspot.com 209.85.145.141 cbf02m01-in-f141.1e100.net
http://www.bankofamerica.com 171.159.100.173 X (primarydmz.bankofamerica.com)
http://www.bankofscotland.co.uk 195.171.220.92 bankofscotland.co.uk
http://www.blogimg.jp 125.6.190.4 125-6-190-4.data-hotel.net
blogpark.jp 125.6.146.13 125-6-146-13.data-hotel.net
http://www.capitalone.com 208.80.48.112 X (z.arin.net)
http://www.careerbuilder.com 208.82.6.22 http://www.careerbuilder.com
http://www.chase.com 159.53.64.105 X (ns1.jpmorganchase.com)
chaseonline.chase.com 159.53.64.54 resources-cdc2.chase.com
http://www.citi.com 192.193.103.222 citibank.com
http://www.citibank.com 192.193.103.222 citibank.com
http://www.citimortgage.com 192.193.103.118 citimortgage.com
http://www.desjardins.com 142.195.132.100 http://www.desjardins.com
http://www.ebay.com 66.211.181.181 http://www.ebay.com
encrypted.google.com 74.125.225.33 ord08s06-in-f1.1e100.net
http://www.etrade.com 12.153.224.22 origin-www.etrade.com
http://www.f-secure.com 184.28.90.32 a184-28-90-32.d[...]echnologies.com
http://www.facebook.com 69.171.247.64 www-13-03-frc1.facebook.com
http://www.fdic.gov 192.147.69.84 http://www.fdic.gov
http://www.friendfinder.com 208.88.180.81 X (ii53-30.friendfinderinc.com)
http://www.google.com 74.125.45.105 yx-in-f105.1e100.net
http://www.google-analytics.com 74.125.225.35 ord08s06-in-f3.1e100.net
http://www.halifax.co.uk 195.171.195.140 http://www.halifax.co.uk
hootsuite.com 184.73.216.15 ec2-184-73-216-[...]1.amazonaws.com
http://www.hsbc.co.uk 193.108.74.126 X (ns3.hsbc.com)
http://www.irs.gov 23.3.108.127 a23-3-108-127.d[...]echnologies.com
http://www.jpmorganchase.com 159.53.60.105 X (ns1.jpmorganchase.com)
mail.google.com 74.125.225.53 ord08s06-in-f21.1e100.net
mail.live.com 65.55.255.17 blumsg1100106.v[...]ssenger.msn.com
mail.yahoo.com 98.139.241.94 l1.login.vip.bf1.yahoo.com
http://www.meebo.com 208.81.191.110 http://www.meebo.com
messenger.yahoo.com 98.139.200.98 myc1.msg.vip.bf1.yahoo.com
http://www.microsoft.com 207.46.19.254 X (msnhst.microsoft.com)
http://www.nationwide.co.uk 155.131.127.82 X (ns0.nationet.net)
http://www.networksolutions.com 205.178.187.13 http://www.networksolutions.com
http://www.newegg.com 204.14.213.185 X (pdns1.ultradns.net)
online.wellsfargo.com 151.151.88.55 online.wellsfargo.com
http://www.orange.fr 193.252.122.103 http://www.orange.fr.b2.fti.net
partner.googleadservices.com 74.125.225.154 ord08s09-in-f26.1e100.net
http://www.paypal.com 66.211.169.2 X (crocodile.ebay.com)
http://www.postbank.de 195.50.155.39 X (ns1.postbank.de)
http://www.rbs.co.uk 155.136.80.222 X (ns0-08.dns.pipex.net)
http://www.schwab.com 162.93.217.34 schwab.co.uk
search.yahoo.com 74.6.238.254 syc.search.vip.ac2.yahoo.com
http://www.sears.com 23.13.153.99 a23-13-153-99.d[...]echnologies.com
smartzone.comcast.net 76.96.58.12 webmail3.westch[...]ail.comcast.net
http://www.smithbarney.com 192.193.20.126 X (ns.citicorp.com)
http://www.tdameritrade.com 216.105.251.204 X (mike.lynn.tdameritrade.com)
thepiratebay.org 194.71.107.50 X (ns0.thepiratebay.org)
http://www.thepiratebay.org 194.71.107.50 X (ns0.thepiratebay.org)
http://www.ticketmaster.com 23.13.148.199 a23-13-148-199.[...]echnologies.com
http://www.twitpic.com 50.23.200.238 50.23.200.238-s[...]e.softlayer.com
http://www.twitter.com 199.59.149.198 www2.twitter.com
us.etrade.com 12.153.224.21 us.etrade.com
http://www.usbank.com 170.135.216.181 artown.usbank.com
http://www.verisign.com 69.58.181.89 www-ilg.verisign.net
http://www.visa.com 23.3.108.109 a23-3-108-109.d[...]echnologies.com
http://www.wamu.com 159.53.116.2 X (ns1.jpmorganchase.com)
http://www.wellsfargo.com 159.45.2.68 mn2-web-pfp-ww.wellsfargo.com
westernunion.com 206.201.228.250 http://www.wuagentlink.com
windowsupdate.microsoft.com 65.55.13.91 X (msnhst.microsoft.com)
wireless.att.com 135.209.168.22 origin-b2b-al[...]eless.att.com
http://www.yahoo.com 98.139.183.24 ir2.fp.vip.bf1.yahoo.com
http://www.youtube.com 74.125.225.78 ord08s07-in-f14.1e100.net
18 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.
Name IP Address Reverse Name/SOA
http://www.alliance-leicester.co.uk 194.130.105.121 X (ns1.ioko.com)
http://www.barclays.co.uk 157.83.107.4 X (nsm1.barcap.com)
http://www.bing.com 23.15.9.161 a23-15-9-161.de[...]echnologies.com
bit.ly 69.58.188.39 X (ns1.verisign-grs.net)
http://www.cnn.com 157.166.255.19 X (ns1.timewarner.net)
http://www.deutsche-bank.de 160.83.8.24 pbc.tec.db.com
http://www.e-gold.com 24.173.168.101 rrcs-24-173-16[...].se.biz.rr.com
http://www.lloydstsb.com 141.92.130.226 X (ns0.bt.net)
http://www.mbna.com 206.17.87.35 X (xbru.br.ns.els-gms.att.net)
http://www.mbna.net 63.236.19.66 X (ns0.teb.qwest.net)
http://www.nordea.fi 92.43.121.130 X (ns01.tdchosting.dk)
online.citibank.com 23.13.180.106 a23-13-180-106.[...]echnologies.com
http://www.secureworks.com 216.52.89.170 X (ns1.nym.pnap.net)
http://www.sparkasse.de 212.34.69.3 rev-212.34.69.3.rev.izb.net
tinyurl.com 64.62.243.89
http://www.torproject.org 38.229.72.16
http://www.trendmicro.com 184.84.229.214 a184-84-229-214[...]echnologies.com
http://www.wachovia.com 151.151.88.100 az1-wachovia-p[...]wellsfargo.com
2 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.
Name IP Address Reverse Name/SOA
http://www.bankofthewest.com 204.44.12.103 X
http://www.sterlingsavingsbank.com 12.69.145.232 X

DNS lookups of popular domains (?): OK +
DNS external proxy (?): OK +
Your host ignores external DNS requests.
DNS external proxy (?): OK +
DNS results wildcarding (?): OK +
Your ISP correctly leaves non-resolving names untouched.
DNS results wildcarding (?): OK +
DNS-level redirection of specific sites (?): OK +
Your ISP does not appear to be using DNS to redirect traffic for specific websites.
DNS-level redirection of specific sites (?): OK +
Direct probing of DNS roots (?) +
We checked which DNS root server instances your computer can reach. All root servers responded. Show them.
Name IP Address Reported Name
a.root-servers.net 198.41.0.4 ans11-lax2
b.root-servers.net 192.228.79.201 b2
c.root-servers.net 192.33.4.12 iad1b.c.root-servers.org
d.root-servers.net 128.8.10.90 css-d.net.umd.edu
e.root-servers.net 192.203.230.10 e-01.bos.comcast.pch.net
f.root-servers.net 192.5.5.241 phl1a.f.root-servers.org
g.root-servers.net 192.112.36.4 g.root-servers-eur1-1.net
h.root-servers.net 128.63.2.53 H3
i.root-servers.net 192.36.148.17 s1.lnx
j.root-servers.net 192.58.128.30 jluepe1-eltor1
k.root-servers.net 193.0.14.129 k2.linx.k.ripe.net
l.root-servers.net 199.7.83.42 phl01.l.root-servers.org
m.root-servers.net 202.12.27.33 M-CDG-1

Direct probing of DNS roots (?): +
IPv6 Tests + + – – DNS support for IPv6 (?): OK +
Your system does not look up IPv6 addresses by default. Your DNS resolver is not on Google's IPv6 "whitelist", which means that Google does not enable IPv6 access to their services for you.
DNS support for IPv6 (?): OK +
IPv4, IPv6, and your web browser (?): No IPv6 support +
Your browser was unable to fetch a test image from an IPv6-only server. IPv4 performance to our IPv4-only server did not differ substantially from our IPv4/IPv6 dual-stacked one.
IPv4, IPv6, and your web browser (?): No IPv6 support +
IPv6 connectivity (?): No IPv6 support +
Your system appears to have no IPv6 connectivity as it was unable to look up the IPv6 address associated with our IPv6 test server.
IPv6 connectivity (?): No IPv6 support +
Host Properties + + – – System clock accuracy (?): OK +
Your computer's clock agrees with our server's clock.
System clock accuracy (?): OK +
Browser properties (?): OK +
Your web browser sends the following parameters to all web sites you visit:
User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; InfoPath.3; .NET4.0C; BRI/2; .NET4.0E)
Accept: image/gif, image/jpeg, image/pjpeg, image/pjpeg, application/x-shockwave-flash, application/x-icq, application/xaml+xml, application/vnd.ms-xpsdocument, application/x-ms-xbap, application/x-ms-application, application/vnd.ms-excel, application/msword, application/vnd.ms-powerpoint, */*
Accept Language: en-us
Accept Encoding: gzip, deflate
Accept Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Java identifies your operating system as Windows XP.
Browser properties (?): OK +
Uploaded data (?): OK +
The applet uploaded the following additional content:
apache_404
custom_404
plain_404
raw_http_content
upnp_0_descr
upnp_0_details

Uploaded data (?): OK +
Feedback + + – – User-provided 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-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:

User-provided feedback +

[renovation]

FP the results above were on comcast so you can see !

[FlyingPenguin]

HOW TO KEEP FROM SATURATING YOUR BANDWIDTH:

There's been a lot of discussion on buffer bloat in forums and on podcasts like Security Now, lately. Buffer bloat manifests itself when someone in the house or office is doing a large download or upload, and everyone else's broadband goes to hell.

Happens to me all the time because I have to upload files via FTP. Even though I'm not actually using all my available upload bandwidth, and virtually none of the download, web pages load slowly during the FTP upload.

Those of you who play online games have experienced this as well: a torrent download one PC can make online gaming impossible on another without extreme lag.

One of the way of fixing this is to limit your routers upload and download speeds to 80% - 95% of your actual upload and download bandwidth. This may seem counter-intuitive: You're getting less bandwidth, but in actuality it greatly helps. I've been doing some testing and have been amazed how much it helps.

Most routers have QoS settings that let you do this. My router is a Linksys 54G running DD-WRT firmware, and I have a QoS setting that was originally disabled. I set my upload cap to 3300 kpbs (80% of 4000) and my download to 4800 kbps (80% of 6000 kpbs).

So far it SEEMS to be helping. I'll just have to see how it works over time. I'll probably slowly raise these numbers closer to 90% and experiment with them.

Just make sure you use numbers based on your ACTUAL bandwidth and not inflated numbers that come from tests that see things like Comcast's Speed Boost.

I like these two tests because they ignore Speed Boost:
http://www.auditmypc.com/broadband-speed-test.asp

http://www.wugnet.com/myspeed/speedtest.asp

[FlyingPenguin]

HMMMM... mixed bag here. Netalyzer says my upload latency went UP from 500 msec to 3000 msec with QoS on. Not sure if that's valid or just Netalyzer mis-reading things because it's being affected by QoS?

Like I said, need to just use it with these settings a while and see if it seems to help.