Freebox Server (Ultra V9/ Pop V8/ Delta V7 / Revolution V6 / Mini 4K)

Concerne le projet: Freebox Server (Ultra V9/ Pop V8/ Delta V7 / Revolution V6 / Mini 4K)
Ouverte par Baloos - 27/11/2013
Dernière modification par nipo - 27/11/2013

The ICSI Netalyzr
Start » Analysis » Results
78.205.144.196
Recorded at 01:24 EST (06:24 UTC), Nov 27 2013. Permalink. Client/server transcript.

Major Abnormalities –

  Your ISP's DNS server is slow to lookup names
  We received unexpected and possibly dangerous results when looking up important names 

Minor Aberrations –

  Network packet buffering may be excessive 

Network buffer measurements (?): Uplink 5100 ms, Downlink 2100 ms –
We estimate your uplink as having 5100 ms 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 2100 ms 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 downloads. With such a buffer, real-time applications such as games or audio chat can work quite poorly when conducting large downloads at the same time.

DNS resolver properties (?): Lookup latency 880 ms –
Your ISP‘s DNS resolver requires 880 ms to conduct an external lookup. It takes 84 ms for your ISP‘s DNS resolver to lookup a name on our server.
This is particularly slow, and you may see significant performance degradation as a result.
Your resolver ignored the response suggesting it should retry with TCP.
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 0×20 randomization, but will pass names in a case-sensitive manner.
Your ISP‘s DNS server cannot use IPv6.
No transport problems were discovered which could affect the deployment of DNSSEC.

DNS lookups of popular domains (?): Warning –
2 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
ad.doubleclick.net 212.27.40.246 white.proxad.net
partner.googleadservices.com 212.27.40.246 white.proxad.net

90 of 90 popular names were resolved successfully. Show all names.
27 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.
5 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.