Nej Lan! Det ser slemt ud ikke sandt?
Har taget mig en ICSI Netalyzr.. Her er svaret:
Summary of Noteworthy Events + –
Major Abnormalities –
•We received unexpected and possibly dangerous results when looking up important names
•Your ISP is using DNS to redirect specific sites
Minor Aberrations – •Certain TCP protocols are blocked in outbound traffic •The measured packet loss was somewhat high
•Network packet buffering may be excessive
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 (?): 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 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 connections to remote authenticated SMTP servers (port 587) succeed, but do not receive the expected content. The applet received the following reply instead of our expected header:
"421 Cannot establish SSL with SMTP server 67.202.37.63:465, SSL_connect error 336031996 "
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
Traceroute (?): OK +
Path MTU (?): OK +
Network Access Link Properties + – Network latency measurements (?): Latency: 110ms Loss: 5.0% – The round-trip time (RTT) between your computer and our server is 110 msec, which is good.
We recorded a packet loss of 5.0%. This loss rate can result in noticeable performance problems. It could be due either to significant load on our servers due to a large number of visitors, or problems with your network. Of the packet loss, at least 5.0% of the packets appear to have been lost on the path from your computer to our servers.
TCP connection setup latency (?): 92ms + Network background health measurement (?): no transient outages +
Network bandwidth (?): Upload 840 Kbit/sec, Download 8.1 Mbit/sec + Network buffer measurements (?): Uplink 600 ms, Downlink 480 ms –
We estimate your uplink as having 600 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 estimate your downlink as having 480 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 downloads. Real-time applications, such as games or audio chat, may also work 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 180ms + Direct probing of DNS resolvers (?): + DNS glue policy (?): OK + DNS resolver port randomization (?): OK +
DNS lookups of popular domains (?): Warning –
3 popular names have a significant anomaly. The ownership suggested by the reverse name lookup does not match our understanding of the original name. This could be caused by an error somewhere in the domain information, deliberate blocking or redirection of a site using DNS, or it could be that your ISP's DNS Server is acting as a DNS "Man-in-the-Middle".
We attempted to download HTTP content from the IP addresses that your ISP's DNS server returned to you for these names. Where the download succeeded, you can click on the IP address in the table below to download a compressed file containing an HTTP session transcript.
Note! The session content is potentially harmful to your computer when viewed in a browser, so use caution when examining it.
Name
IP Address
Reverse Name/SOA
encrypted.google.com
77.214.52.170
SOA: ns1.cybercity.dk
www.google.com[...]
77.214.52.187
SOA: ns1.cybercity.dk
www.google-analytics.com[...]
77.214.52.174
SOA: ns1.cybercity.dk
90 of 90 popular names were resolved successfully. Show
23 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 n
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 +
DNS results wildcarding (?): OK +
DNS-level redirection of specific sites (?): Danger –
Your ISP appears to be using DNS to redirect traffic for one or more websites to third-party servers. The affected sites are:
www.google.com.[...]
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 + Host Properties + –
System clock accuracy (?): OK +
Browser properties (?): OK +
Uploaded data (?): OK +
--
trololol
1.6 1.6 1.6