Okay tak for det. Men det gav mig en masse bogstaver og tal som jeg ikke fatter overhovedet:)
Summary of Noteworthy Events –
Minor Aberrations
* Certain TCP protocols are blocked in outbound traffic
* Network packet buffering may be excessive
* Virus filtering appears to be present on your host or network
* Your computer's clock is slightly slow
Minor Aberrations
Address-based Tests +
NAT detection (?): NAT Detected
Your global IP address is 80.164.23.232 while your local one is 192.168.1.101. 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.
port sequence plot
The NAT or some other process renumbers TCP ports. The following graph shows connection attempts on the X-axis and their corresponding source ports on the Y-axis as seen by our server.
port sequence plot
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 dynamically assigned IP address.
NAT detection (?): NAT Detected
DNS-based host information (?): OK
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 connections to remote POP3 servers (port 110) succeed, but do not receive the expected content.
The applet received the following reply instead of our expected header:
"-ERR AVG POP3 Proxy Server: Cannot connect to the mail server! "
Direct TCP access to remote RPC servers (port 135) is allowed.
Direct TCP access to remote NetBIOS servers (port 139) is allowed.
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 (?): 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 OpenVPN servers (port 1194) is allowed.
Direct UDP access to remote MSSQL servers (port 1434) is allowed.
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.
TCP connectivity (?): Note
UDP connectivity (?): OK
Path MTU (?): OK
Network Access Link Properties –
Network latency measurements (?): Latency: 110ms Loss: 0.0%
The round-trip time (RTT) between your computer and our server is 110 msec, which is good.
We recorded no packet loss between your system and our server.
TCP connection setup latency (?): 120ms
The time it takes your computer to set up a TCP connection with our server is 120 msec, which is good.
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 bandwidth measurements (?): Upload 440 Kbit/sec, Download 3.4 Mbit/sec
Your Uplink: We measured your uplink's sending bandwidth at 440 Kbit/sec. This level of bandwidth works well for many users.
Your Downlink: We measured your downlink's receiving bandwidth at 3.4 Mbit/sec. This level of bandwidth works well for many users.
Network buffer measurements (?): Uplink 2400 ms, Downlink 440 ms
We estimate your uplink as having 2400 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 uploads. With such a buffer, real-time applications such as games or audio chat can work quite poorly when conducting large uploads at the same time.
We estimate your downlink as having 440 msec of buffering. This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic.
Network latency measurements (?): Latency: 110ms Loss: 0.0%
TCP connection setup latency (?): 120ms
Network background health measurement (?): no transient outages
Network bandwidth measurements (?): Upload 440 Kbit/sec, Download 3.4 Mbit/sec
Network buffer measurements (?): Uplink 2400 ms, Downlink 440 ms
HTTP Tests –
Address-based HTTP proxy detection (?): OK
There is no explicit sign of HTTP proxy use based on IP address.
Header-based HTTP proxy detection (?): OK
No HTTP header or content changes hint at the presence of a proxy.
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.
Filetype-based filtering (?): Note
Files of type exe remain unmodified by the network.
Files of type mp3 remain unmodified by the network.
Files of type torrent remain unmodified by the network.
A test "virus" (the benign EICAR test file that antivirus vendors recognize as a test) was blocked or modified in transit.
HTTP caching behavior (?): OK
There is no suggestion that a transparent HTTP cache exists in your network.
JavaScript-based tests (?): 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)
Your web browser was unable to fetch an image using IPv6.
Address-based HTTP proxy detection (?): OK
Header-based HTTP proxy detection (?): OK
HTTP proxy detection via malformed requests (?): OK
Filetype-based filtering (?): Note
HTTP caching behavior (?): OK
JavaScript-based tests (?): OK
DNS Tests +
Restricted domain DNS lookup (?): 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 (?): 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 (?): 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.
DNS resolver address (?): OK
The IP address of your ISP's DNS Resolver is 193.162.153.170, which resolves to ns3r2.inet.tele.dk. Additional nameservers observed for your host: 193.162.153.171, 193.162.153.162
DNS resolver properties (?): Lookup latency: 200ms
Your ISP's DNS resolver requires 200 msec to conduct an external lookup.
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 NAT has a built in DNS proxy.
DNS glue policy (?): 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 (?): 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.
port sequence plot
DNS lookups of popular domains (?): OK
77 of 77 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
www.abbey.co.uk[...] 165.160.15.20 X (pdns1.cscdns.net)
ad.doubleclick.net 74.125.79.149 ey-in-f149.1e100.net
www.alliance-leicester.co.uk[...] 194.130.105.121 X (alice.ioko365.com)
www.amazon.com[...] 207.171.166.252 166-252.amazon.com
www.ameritrade.com[...] 204.58.27.113 beta-new.tdameritrade.com
www.bankofamerica.com[...] 171.161.161.173
www.bankofamerica.com[...]
www.bankofscotland.co.uk[...] 195.171.171.21 X (ns0.bt.net)
www.barclays.co.uk[...] 213.219.1.141 X (dns1.lon7.telecityredbus.net)
bit.ly 168.143.174.29 X (ns1.dn.net)
www.capitalone.com[...] 208.80.48.112 X (chia.arin.net)
www.chase.com[...] 159.53.60.105 X (ns1.jpmorganchase.com)
chaseonline.chase.com 159.53.52.105 X (ns1.jpmorganchase.com)
www.citi.com[...] 192.193.219.58 citibank.com
www.citibank.com[...] 192.193.219.58 citibank.com
www.citimortgage.com[...] 192.193.103.118 citimortgage.com
www.cnn.com[...] 157.166.226.26
www.cnn.com[...]
www.desjardins.com[...] 142.195.132.100
www.desjardins.com[...]
www.deutsche-bank.de[...] 217.73.49.24
www.deutsche-bank.de[...]
www.e-gold.com[...] 209.200.169.10 unknown.prolexic.com
www.ebay.com[...] 66.211.181.11 hp-core.ebay.com
www.etrade.com[...] 198.93.34.21
www.etrade.com[...]
www.f-secure.com[...] 195.215.37.39 a195-215-37-39.[...]echnologies.com
www.fdic.gov[...] 192.147.69.84
www.fdic.gov[...]
www.friendfinder.com[...] 208.88.180.81 X (ii53-30.friendfinderinc.com)
www.google.com[...] 74.125.79.99 ey-in-f99.1e100.net
www.halifax.co.uk[...] 212.140.245.97 halifax.co.uk
www.hsbc.co.uk[...] 193.108.74.126 X (ns3.hsbc.com)
www.irs.gov[...] 195.215.37.33 a195-215-37-33.[...]echnologies.com
www.jpmorganchase.com[...] 159.53.64.105 X (ns1.jpmorganchase.com)
mail.google.com 74.125.79.83 ey-in-f83.1e100.net
mail.live.com 64.4.20.186 dp4.mail.live.com
mail.yahoo.com 217.12.8.76 l1.login.vip.ukl.yahoo.com
www.mbna.com[...] 209.135.59.10 X (ns1.usi.net)
www.mbna.net[...] 209.135.59.10 X (ns1.usi.net)
www.meebo.com[...] 208.81.191.110 X (ns1.meebo.com)
messenger.yahoo.com 68.142.230.204 myc1.msg.vip.re2.yahoo.com
www.microsoft.com[...] 207.46.19.254 wwwbaytest2.microsoft.com
www.nationwide.co.uk[...] 155.131.31.82
www.nationwide.co.uk[...]
www.networksolutions.com[...] 205.178.187.13
www.networksolutions.com[...]
www.newegg.com[...] 216.52.208.185 X (pdns1.ultradns.net)
online.citibank.com 199.67.180.11 myciti.com
online.wellsfargo.com 151.151.13.132 psaltery-on.wellsfargo.com
www.orange.fr[...] 193.252.122.103
www.orange.fr.b2.fti.net[...]
partner.googleadservices.com 74.125.79.164 ey-in-f164.1e100.net
www.paypal.com[...] 64.4.241.33
www.paypal.co.nz[...]
www.postbank.de[...] 62.153.105.37 X (ns1.postbank.de)
www.rbs.co.uk[...] 155.136.80.222 X (ns0-08.dns.pipex.net)
www.schwab.com[...] 162.93.202.80 wwwschwab-vip.schwab.com
search.yahoo.com 72.30.186.249 m1.search.vip.ac2.yahoo.com
www.sears.com[...] 92.122.89.99 a92-122-89-99.d[...]echnologies.com
www.secureworks.com[...] 67.107.53.168 67.107.53.168.ptr.us.xo.net
smartzone.comcast.net 76.96.26.12 webmail3.emeryv[...]ail.comcast.net
www.smithbarney.com[...] 192.193.20.126 X (ns.citicorp.com)
www.sterlingsavingsbank.com[...] 12.19.55.215 sterlingsavingsbank.com
www.tdameritrade.com[...] 204.58.27.105 beta-new.tdameritrade.com
www.ticketmaster.com[...] 88.221.116.199 a88-221-116-199[...]echnologies.com
tinyurl.com 85.255.210.133 crp1.tinyurl.com
www.torproject.org[...] 86.59.21.36 byblos.torproject.org
us.etrade.com 12.153.224.21 us.etrade.com
www.usbank.com[...] 170.135.216.181 communications.usbank.com
www.verisign.com[...] 65.205.249.60
www.verisign.net[...]
www.visa.com[...] 195.215.37.55 a195-215-37-55.[...]echnologies.com
www.wachovia.com[...] 169.200.89.101 X (sls-ns1.wachovia.com)
www.wamu.com[...] 159.53.62.63 X (ns1.jpmorganchase.com)
www.wellsfargo.com[...] 151.151.13.133 psaltery-dd.wellsfargo.com
westernunion.com 206.201.227.250 wumt1.westernunion.com
windowsupdate.microsoft.com 207.46.225.221 X (msnhst.microsoft.com)
wireless.att.com 135.209.168.22 origin-b2b-al[...]eless.att.com
www.yahoo.com[...] 87.248.113.14 f1.us.
www.vip.ird.yahoo.com[...]
5 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
www.bing.com[...] 195.215.37.39 a195-215-37-39.[...]echnologies.com
www.facebook.com[...] 69.63.189.16 www-11-01.ash2.[...]69.in-addr.arpa
www.lloydstsb.com[...] 141.92.130.226 X (ns0.bt.net)
www.nordea.fi[...] 92.43.121.130 X (ns01.tdchosting.dk)
www.trendmicro.com[...] 195.215.37.47 a195-215-37-47.[...]echnologies.com
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.
Name IP Address Reverse Name/SOA
www.bankofthewest.com[...] 204.44.2.241 X
www.careerbuilder.com[...] 208.88.81.22 X
www.sparkasse.de[...] 212.34.69.3 X
DNS external proxy (?): OK
Your host ignores external DNS requests.
DNS results wildcarding (?): OK
Your ISP correctly leaves non-resolving names untouched.
Restricted domain DNS lookup (?): OK
Unrestricted domain DNS lookup (?): OK
Direct EDNS support (?): OK
DNS resolver address (?): OK
DNS resolver properties (?): Lookup latency: 200ms
DNS glue policy (?): OK
DNS resolver port randomization (?): OK
DNS lookups of popular domains (?): OK
DNS external proxy (?): OK
DNS results wildcarding (?): OK
Host Properties –
System clock accuracy (?): Warning
Your computer's clock is 6 seconds slow.
Browser properties (?): 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; da; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7
* Accept: text/html,application/xhtml+xml,application/xml; q=0.9,*/*; q=0.8
* Accept Language: da,en-us;q=0.7,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.
--