Welcome to the Forum Archive!

Years of conversation fill a ton of digital pages, and we've kept all of it accessible to browse or copy over. Whether you're looking for reveal articles for older champions, or the first time that Rammus rolled into an "OK" thread, or anything in between, you can find it here. When you're finished, check out the boards to join in the latest League of Legends discussions.

GO TO BOARDS


Failed to connect, was fine earlier.. please help

12
Comment below rating threshold, click here to show it.

Blue Phoenix

Member

03-29-2010

Well, I just did. Netalyzr said "OK" for every test he did.

Quote:
Address-based Tests +
NAT detection (?): NAT Detected
DNS-based host information (?): OK

Reachability Tests +
TCP connectivity (?): OK
UDP connectivity (?): OK
Path MTU (?): Not Executed
Network Access Link Properties +
Network latency measurements (?): Prohibited
TCP connection setup latency (?): 220ms
Network background health measurement (?): Not Executed
Network bandwidth measurements (?): Not Executed
Network buffer measurements (?): Not Executed

HTTP Tests +
Address-based HTTP proxy detection (?): OK
Header-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 EDNS support (?): Not Executed
DNS resolver address (?): OK
DNS resolver properties (?): Lookup latency: 260ms
DNS glue policy (?): OK
DNS resolver port randomization (?): OK
DNS lookups of popular domains (?): OK
DNS external proxy (?): Not Executed
DNS results wildcarding (?): OK

Host Properties +
System clock accuracy (?): Not Executed
Browser properties (?): OK
Uploaded Data (?): OK


Comment below rating threshold, click here to show it.

Blue Phoenix

Member

03-30-2010

I thought there could be some problem with LoL Client specific UDP port so I've put my PC's IP as DMZ on router, what means that ALL ports are Open. And yes, I tested, they are really opened. But still, nothing changed, the LoL client doesn't connect (or reconnect) to the game.


Comment below rating threshold, click here to show it.

Kovsky

Senior Member

03-30-2010

Just to keep feeding you with more info, the problem is still happening right now.

edit: for a couple of hours now, i've been able to play properly.

No Reverse Information / 187.60.68.186 Recorded at 04:49 EDT (08:49 UTC), Mar 30 2010. Permalink (http://netalyzr.icsi.berkeley.edu/restore/id=43ca253f-32441-3d161aaf-283a-46ce-8574). Client (http://n1.netalyzr.icsi.berkeley.edu/transcript/id=43ca253f-32441-3d161aaf-283a-46ce-8574/side=client)/server (http://n1.netalyzr.icsi.berkeley.edu/transcript/id=43ca253f-32441-3d161aaf-283a-46ce-8574/side=server) transcript.
Summary of Noteworthy Events – (http://javascript%3Cb%3E%3C/b%3E:toggle_cb%280%29;)
Minor Aberrations

  • We received unexpected and possibly dangerous results when looking up important names (http://n1.netalyzr.icsi.berkeley.edu/summary/id=43ca253f-32441-3d161aaf-283a-46ce-8574#DNSLookup)


Minor Aberrations


Address-based Tests + (http://javascript%3Cb%3E%3C/b%3E:toggle_cb%281%29;)
NAT detection (? (http://n1.netalyzr.icsi.berkeley.edu/info_nat_detect.html)): NAT Detected
Your global IP address is 187.60.68.186 while your local one is 10.0.0.12. 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.

DNS-based host information (? (http://n1.netalyzr.icsi.berkeley.edu/info_dns_hostinfo.html)): OK
You are not a Tor (http://www.torproject.org/) exit node for HTTP traffic.
You are not listed on any Spamhaus (http://www.spamhaus.org/) blacklists.
The SORBS DUHL (http://www.au.sorbs.net/faq/dul.shtml) believes you are using a statically assigned IP address.


NAT detection (? (http://n1.netalyzr.icsi.berkeley.edu/info_nat_detect.html)): NAT Detected

DNS-based host information (? (http://n1.netalyzr.icsi.berkeley.edu/info_dns_hostinfo.html)): OK


Reachability Tests + (http://javascript%3Cb%3E%3C/b%3E:toggle_cb%282%29;)
TCP connectivity (? (http://n1.netalyzr.icsi.berkeley.edu/info_tcp_connectivity.html)): OK
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 prohibited.
This means you cannot send email via SMTP to arbitrary mail servers. Such blocking is a common countermeasure against malware abusing infected machines for generating spam. Your ISP likely provides a specific mail server that is permitted. Also, webmail services remain unaffected.

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 allowed.
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.
UDP connectivity (? (http://n1.netalyzr.icsi.berkeley.edu/info_udp_connectivity.html)): OK
We are unable to deliver non-DNS UDP datagrams to our servers.
Possible reasons include a restrictive Java security policy, a blocking rule imposed by your firewall or personal firewall configuration, or filtering performed by your ISP. Although it means we cannot conduct the latency and bandwidth tests, it does not necessarily indicate a problem with your network.

Path MTU (? (http://n1.netalyzr.icsi.berkeley.edu/info_mtu.html)): Not Executed
The test was not executed. Required functionality was unavailable or not permitted.


TCP connectivity (? (http://n1.netalyzr.icsi.berkeley.edu/info_tcp_connectivity.html)): OK

UDP connectivity (? (http://n1.netalyzr.icsi.berkeley.edu/info_udp_connectivity.html)): OK

Path MTU (? (http://n1.netalyzr.icsi.berkeley.edu/info_mtu.html)): Not Executed


Network Access Link Properties + (http://javascript%3Cb%3E%3C/b%3E:toggle_cb%283%29;)
Network latency measurements (? (http://n1.netalyzr.icsi.berkeley.edu/info_latency.html)): Prohibited
The applet was not permitted to run this test in its entirety. We encourage you to re-run the applet, allowing it to conduct its tests if prompted. However, some system configurations will always block this test. See the corresponding FAQ (http://n1.netalyzr.icsi.berkeley.edu/faq.html#permissions) for help.
TCP connection setup latency (? (http://n1.netalyzr.icsi.berkeley.edu/info_tcp_latency.html)): 220ms
The time it takes your computer to set up a TCP connection with our server is 220 msec, which is good.
Network background health measurement (? (http://n1.netalyzr.icsi.berkeley.edu/info_burst_loss.html)): Not Executed
The test was not executed. Required functionality was unavailable or not permitted.
Network bandwidth measurements (? (http://n1.netalyzr.icsi.berkeley.edu/info_bandwidth.html)): Not Executed
The test was not executed. Required functionality was unavailable or not permitted.
Network buffer measurements (? (http://n1.netalyzr.icsi.berkeley.edu/info_buffer.html)): Not Executed
The test was not executed. Required functionality was unavailable or not permitted.


Network latency measurements (? (http://n1.netalyzr.icsi.berkeley.edu/info_latency.html)): Prohibited

TCP connection setup latency (? (http://n1.netalyzr.icsi.berkeley.edu/info_tcp_latency.html)): 220ms

Network background health measurement (? (http://n1.netalyzr.icsi.berkeley.edu/info_burst_loss.html)): Not Executed

Network bandwidth measurements (? (http://n1.netalyzr.icsi.berkeley.edu/info_bandwidth.html)): Not Executed

Network buffer measurements (? (http://n1.netalyzr.icsi.berkeley.edu/info_buffer.html)): Not Executed


HTTP Tests + (http://javascript%3Cb%3E%3C/b%3E:toggle_cb%284%29;)
Address-based HTTP proxy detection (? (http://n1.netalyzr.icsi.berkeley.edu/info_httpproxy_addr.html)): OK
There is no explicit sign of HTTP proxy use based on IP address.
Header-based HTTP proxy detection (? (http://n1.netalyzr.icsi.berkeley.edu/info_httpproxy_header.html)): OK
No HTTP header or content changes hint at the presence of a proxy.
HTTP proxy detection via malformed requests (? (http://n1.netalyzr.icsi.berkeley.edu/info_httpproxy_malformed.html)): OK
Deliberately malformed HTTP requests arrive at our server unchanged. Thus, the proxies along your path are able to transparently forward invalid HTTP traffic.
Filetype-based filtering (? (http://n1.netalyzr.icsi.berkeley.edu/info_content_filters.html)): OK
We did not detect file-content filtering.
HTTP caching behavior (? (http://n1.netalyzr.icsi.berkeley.edu/info_httpcache.html)): OK
There is no suggestion that a transparent HTTP cache exists in your network.
JavaScript-based tests (? (http://n1.netalyzr.icsi.berkeley.edu/info_javascript.html)): OK
The applet was not run from within a frame.
Your web browser reports the following cookies for our web page:
  • netAlizEd = BaR (set by our server)
  • netalyzrComplete = True (set by our server)
  • netalyzrStatus = running (set by our server)

Your web browser was unable to fetch an image using IPv6.


Address-based HTTP proxy detection (? (http://n1.netalyzr.icsi.berkeley.edu/info_httpproxy_addr.html)): OK

Header-based HTTP proxy detection (? (http://n1.netalyzr.icsi.berkeley.edu/info_httpproxy_header.html)): OK

HTTP proxy detection via malformed requests (? (http://n1.netalyzr.icsi.berkeley.edu/info_httpproxy_malformed.html)): OK

Filetype-based filtering (? (http://n1.netalyzr.icsi.berkeley.edu/info_content_filters.html)): OK

HTTP caching behavior (? (http://n1.netalyzr.icsi.berkeley.edu/info_httpcache.html)): OK

JavaScript-based tests (? (http://n1.netalyzr.icsi.berkeley.edu/info_javascript.html)): OK


DNS Tests – (http://javascript%3Cb%3E%3C/b%3E:toggle_cb%285%29;)
Restricted domain DNS lookup (? (http://n1.netalyzr.icsi.berkeley.edu/info_dns_restricted.html)): OK
We are able to successfully lookup 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 (? (http://n1.netalyzr.icsi.berkeley.edu/info_dns_unrestricted.html)): OK
We are able to successfully lookup arbitrary names from within the Java applet. This means we are able to conduct all test on your DNS server.
Direct EDNS support (? (http://n1.netalyzr.icsi.berkeley.edu/info_edns_connectivity.html)): Not Executed
The test was not executed. Required functionality was unavailable or not permitted.
DNS resolver address (? (http://n1.netalyzr.icsi.berkeley.edu/info_dns_resolver.html)): OK
The IP address of your ISP's DNS Resolver is 189.124.128.33, which resolves to ns2.supercabo.com.br.
DNS resolver properties (? (http://n1.netalyzr.icsi.berkeley.edu/info_dns_resolver_behavior.html)): Lookup latency: 260ms
Your ISP's DNS resolver requires 260 msec to conduct an external lookup, and 17 msec to lookup an item in the cache. It takes 240 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 4096 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 resolver respects a TTL of 0 seconds.
Your ISP's DNS resolver respects a TTL of 1 seconds.
No transport issues were discovered which could affect the deployment of DNSSEC
DNS glue policy (? (http://n1.netalyzr.icsi.berkeley.edu/info_dns_glue.html)): OK
Your ISP's DNS resolver does not accept generic additional (glue) records — good.
Your ISP's DNS resolver accepts additional (glue) records for nameservers located in subdomains of the queried domain.
Your ISP's DNS resolver does not follow CNAMEs.
DNS resolver port randomization (? (http://n1.netalyzr.icsi.berkeley.edu/info_dns_random.html)): 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 (? (http://n1.netalyzr.icsi.berkeley.edu/info_dnslookups.html)): Warning
1 popular name has a moderate anomaly: we are unable to find a reverse name associated with the IP address provided by your ISP's DNS server, although we expected to find a name. This is most likely due to a slow responding DNS server. If you rerun Netalyzr and see this condition remain, it could be due to a misconfiguration on the part of the domain owner or your DNS server could be misconfigured or enabling a Man-in-the-Middle attack.
Name IP Address Reverse Name/SOA wireless.att.com (http://wireless.att.com/) 135.209.168.22 X
77 of 77 popular names were resolved successfully. Show all names (http://javascript%3Cb%3E%3C/b%3E:toggle%28%29;). 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 www.abbey.co.uk (http://www.abbey.co.uk/) 165.160.15.20 X (pdns1.cscdns.net (http://pdns1.cscdns.net/)) ad.doubleclick.net (http://ad.doubleclick.net/) 64.233.163.148 bs-in-f148.1e100.net (http://bs-in-f148.1e100.net/) www.alliance-leicester.co.uk (http://www.alliance-leicester.co.uk/) 194.130.105.121 X (alice.ioko365.com (http://alice.ioko365.com/)) www.amazon.com (http://www.amazon.com/) 72.21.210.250 210-250.amazon.com (http://210-250.amazon.com/) www.bankofamerica.com (http://www.bankofamerica.com/) 171.159.193.173 www.bankofamerica.com (http://www.bankofamerica.com/) www.bankofscotland.co.uk (http://www.bankofscotland.co.uk/) 195.171.171.21 X (ns0.bt.net (http://ns0.bt.net/)) www.barclays.co.uk (http://www.barclays.co.uk/) 213.219.1.141 X (dns1.lon7.telecityredbus.net (http://dns1.lon7.telecityredbus.net/)) bit.ly (http://bit.ly/) 168.143.174.25 X (ns1.dn.net (http://ns1.dn.net/)) www.capitalone.com (http://www.capitalone.com/) 208.80.48.112 X (chia.arin.net (http://chia.arin.net/)) www.careerbuilder.com (http://www.careerbuilder.com/) 208.82.7.22 X (smokey.careerbuilder.com (http://smokey.careerbuilder.com/)) www.chase.com (http://www.chase.com/) 159.53.60.105 X (ns1.jpmorganchase.com (http://ns1.jpmorganchase.com/)) chaseonline.chase.com (http://chaseonline.chase.com/) 159.53.64.54 resources-cdc2.chase.com (http://resources-cdc2.chase.com/) www.citi.com (http://www.citi.com/) 192.193.103.222 citibank.com (http://citibank.com/) www.citibank.com (http://www.citibank.com/) 192.193.103.222 citibank.com (http://citibank.com/) www.citimortgage.com (http://www.citimortgage.com/) 192.193.218.222 citimortgage.com (http://citimortgage.com/) www.cnn.com (http://www.cnn.com/) 157.166.226.26 www.cnn.com (http://www.cnn.com/) www.desjardins.com (http://www.desjardins.com/) 142.195.132.100 www.desjardins.com (http://www.desjardins.com/) www.deutsche-bank.de (http://www.deutsche-bank.de/) 217.73.49.24 www.deutsche-bank.de (http://www.deutsche-bank.de/) www.e-gold.com (http://www.e-gold.com/) 209.200.169.10 unknown.prolexic.com (http://unknown.prolexic.com/) www.ebay.com (http://www.ebay.com/) 66.211.181.11 hp-core.ebay.com (http://hp-core.ebay.com/) www.etrade.com (http://www.etrade.com/) 198.93.34.21 www.etrade.com (http://www.etrade.com/) www.facebook.com (http://www.facebook.com/) 66.220.145.10 www-10-01.snc4.facebook.com (http://www-10-01.snc4.facebook.com/) www.fdic.gov (http://www.fdic.gov/) 192.147.69.84 www.fdic.gov (http://www.fdic.gov/) www.friendfinder.com (http://www.friendfinder.com/) 208.88.180.81 X (ii53-30.friendfinderinc.com (http://ii53-30.friendfinderinc.com/)) www.google.com (http://www.google.com/) 64.233.163.104 bs-in-f104.1e100.net (http://bs-in-f104.1e100.net/) www.halifax.co.uk (http://www.halifax.co.uk/) 212.140.245.97 www.halifax.co.uk (http://www.halifax.co.uk/) www.hsbc.co.uk (http://www.hsbc.co.uk/) 193.108.74.126 X (ns3.hsbc.com (http://ns3.hsbc.com/)) www.jpmorganchase.com (http://www.jpmorganchase.com/) 159.53.64.105 X (ns1.jpmorganchase.com (http://ns1.jpmorganchase.com/)) mail.google.com (http://mail.google.com/) 64.233.163.83 bs-in-f83.1e100.net (http://bs-in-f83.1e100.net/) mail.live.com (http://mail.live.com/) 64.4.20.169 dp2.mail.live.com (http://dp2.mail.live.com/) mail.yahoo.com (http://mail.yahoo.com/) 209.191.92.114 l2.login.vip.mud.yahoo.com (http://l2.login.vip.mud.yahoo.com/) www.mbna.com (http://www.mbna.com/) 209.135.59.10 X (ns1.usi.net (http://ns1.usi.net/)) www.mbna.net (http://www.mbna.net/) 209.135.59.10 X (ns1.usi.net (http://ns1.usi.net/)) www.meebo.com (http://www.meebo.com/) 74.114.28.110 X (ns1.meebo.com (http://ns1.meebo.com/)) messenger.yahoo.com (http://messenger.yahoo.com/) 68.142.194.14 myc1.msg.vip.mud.yahoo.com (http://myc1.msg.vip.mud.yahoo.com/) www.microsoft.com (http://www.microsoft.com/) 65.55.21.250 wwwco1vip.microsoft.com (http://wwwco1vip.microsoft.com/) www.nationwide.co.uk (http://www.nationwide.co.uk/) 155.131.31.10 X (ns0.nationet.net (http://ns0.nationet.net/)) www.networksolutions.com (http://www.networksolutions.com/) 205.178.187.13 www.networksolutions.com (http://www.networksolutions.com/) www.newegg.com (http://www.newegg.com/) 204.14.213.185 X (pdns1.ultradns.net (http://pdns1.ultradns.net/)) online.citibank.com (http://online.citibank.com/) 199.67.180.11 myciti.com (http://myciti.com/) online.wellsfargo.com (http://online.wellsfargo.com/) 151.151.13.132 psaltery-on.wellsfargo.com (http://psaltery-on.wellsfargo.com/) www.orange.fr (http://www.orange.fr/) 193.252.122.103 www.orange.fr.b2.fti.net (http://www.orange.fr.b2.fti.net/) partner.googleadservices.com (http://partner.googleadservices.com/) 64.233.163.164 bs-in-f164.1e100.net (http://bs-in-f164.1e100.net/) www.paypal.com (http://www.paypal.com/) 64.4.241.49 node-64-4-241-4[...]orks.paypal.com (http://node-64-4-241-49.networks.paypal.com/) www.postbank.de (http://www.postbank.de/) 62.153.105.37 X (ns1.postbank.de (http://ns1.postbank.de/)) www.rbs.co.uk (http://www.rbs.co.uk/) 155.136.80.222 X (ns0-08.dns.pipex.net (http://ns0-08.dns.pipex.net/)) www.schwab.com (http://www.schwab.com/) 162.93.237.80 wwwschwab-vip.schwab.com (http://wwwschwab-vip.schwab.com/) search.yahoo.com (http://search.yahoo.com/) 74.6.146.119 m1.search.vip.sk1.yahoo.com (http://m1.search.vip.sk1.yahoo.com/) www.sears.com (http://www.sears.com/) 96.7.169.99 a96-7-169-99.de[...]echnologies.com (http://a96-7-169-99.deploy.akamaitechnologies.com/) www.secureworks.com (http://www.secureworks.com/) 67.107.53.168 67.107.53.168.ptr.us.xo.net (http://67.107.53.168.ptr.us.xo.net/) smartzone.comcast.net (http://smartzone.comcast.net/) 76.96.26.12 webmail3.emeryv[...]ail.comcast.net (http://webmail3.emeryville.ca.mail.comcast.net/) www.smithbarney.com (http://www.smithbarney.com/) 192.193.20.126 X (ns.citicorp.com (http://ns.citicorp.com/)) www.sterlingsavingsbank.com (http://www.sterlingsavingsbank.com/) 12.19.55.215 sterlingsavingsbank.com (http://sterlingsavingsbank.com/) www.ticketmaster.com (http://www.ticketmaster.com/) 72.247.68.199 a72-247-68-199.[...]echnologies.com (http://a72-247-68-199.deploy.akamaitechnologies.com/) tinyurl.com (http://tinyurl.com/) 195.66.135.131 a.tinyurl.com (http://a.tinyurl.com/) www.torproject.org (http://www.torproject.org/) 38.229.70.16 vescum.torproject.org (http://vescum.torproject.org/) us.etrade.com (http://us.etrade.com/) 198.93.34.50 us.etrade.com (http://us.etrade.com/) www.usbank.com (http://www.usbank.com/) 170.135.216.181 epay.usbank.com (http://epay.usbank.com/) www.verisign.com (http://www.verisign.com/) 65.205.249.60 www.verisign.net (http://www.verisign.net/) www.wachovia.com (http://www.wachovia.com/) 169.200.89.101 X (sls-ns1.wachovia.com (http://sls-ns1.wachovia.com/)) www.wamu.com (http://www.wamu.com/) 159.53.62.63 X (ns1.jpmorganchase.com (http://ns1.jpmorganchase.com/)) www.wellsfargo.com (http://www.wellsfargo.com/) 151.151.13.133 psaltery-dd.wellsfargo.com (http://psaltery-dd.wellsfargo.com/) westernunion.com (http://westernunion.com/) 206.201.227.250 wumt1.westernunion.com (http://wumt1.westernunion.com/) windowsupdate.microsoft.com (http://windowsupdate.microsoft.com/) 207.46.225.221 X (msnhst.microsoft.com (http://msnhst.microsoft.com/)) www.yahoo.com (http://www.yahoo.com/) 200.152.168.178 ir1.fp.vip.br1.yahoo.com (http://ir1.fp.vip.br1.yahoo.com/)

7 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 (http://javascript%3Cb%3E%3C/b%3E:toggle2%28%29;). Name IP Address Reverse Name/SOA www.bing.com (http://www.bing.com/) 200.182.35.25 X (ns.embratel.net.br (http://ns.embratel.net.br/)) www.f-secure.com (http://www.f-secure.com/) 200.182.35.18 X (ns.embratel.net.br (http://ns.embratel.net.br/)) www.irs.gov (http://www.irs.gov/) 200.182.35.18 X (ns.embratel.net.br (http://ns.embratel.net.br/)) www.lloydstsb.com (http://www.lloydstsb.com/) 141.92.130.226 X (ns0.bt.net (http://ns0.bt.net/)) www.nordea.fi (http://www.nordea.fi/) 92.43.121.130 X (ns01.tdchosting.dk (http://ns01.tdchosting.dk/)) www.trendmicro.com (http://www.trendmicro.com/) 200.182.35.18 X (ns.embratel.net.br (http://ns.embratel.net.br/)) www.visa.com (http://www.visa.com/) 200.182.35.9 X (ns.embratel.net.br (http://ns.embratel.net.br/))

4 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 (http://javascript%3Cb%3E%3C/b%3E:toggle3%28%29;). Name IP Address Reverse Name/SOA www.ameritrade.com (http://www.ameritrade.com/) 204.58.27.97 X www.bankofthewest.com (http://www.bankofthewest.com/) 204.44.12.103 X www.sparkasse.de (http://www.sparkasse.de/) 212.34.69.3 X www.tdameritrade.com (http://www.tdameritrade.com/) 204.58.27.121 X

DNS external proxy (? (http://n1.netalyzr.icsi.berkeley.edu/info_dns_proxy.html)): Not Executed
The test was not executed. Required functionality was unavailable or not permitted.
DNS results wildcarding (? (http://n1.netalyzr.icsi.berkeley.edu/info_dns_wildcarding.html)): OK
Your ISP correctly leaves non-resolving names untouched.


Restricted domain DNS lookup (? (http://n1.netalyzr.icsi.berkeley.edu/info_dns_restricted.html)): OK

Unrestricted domain DNS lookup (? (http://n1.netalyzr.icsi.berkeley.edu/info_dns_unrestricted.html)): OK

Direct EDNS support (? (http://n1.netalyzr.icsi.berkeley.edu/info_edns_connectivity.html)): Not Executed

DNS resolver address (? (http://n1.netalyzr.icsi.berkeley.edu/info_dns_resolver.html)): OK

DNS resolver properties (? (http://n1.netalyzr.icsi.berkeley.edu/info_dns_resolver_behavior.html)): Lookup latency: 260ms

DNS glue policy (? (http://n1.netalyzr.icsi.berkeley.edu/info_dns_glue.html)): OK

DNS resolver port randomization (? (http://n1.netalyzr.icsi.berkeley.edu/info_dns_random.html)): OK

DNS lookups of popular domains (? (http://n1.netalyzr.icsi.berkeley.edu/info_dnslookups.html)): Warning

DNS external proxy (? (http://n1.netalyzr.icsi.berkeley.edu/info_dns_proxy.html)): Not Executed

DNS results wildcarding (? (http://n1.netalyzr.icsi.berkeley.edu/info_dns_wildcarding.html)): OK


Host Properties + (http://javascript%3Cb%3E%3C/b%3E:toggle_cb%286%29;)
System clock accuracy (? (http://n1.netalyzr.icsi.berkeley.edu/info_system_clock.html)): Not Executed
The test was not executed. Required functionality was unavailable or not permitted.
Browser properties (? (http://n1.netalyzr.icsi.berkeley.edu/info_browser_properties.html)): OK
The following parameters are sent by your web browser to all web sites you visit:
  • User Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; pt-BR; rv:1.9.2.2) Gecko/20100316 Firefox/3.6.2 (.NET CLR 3.5.30729)
  • Accept: text/html,application/xhtml+xml,application/xml; q=0.9,*/*; q=0.8
  • Accept Language: pt-br,pt;q=0.8,en-us;q=0.5,en;q=0.3
  • Accept Encoding: gzip,deflate
  • Accept Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Java identifies your operating system as Windows 7.
Uploaded Data (? (http://n1.netalyzr.icsi.berkeley.edu/info_upload.html)): OK
The following additional data was uploaded by the applet:
  • raw_http_content (http://n1.netalyzr.icsi.berkeley.edu/uploaded/id=43ca253f-32441-3d161aaf-283a-46ce-8574/key=raw_http_content/dummy=name.txt)



System clock accuracy (? (http://n1.netalyzr.icsi.berkeley.edu/info_system_clock.html)): Not Executed

Browser properties (? (http://n1.netalyzr.icsi.berkeley.edu/info_browser_properties.html)): OK

Uploaded Data (? (http://n1.netalyzr.icsi.berkeley.edu/info_upload.html)): OK


12