1
Petit site qui fait une analyse technique de sa connexion internet:
http://netalyzr.icsi.berkeley.edu/

Exemple:
Major Abnormalities

    * No DNS Port Randomization 

Minor Aberrations

    * Certain protocols are blocked in outbound traffic
    * An HTTP proxy was detected based on added or changed HTTP traffic
    * Your computer's clock is slightly fast 

Address-based Tests

NAT detection: NAT Detected

Your global IP address is 10.0.1.2 while your local one is 192.168.200.206. You are behind a NAT. Your local address is in unroutable address space.

Your NAT renumbers TCP source ports sequentially. The following graph shows connection attempts on the X-axis and their corresponding source ports on the Y-axis.
...

2
Ca poutre! Ca fait longtemps que je cherchais un outil de diagnostic efficace, pour savoir si c'était ma connexion qui merdait ou quoi, bah maintenant je suis fixé tongue

The ICSI Netalyzr Beta
Introduction » Analysis » Results
Result Summary
137.212.97-84.rev.gaoland.net / 84.97.212.137
Recorded at 16:39 EDT (20:39 UTC) on Tue, June 09 2009. Permalink. Transcript.
Noteworthy Events
Minor Aberrations

Certain protocols are blocked in outbound traffic
The measured packet loss was somewhat high
The measured time to set up a TCP connection was somewhat high
Network bandwidth may be low
Network packet buffering may be excessive
Address-based Tests
NAT detection: NAT Detected

Your global IP address is 84.97.212.137 while your local one is 192.168.1.100. You are behind a NAT. Your local address is in unroutable address space.

Your NAT renumbers TCP source ports sequentially. The following graph shows connection attempts on the X-axis and their corresponding source ports on the Y-axis.


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 not be sending any email.
The SORBS DUHL believes you are using a dynamically assigned IP address.
Reachability Tests
General connectivity: Note

Basic UDP access is available.
Direct UDP access to remote DNS servers (port 53) is allowed.
The applet was also able to directly request a large DNS response.
Direct UDP access to remote MSSQL servers (port 1434) is allowed.
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) succeeds, but does not return the expected content.
This suggests that your network enforces a mandatory SMTP proxy which may or may not allow you to send email directly from your system. This is probably a countermeasure against malware abusing infected machines for generating spam. You ISP also likely provides a specific mail server that is permitted. Also, webmail services remain unaffected.

The applet received the following reply instead of our expected header:
"220 msfrf2104.sfr.fr ESMTP ABO ************************** "
Direct TCP access to remote DNS servers (port 53) is blocked.
The network you are using appears to enforce the use of a local DNS resolver.
Direct TCP access to remote HTTP servers (port 80) is allowed.
Direct TCP access to remote POP 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 blocked.
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 blocked.
Direct TCP access to remote authenticated SMTP servers (port 587) is allowed.
Direct TCP access to remote IMAP/SSL servers (port 993) is blocked.
Direct TCP access to remote POP/SSL servers (port 995) is allowed.
Direct TCP access to remote SIP servers (port 5060) is allowed.
Direct TCP access to remote BitTorrent servers (port 6881) is allowed.
Network Access Link Properties
Network latency measurements: Latency: 190ms Loss: 7.5%

The round-trip time (RTT) between your computer and our server is 190 msec, which is good.
We recorded a packet loss of 8%. This loss is very significant and will lead to serious performance problems. It could be due either to very high load on our servers due to a large number of visitors, or problems in your network. Of the packet loss, at least 7.5% of the packets appear to have been lost on the path from your computer to our servers.
TCP connection setup latency: 650ms

The time it takes for your computer to set up a TCP connection with our server is 650 msec, which is quite high. This may be due to a variety of factors, including a significant distance between your computer and our server on the West coast of the United States, a particularly slow or poor network link, or problems in your network.
Network bandwidth measurements: Upload 22 Kbit/sec, Download 4.1 Mbit/sec

Your Uplink: We measured your uplink's sending bandwidth at 22 Kbit/sec. This rate could be considered quite slow, and will affect your user experience if you perform large transfers.
During this test, the applet observed 4 reordered packets.
Your Downlink: We measured your downlink's receiving bandwidth at 4.1 Mbit/sec. This level of bandwidth works well for many users.
Network buffer measurements: Uplink 5800 ms, Downlink 110 ms

We estimate your uplink as having 5800 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 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 110 msec of buffering. This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic.
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: OK

We did not detect file-content filtering.
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 (set by our server)
Your web browser was unable to fetch an image using IPv6.
HTTP caching behavior: OK

There is no suggestion that a transparent HTTP cache exists in your network.
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.
DNS resolver address: OK

The IP address of your ISP's DNS Resolver is 86.64.145.148, which resolves to 148.145.64-86.rev.gaoland.net.
DNS resolver properties: Lookup latency: 210ms

Your ISP's DNS resolver requires 210 msec to conduct an external lookup, and 65 msec to lookup an item in the cache.
Your resolver is using QTYPE=A for default queries.
Your resolver is not automatically performing IPv6 queries.
Your DNS resolver does not use EDNS.
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.
DNS glue policy: OK

Your ISP's DNS resolver accepts generic glue records located in subdomains of the queried domain.
Your ISP's DNS resolver accepts additional (glue) records for nameservers located in subdomains of the queried domain.
Your ISP's DNS resolver follows CNAMEs when it is in the same domain.
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 lookups of popular domains: OK

74 of 74 popular names were resolved successfully. Show all names.
4 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.
1 popular name has 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 results wildcarding: OK

Your ISP correctly leaves non-resolving names untouched.
Host Properties
System clock accuracy: OK

Your computer's clock agrees with our server's clock.
Browser properties

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; en-US) AppleWebKit/530.5 (KHTML, like Gecko) Chrome/2.0.172.30 Safari/530.5
Accept: application/xml,application/xhtml+xml,text/html; q=0.9,text/plain; q=0.8,image/png,*/*; q=0.5
Accept Language: en-US,en;q=0.8
Accept Encoding: gzip,deflate,bzip2,sdch
Accept Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
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
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:

ID ae8172f5-27187-be0574c8-ee54-4e9e-9a53 FAQs + ICSI
3
Sympa happy
avatar<<< Kernel Extremis©®™ >>> et Inventeur de la différence administratif/judiciaire ! (©Yoshi Noir)

<Vertyos> un poil plus mais elle suce bien quand même la mienne ^^
<Sabrina`> tinkiete flan c juste qu'ils sont jaloux que je te trouve aussi appétissant
4
Clair, sympa (surtout quand je comprends rien)
avatar"The trouble with quotes on the Internet is that you can never know is they are genuine" (Abraham Lincoln)
5
grin
avatar<<< Kernel Extremis©®™ >>> et Inventeur de la différence administratif/judiciaire ! (©Yoshi Noir)

<Vertyos> un poil plus mais elle suce bien quand même la mienne ^^
<Sabrina`> tinkiete flan c juste qu'ils sont jaloux que je te trouve aussi appétissant