Google+

¿Quieres saber más información sobre tu proveedor de Internet y si te está limitando tu conexión? (ACTUALIZADO)

Ancho de banda 150x150 ¿Quieres saber más información sobre tu proveedor de Internet y si te está limitando tu conexión? (ACTUALIZADO)Si tienes sospechas o dudas sobre tu proveedor de Internet y quieres saber si te están limitando tu conexión estás en la misma situación de muchos usuarios en nuestro país República Dominicana.

Existen herramientas para poder descubrir si tu proveedor te limita la velocidad de Internet y otros trucos sucios que suelen usar.  Mayormente estas herramientas son difíciles de usar y están desarrolladas para sistemas operativos como Linux y Unix.  La mayoría de los usuarios usan Windows (No se porque) y por eso me di la tarea de buscar algo fácil de usar y compatible con Windows.  Se trata de un applet diseñoado en los laboratorios informáticos de la universidad Estadounidense  de Berkeley.  Es una herramienta que prueba tu conexión de distintas formas para verificar que esta haciendo tu proveedor de Internet detrás de las puertas.

Para usar la herramienta visiten el siguiente LINK y presionen “Start Analysis”.  Para que el applet funcione deben tener java instalado en sus cajitas de Windows.  Tomen en cuenta que todo está en Inglés.  Luego de  que prueben les pido que publiquen vía un comentario sus resultados aquí en el Blog y les explicaré con punto y coma los resultados.  Gracias y hasta luego.

ACTUALIZACIÓN

Encontré otra herramienta que nos deja probar si nos están limitando por protocolos.  Con ella puedes probar el protocolo de HTTP,POP,POP4,SSH y las aplicaciones de P2P como Emule, Bittorrent, Gnutella, Usenet (NNTP).  También podrán probar servicios de Video como Youtube. Ya hice varias pruebas y gracias a los resultados puedo ver más allá del engaño.  Aquí les dejo el LINK a la herramienta.  Prueben y comenten sus resultados por aquí.  Si tienen alguna pregunta coméntala por aquí para que otros usuarios aprendan de la respuesta.  Happy Testing =)


Consultor de Tecnologías de Información, padre. Nativo Dominicano. Futurísta. WHH. Fundador del Ejército geek. Pueden seguirme vía Twitter @carlosfanini

Publicidad

  • http://www.facebook.com/roycordero Roy Cordero

    hola pana gracias por ayudarnos y decir q tu aporte y explicacion es un acto de buena fe… mira aca esta los datos q copie y pegue

    The ICSI Netalyzr

    Start » Analysis » Results

    Result Summary

    + – (help)200.87.158.129

    Recorded at 22:45 EST (03:45 UTC next day), Mar 07 2013. Permalink. Referrer. Client/server transcript.

    Summary of Noteworthy Events+ –

    Major Abnormalities–

    You are listed on a significant DNS blacklist

    Minor Aberrations–

    The time to set up a TCP connection was somewhat high

    The network indicated bursts of packet loss

    Network bandwidth may be low

    Network packet buffering may be excessive

    The DNS resolver may have problems with DNSSEC

    Not all DNS types were correctly processed

    Your IP address acts as a DNS server

    Your computer’s clock is slightly slow

    Address-based Tests+ –

    NAT detection (?): NAT Detected+

    Local Network Interfaces (?): OK+

    DNS-based host information (?): Warning–

    You are not a Tor exit node for HTTP traffic.

    You are listed on the following Spamhaus blacklists: XBL PBL

    The SORBS DUHL believes you are using a statically assigned IP address.

    NAT support for Universal Plug and Play (UPnP) (?): Yes+

    Reachability Tests+ –

    TCP connectivity (?): OK+

    UDP connectivity (?): OK+

    Traceroute (?): OK+

    Path MTU (?): OK+

    Hidden Proxy Detection (?): OK+

    Network Access Link Properties+ –

    Network performance (?): Latency: 210 ms, Loss: 0.0%+

    TCP connection setup latency (?): 360ms–

    The time it takes your computer to set up a TCP connection with our server is 360 ms, which is somewhat high. This may be due to a variety of factors, including distance between your computer and our server, a slow network link, or other network traffic.

    Background measurement of network health (?): 4 transient outages, longest: 2.8 seconds–

    During most of Netalyzr’s execution, the client continuously measures the state of the network in the background, looking for short outages. During testing, the client observed 4 such outages. The longest outage lasted for 2.8 seconds. This suggests a general problem with the network where connectivity is intermittent. This loss might also cause some of Netalyzr’s other tests to produce incorrect results.

    Network bandwidth (?): Upload 220 Kbit/s, Download 23 Kbit/s–

    Your Uplink: We measured your uplink’s sending bandwidth at 220 Kbit/s. This rate could be considered somewhat slow, and may affect your user experience if you perform large transfers.

    Your Downlink: We measured your downlink’s receiving bandwidth at 23 Kbit/s. This rate could be considered quite slow, and will affect your user experience if you perform large transfers.

    Network buffer measurements (?): Uplink 4000 ms, Downlink 2200 ms–

    We estimate your uplink as having 4000 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 2200 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.

    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 280 ms–

    Your ISP’s DNS resolver requires 280 ms to conduct an external lookup. It takes 270 ms for your ISP’s DNS resolver to lookup a name on our server.

    Your resolver is incapable of using TCP to process 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 0×20 randomization, but will pass names in a case-sensitive manner.

    Your ISP’s DNS server cannot use IPv6.

    Your DNS resolver may have significant transport-problems with the upcoming DNSSEC deployments. The resolver is incapable of falling back to TCP.

    Direct probing of DNS resolvers (?)–

    Your system is configured to use 2 DNS resolver(s).

    The resolver at 200.87.100.10 (illimani1) could not process the following tested types:

    Medium (~1300B) TXT records

    Large (~3000B) TXT records

    Large (~3000B) TXT records fetched with EDNS0Requests from this resolver come from 200.87.100.236. This resolver requries 351 ms to fetch a result from our server and 119 ms to return a result from its cache. It does not validate DNSSEC. It does not wildcard NXDOMAIN errors. The resolver reports a number of additional properties. Show them.

    The resolver at 200.87.100.40 (illimani2) could not process the following tested types:

    Medium (~1300B) TXT records

    Large (~3000B) TXT records

    Large (~3000B) TXT records fetched with EDNS0Requests from this resolver come from 200.87.100.236. This resolver requries 278 ms to fetch a result from our server and 93 ms to return a result from its cache. It does not validate DNSSEC. It does not wildcard NXDOMAIN errors. The resolver reports a number of additional properties. Show them.

    DNS glue policy (?): OK+

    DNS resolver port randomization (?): OK+

    DNS lookups of popular domains (?): OK+

    DNS external proxy (?): Warning–

    Your host, NAT, or firewall acts as a DNS server or proxy. Requests sent to this server are eventually processed by 200.87.100.235.

    This is probably a bug in your NAT’s firmware, and represents a minor security vulnerability.

    DNS results wildcarding (?): OK+

    DNS-level redirection of specific sites (?): OK+

    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 (?): Warning–

    Your computer’s clock is 6 seconds slow.

    Browser properties (?): OK+

    Uploaded data (?): OK+

    Feedback+ –

    User-provided feedback–

    Feel free to update your feedback below.

    If you’d like to give us a way to contact you at a later time, please provide an email address. We will never share your address with anyone.

    How is your machine/device connected to the local network?
    Wireless
    Wired

    Where are you right now?
    At home
    At work
    In a public setting (wifi hotspot, internet cafe, etc)
    Other (please describe)

    Feel free to leave additional comments here.

    ID 43ca208a-29203-015a6739-788b-4d8f-a0d6

    FAQs + Blog + Papers + Links + ICSI

  • http://twitter.com/carlos_Spears69 Carlos_Spears

    SALUDOS, aqui mi resultado del test, Porfavor ayudame, que significa esto, parece malo

    Summary of Noteworthy Events

    +

    Minor Aberrations –

    Certain TCP protocols are blocked in outbound traffic The network measured bursts of packet loss Network bandwidth may be low Network packet buffering may be excessive Some DNS resolvers appear to be down Your IP address acts as a DNS server

    Address-based Tests
    +

    NAT detection (?): NAT Detected +

    Local Network Interfaces (?): OK +

    DNS-based host information (?): OK +

    NAT support for Universal Plug and Play (UPnP) (?): Not found +

    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 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 connections to remote PPTP Control
    servers (port 1723) succeed, but do not receive the expected content.
    The applet received an empty response instead of our normal
    banner. This suggests that a firewall, proxy, or filter initially
    allowed the connection and then terminated it, either because it did
    not understand our server’s reply or decided to block the service.

    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: 150ms Loss: 0.0% +

    TCP connection setup latency (?): 210ms +

    Network background health measurement (?): 1 transient outages, longest: 0.6 seconds –

    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 1 such outages.
    The longest outage lasted for 0.6 seconds. This suggests a general
    problem with the network where connectivity is intermittent. This
    loss might also cause some of Netalyzr’s other tests to produce
    incorrect results.

    Network bandwidth (?): Upload 81 Kbit/sec, Download 160 Kbit/sec –

    Your Uplink: We measured your uplink’s
    sending bandwidth at 81 Kbit/sec. This rate could be considered
    somewhat slow, and may affect your user experience if you perform
    large transfers.

    Your Downlink: We measured your downlink’s
    receiving bandwidth at 160 Kbit/sec. This rate could be considered
    quite slow, and will affect your user experience if you perform large
    transfers.

    Network buffer measurements (?): Uplink 1600 ms, Downlink 6200 ms –

    We estimate your uplink as having 1600 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 6200 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 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.

    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 700ms +

    Direct probing of DNS resolvers (?) –

    Your system is configured to use 3 DNS resolver(s).

    The resolver at 192.168.1.1 could not process the following tested types: Medium (~1300B) TXT recordsLarge (~3000B) TXT recordsLarge (~3000B) TXT records fetched with EDNS0
    It does not validate DNSSEC. It does not wildcard NXDOMAIN errors.

    The resolver at 190.103.64.11 (ns1) can process all tested types. It
    does not validate DNSSEC. It does not wildcard NXDOMAIN errors. The
    resolver reports a number of additional properties.
    Show them.

    The resolver at 200.105.128.41 is not responding to requests.

    DNS glue policy (?): OK +

    DNS resolver port randomization (?): OK +

    DNS lookups of popular domains (?): OK +

    DNS external proxy (?): Warning –

    Your host, NAT, or firewall acts as a DNS server
    or proxy. Requests sent to this server are eventually processed by
    74.125.178.20.
    This is probably a bug in your NAT’s firmware, and represents a
    minor security vulnerability.

    DNS results wildcarding (?): OK +

    DNS-level redirection of specific sites (?): OK +

    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 

  • http://www.facebook.com/profile.php?id=1215417440 Andres Melendez

    Saludos amigo. Ya le envié la información del análisis de la pagina que recomendó. Espero su ayuda con la interpretación de dicha info. Muchas gracias de ante mano.

  • Emilio Arias

    Summary of Noteworthy Events –Minor AberrationsNetwork bandwidth may be low Network packet buffering may be excessive The NAT’s DNS proxy doesn’t fully implement the DNS standard Not all DNS types were correctly processed Your computer’s clock is slightly slow 
    Address-based Tests +
    NAT detection (?): NAT Detected
    Local Network Interfaces (?): OK
    DNS-based host information (?): OKNAT support for Universal Plug and Play (UPnP) (?): Not found
    Reachability Tests +
    TCP connectivity (?): OK
    UDP connectivity (?): OK
    Traceroute (?): OKPath MTU (?): OK
    Network Access Link Properties –Network latency measurements (?): Latency: 71ms Loss: 0.0%The round-trip time (RTT) between your computer and our server is 71 msec, which is good.We recorded no packet loss between your system and our server.TCP connection setup latency (?): 74msThe time it takes your computer to set up a TCP connection with our server is 74 msec, which is good.Network background health measurement (?): no transient outagesDuring 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 220 Kbit/sec, Download 30 Kbit/secYour Uplink: We measured your uplink’s sending bandwidth at 220 Kbit/sec. This rate could be considered somewhat slow, and may affect your user experience if you perform large transfers.Your Downlink: We measured your downlink’s receiving bandwidth at 30 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 one reordered packet.Network buffer measurements (?): Uplink 4200 ms, Downlink 840 msWe estimate your uplink as having 4200 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 840 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 (?): OKJavaScript-based tests (?): OK
    DNS Tests –Restricted domain DNS lookup (?): OKWe can successfully look up 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 (?): OKWe can successfully look up arbitrary names from within the Java applet. This means we are able to conduct all test on your DNS server.Direct DNS support (?): OKAll tested DNS types were received OK.Direct EDNS support (?): OKEDNS-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 (?): OKThe IP address of your ISP’s DNS Resolver is 190.94.2.27, which resolves to ganimedes.tricom.net.DNS resolver properties (?): Lookup latency 160msYour ISP’s DNS resolver requires 160 msec to conduct an external lookup. It takes 110 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 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.Direct probing of DNS resolvers (?)Your system is configured to use 1 DNS resolver(s).The resolver at 192.168.1.1 could not process the following tested types:TXT (text) recordsMedium (~1300B) TXT recordsLarge (~3000B) TXT recordsLarge (~3000B) TXT records fetched with EDNS0RTYPE=1169 (deliberately unknown) records
    It does not validate DNSSEC. It does not wildcard NXDOMAIN errors.DNS glue policy (?): OKYour ISP’s DNS resolver does not accept generic additional (glue) records — good.Your ISP’s DNS resolver does not accept additional (glue) records which correspond to nameservers.Your ISP’s DNS resolver does not follow CNAMEs.DNS resolver port randomization (?): OKYour 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 (?): OK90 of 90 popular names were resolved successfully. Show all names.13 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.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.DNS external proxy (?): OKYour host ignores external DNS requests.DNS results wildcarding (?): OKYour ISP correctly leaves non-resolving names untouched.DNS-level redirection of specific sites (?): OKYour ISP does not appear to be using DNS to redirect traffic for specific websites.Direct probing of DNS roots (?)We checked which DNS root server instances your computer can reach. All root servers responded. Show them.
    IPv6 Tests +
    DNS support for IPv6 (?): OK
    IPv4, IPv6, and your web browser (?): No IPv6 supportIPv6 connectivity (?): No IPv6 support
    Host Properties –System clock accuracy (?): WarningYour computer’s clock is 20 seconds slow.Browser properties (?): OKYour web browser sends the following parameters to all web sites you visit:User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.46 Safari/535.11Accept: text/html,application/xhtml+xml,application/xml; q=0.9,*/*; q=0.8Accept Language: es-419,es;q=0.8Accept Encoding: gzip,deflate,sdchAccept Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
    Java identifies your operating system as Windows 7.Uploaded data (?): OKThe applet uploaded the following additional content:apache_404custom_404plain_404raw_http_content

  • adolfo paredes

    una  pregunta mas cual es el mejor sistema para gamers lo digo por las cajitas de windowsMajor AbnormalitiesNo DNS Port Randomization Minor AberrationsNetwork bandwidth may be low Network packet buffering may be excessive Not all DNS types were correctly processed We received unexpected and possibly dangerous results when looking up important names Your computer’s clock is slightly slow Address-based Tests +

    NAT detection (?): NAT Detected
    Local Network Interfaces (?): OK
    DNS-based host information (?): OKNAT support for Universal Plug and Play (UPnP) (?): Not foundReachability Tests +

    TCP connectivity (?): OK
    UDP connectivity (?): OK
    Traceroute (?): OKPath MTU (?): OKNetwork Access Link Properties –
    Network latency measurements (?): Latency: 71ms Loss: 0.5%The round-trip time (RTT) between your computer and our server is 71 msec, which is good.We recorded a packet loss of 0.5%. This loss rate is within the range commonly encountered and not usually inducing significant performance problems. All the packet loss appears to have occurred on the path from our server to your computer.TCP connection setup latency (?): 86msThe time it takes your computer to set up a TCP connection with our server is 86 msec, which is good.Network background health measurement (?): no transient outagesDuring 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 170 Kbit/sec, Download 1.1 Mbit/secYour Uplink: We measured your uplink’s sending bandwidth at 170 Kbit/sec. This rate could be considered somewhat slow, and may affect your user experience if you perform large transfers.Your Downlink: We measured your downlink’s receiving bandwidth at 1.1 Mbit/sec. This level of bandwidth works well for many users.Network buffer measurements (?): Uplink 2500 ms, Downlink 700 msWe estimate your uplink as having 2500 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 700 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 (?): OKJavaScript-based tests (?): OKDNS Tests –
    Restricted domain DNS lookup (?): OKWe can successfully look up 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 (?): OKWe can successfully look up arbitrary names from within the Java applet. This means we are able to conduct all test on your DNS server.Direct DNS support (?): OKAll tested DNS types were received OK.Direct EDNS support (?): OKEDNS-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 (?): OKThe IP address of your ISP’s DNS Resolver is 196.3.81.28, which does not resolve. Additional nameservers observed for your host: 196.3.81.27, 196.3.81.26.DNS resolver properties (?): Lookup latency 160msYour ISP’s DNS resolver requires 160 msec to conduct an external lookup. It takes 140 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 0×20 randomization, but will pass names in a case-sensitive manner.Your NAT has a built-in DNS proxy.Your ISP’s DNS server cannot use IPv6.No transport problems were discovered which could affect the deployment of DNSSEC.Direct probing of DNS resolvers (?)Your system is configured to use 1 DNS resolver(s).The resolver at 10.0.0.1 was unable to process the following tested types:Medium (~1300B) TXT recordsLarge (~3000B) TXT records
    It does not validate DNSSEC. It does not wildcard NXDOMAIN errors. The resolver reports the following properties:Version: BIND X.Y.ZAuthors: XYZDNS glue policy (?): OKYour ISP’s DNS resolver does not accept generic additional (glue) records — good.Your ISP’s DNS resolver does not accept additional (glue) records which correspond to nameservers.Your ISP’s DNS resolver does not follow CNAMEs.DNS resolver port randomization (?): DangerYour ISP’s DNS resolver does not randomize its local port number. This means your ISP’s DNS resolver is probably vulnerable to DNS cache poisoning, which enables an attacker to intercept and modify effectively all communications of anyone using your ISP.
    We suggest that, if possible, you immediately contact your network provider, as this represents a serious vulnerability.
    The following graph shows DNS requests on the x-axis and the detected source ports on the y-axis.
    DNS lookups of popular domains (?): Warning5 popular names have 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, deliberate blocking using DNS, or your DNS server could be misconfigured or enabling a Man-in-the-Middle attack.
    NameIP AddressReverse Name/SOAad.doubleclick.net190.167.241.152Xencrypted.google.com190.167.241.144Xwww.google.com190.167.241.147Xwww.google-analytics.com190.167.241.144Xpartner.googleadservices.com190.167.241.149X79 of 79 popular names were resolved successfully. Show all names.12 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.DNS external proxy (?): OKYour host ignores external DNS requests.DNS results wildcarding (?): OKYour ISP correctly leaves non-resolving names untouched.DNS-level redirection of specific sites (?): OKYour ISP does not appear to be using DNS to redirect traffic for specific websites.IPv6 Tests +

    DNS support for IPv6 (?): OK
    IPv4, IPv6, and Your Web Browser (?): No IPv6 SupportIPv6 Connectivity (?): No IPv6 SupportHost Properties –System clock accuracy (?): WarningYour computer’s clock is 7 seconds slow.Browser properties (?): OKYour web browser sends the following parameters to all web sites you visit:User Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/534.30 (KHTML, like Gecko) Chrome/12.0.742.100 Safari/534.30Accept: text/html,application/xhtml+xml,application/xml; q=0.9,*/*; q=0.8Accept Language: en-US,en;q=0.8Accept Encoding: gzip,deflate,sdchAccept Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
    Java identifies your operating system as Windows 7.Uploaded Data (?): OKThe applet uploaded the following additional content:apache_404custom_404plain_404raw_http_content

  • Luis

    Hola Carlos acabo de hacer el Test, tengo conexion de 2 Megas, estos fueron los resultados:

    Summary of Noteworthy Events –
    Minor Aberrations •Certain TCP protocols are blocked in outbound traffic
    •The measured time to set up a TCP connection was somewhat high
    •None of the server’s bandwidth measurement packets arrived at the client
    Minor Aberrations
    Address-based Tests +
    NAT detection (?): NAT DetectedYour global IP address is 201.205.197.194 while your local one is 192.168.0.100. 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.

    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.

    Local Network Interfaces (?): OKYour computer reports the following network interfaces, with the following IP addresses for each one: eth0: (an ethernet interface)eth1: (an ethernet interface)eth10: (an ethernet interface)eth11: (an ethernet interface)eth2: (an ethernet interface)eth3: (an ethernet interface)fe80::4041:aadf:dab2:645b (a link-local IPv6 address)192.168.0.100 (a private IPv4 address)eth4: (an ethernet interface)eth5: (an ethernet interface)eth6: (an ethernet interface)eth7: (an ethernet interface)eth8: (an ethernet interface)eth9: (an ethernet interface)lo: (a local loopback interface)::1 (an IPv6 loopback address)127.0.0.1 (an IPv4 loopback address)net0: net1: net2: net3: net4: 2001:0:4137:9e76:305c:1492:3632:3a3d [Akhbar_25-PC] (a Teredo IPv6 address)fe80::305c:1492:3632:3a3d [Akhbar_25-PC] (a link-local IPv6 address)net5: net6: fe80::5efe:c0a8:64 (a link-local IPv6 address)ppp0: ppp1: DNS-based host information (?): OKYou are not a Tor exit node for HTTP traffic. You are not listed on any Spamhaus blacklists. The SORBS DUHL believes you are using a statically assigned IP address.
    NAT detection (?): NAT Detected Local Network Interfaces (?): OK DNS-based host information (?): OK Reachability Tests –
    TCP connectivity (?): NoteDirect 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 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 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 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 174.129.176.88: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 (?): OKBasic 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 NTP servers (port 123) is allowed. Direct UDP access to remote OpenVPN servers (port 1194) is allowed. Direct UDP access to remote MSSQL servers (port 1434) is allowed. Traceroute (?): OKIt takes 15 network hops for traffic to pass from our server to your system, as shown below. For each hop, the time it takes to traverse it is shown in parentheses.

    1.None (0 ms)
    2.ec2-75-101-160-188.compute-1.amazonaws.com (0 ms)
    3.None (0 ms)
    4.*
    5.*
    6.*
    7.xe-0-4-0-7.r01.asbnva02.us.bb.gin.ntt.net (1 ms)
    8.ae-3.r02.asbnva02.us.bb.gin.ntt.net (1 ms)
    9.None (1 ms)
    10.0.ae2.XL3.IAD8.ALTER.NET (1 ms)
    11.0.xe-6-0-0.IG2.LAX1.ALTER.NET (68 ms)
    12.mwx00738-gw.customer.alter.net (135 ms)
    13.mwx00738-gw.customer.alter.net (135 ms)
    14.None (112 ms)
    15.*
    Path MTU (?): OKThe 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 Traceroute (?): OK Path MTU (?): OK
    Network Access Link Properties –
    Network latency measurements (?): Latency: 190ms Loss: 0.0%The round-trip time (RTT) between your computer and our server is 190 msec, which is good. We recorded no packet loss between your system and our server. TCP connection setup latency (?): 760msThe time it takes for your computer to set up a TCP connection with our server is 760 msec, which is quite high. This may be due to a variety of factors, including a significant distance between your computer and our server, a particularly slow or poor network link, or problems in your network. Network background health measurement (?): no transient outagesDuring 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 (?): NoteNone of the bandwidth measurement packets sent between the server and client arrived at the client, which prevented us from measuring the available bandwidth. One possible reason for this is dynamic filtering by access gateway devices. Another possibility is simply a transient error. Network buffer measurements (?): NoteNone of the buffer measurement packets sent by the server arrived at the client, which prevented us from measuring the available buffer size. One possible reason for this is dynamic filtering by access gateway devices. Network latency measurements (?): Latency: 190ms Loss: 0.0% TCP connection setup latency (?): 760ms Network background health measurement (?): no transient outages Network bandwidth measurements (?): Note Network buffer measurements (?): Note
    HTTP Tests +
    Address-based HTTP proxy detection (?): OKThere is no explicit sign of HTTP proxy use based on IP address. Header-based HTTP proxy detection (?): OKNo HTTP header or content changes hint at the presence of a proxy. HTTP proxy detection via malformed requests (?): OKDeliberately 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 (?): OKWe did not detect file-content filtering. HTTP caching behavior (?): OKThere is no suggestion that a transparent HTTP cache exists in your network. JavaScript-based tests (?): OKThe 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)netalyzrStatus = running (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 (?): OK HTTP caching behavior (?): OK JavaScript-based tests (?): OK DNS Tests +
    Restricted domain DNS lookup (?): OKWe can successfully look up 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 (?): OKWe can successfully look up arbitrary names from within the Java applet. This means we are able to conduct all test on your DNS server. Direct DNS support (?): OKAll tested DNS types were received OK Direct EDNS support (?): OKEDNS-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 (?): OKThe IP address of your ISP’s DNS Resolver is 200.91.75.5, which resolves to tesla.ice.co.cr. DNS resolver properties (?): Lookup latency 170msYour ISP’s DNS resolver requires 170 msec to conduct an external lookup. It takes 120 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 0×20 randomization, but will pass names in a case-sensitive manner. Your NAT has a built-in DNS proxy. We sent it a DNS request and our server received it from 200.91.75.5. Your ISP’s DNS server cannot use IPv6. No transport problems were discovered which could affect the deployment of DNSSEC. DNS glue policy (?): OKYour ISP’s DNS resolver does not accept generic additional (glue) records — good. Your ISP’s DNS resolver does not accept additional (glue) records which correspond to nameservers. Your ISP’s DNS resolver does not follow CNAMEs. DNS resolver port randomization (?): OKYour 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 (?): OK80 of 80 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
    http://www.abbey.co.uk 165.160.13.20 X (pdns1.cscdns.net)
    ad.doubleclick.net 74.125.65.148 gx-in-f148.1e100.net
    http://www.alliance-leicester.co.uk 194.130.105.121 X (alice.ioko365.com)
    http://www.amazon.com 72.21.211.176 X (dns-external-master.amazon.com)
    http://www.ameritrade.com 216.105.251.204 X (mike.lynn.tdameritrade.com)
    http://www.bankofamerica.com 171.161.148.173 wwwao-prodtx.bankofamerica.com
    http://www.bankofscotland.co.uk 195.171.171.21 X (ns0.bt.net)
    bit.ly 168.143.172.53 X (ns1.dn.net)
    http://www.capitalone.com 208.80.48.112 X (z.arin.net)
    http://www.chase.com 159.53.64.105 X (ns1.jpmorganchase.com)
    chaseonline.chase.com 159.53.52.105 X (ns1.jpmorganchase.com)
    http://www.citi.com 192.193.103.222 citibank.com
    http://www.citibank.com 192.193.103.222 citibank.com
    http://www.citimortgage.com 192.193.103.118 citimortgage.com
    http://www.cnn.com 157.166.255.18 http://www.cnn.com
    http://www.desjardins.com 142.195.132.100 http://www.desjardins.com
    http://www.dnssec-failed.org 68.87.64.48 speedlab-app03.[...].bo.comcast.net
    http://www.e-gold.com 209.200.169.10 unknown.prolexic.com
    http://www.ebay.com 66.135.200.27 hp-core.ebay.com
    encrypted.google.com 74.125.65.138 gx-in-f138.1e100.net
    http://www.etrade.com 198.93.34.21 http://www.etrade.com
    http://www.f-secure.com 96.16.98.18 a96-16-98-18.de[...]echnologies.com
    http://www.facebook.com 66.220.158.18 www-11-01-ash4.facebook.com
    http://www.fdic.gov 167.176.17.84 http://www.fdic.gov
    http://www.friendfinder.com 208.88.180.81 X (ii53-30.friendfinderinc.com)
    http://www.google.com 74.125.65.99 gx-in-f99.1e100.net
    http://www.google-analytics.com 74.125.65.138 gx-in-f138.1e100.net
    http://www.halifax.co.uk 212.140.245.97 http://www.halifax.co.uk
    http://www.hsbc.co.uk 193.108.74.126 X (ns3.hsbc.com)
    http://www.irs.gov 96.16.98.17 a96-16-98-17.de[...]echnologies.com
    http://www.jpmorganchase.com 159.53.64.105 X (ns1.jpmorganchase.com)
    mail.google.com 74.125.65.17 gx-in-f17.1e100.net
    mail.live.com 64.4.56.55 origin.by148w.[...].mail.live.com
    mail.yahoo.com 69.147.112.160 l2.login.vip.re3.yahoo.com
    http://www.mbna.com 209.135.59.10 X (ns1.usi.net)
    http://www.mbna.net 209.135.59.10 X (ns1.usi.net)
    http://www.meebo.com 208.81.191.110 X (ns1.meebo.com)
    messenger.yahoo.com 98.139.200.98 myc1.msg.vip.bf1.yahoo.com
    http://www.microsoft.com 65.55.21.250 wwwco1vip.microsoft.com
    http://www.nationwide.co.uk 155.131.127.83 http://www.nationwide.co.uk
    http://www.networksolutions.com 205.178.187.13 http://www.networksolutions.com
    http://www.newegg.com 216.52.208.185 X (pdns1.ultradns.net)
    online.citibank.com 199.67.181.11 citibankonline.com
    online.wellsfargo.com 151.151.13.132 psaltery-on.wellsfargo.com
    http://www.orange.fr 193.252.122.103 http://www.orange.fr.b2.fti.net
    partner.googleadservices.com 74.125.65.165 gx-in-f165.1e100.net
    http://www.paypal.com 66.211.169.2 X (crocodile.ebay.com)
    http://www.rbs.co.uk 155.136.80.222 X (ns0-08.dns.pipex.net)
    http://www.schwab.com 162.93.218.34 X (d0002cdc.schwab.com)
    search.yahoo.com 74.6.238.254 syc.search.vip.ac2.yahoo.com
    http://www.sears.com 173.223.217.99 a173-223-217-99[...]echnologies.com
    http://www.secureworks.com 206.55.100.29 atl1www01.secureworks.net
    smartzone.comcast.net 76.96.58.12 webmail3.westch[...]ail.comcast.net
    http://www.smithbarney.com 192.193.224.11 ssb.com
    http://www.sterlingsavingsbank.com 12.19.55.215 sterlingsavingsbank.com
    http://www.tdameritrade.com 216.105.251.204 X (mike.lynn.tdameritrade.com)
    http://www.ticketmaster.com 173.223.212.199 a173-223-212-19[...]echnologies.com
    tinyurl.com 195.66.135.138 e2.tinyurl.com
    http://www.torproject.org 86.59.30.36 http://www.torproject.org
    us.etrade.com 12.153.224.21 us.etrade.com
    http://www.usbank.com 170.135.216.181 swiftsend.usbank.com
    http://www.verisign.com 69.58.181.89 www-ilg.verisign.net
    http://www.visa.com 96.16.98.40 a96-16-98-40.de[...]echnologies.com
    http://www.wachovia.com 169.200.183.139 X (sls-ns1.wachovia.com)
    http://www.wamu.com 159.53.116.2 X (ns1.jpmorganchase.com)
    http://www.wellsfargo.com 151.151.88.133 http://www.wellsfargo.com
    westernunion.com 206.201.227.250 wumt1.westernunion.com
    windowsupdate.microsoft.com 207.46.18.94 X (msnhst.microsoft.com)
    wireless.att.com 135.209.168.22 origin-b2b-al[...]eless.att.com
    http://www.yahoo.com 69.147.125.65 ir1.fp.vip.re1.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. Name IP Address Reverse Name/SOA
    http://www.bing.com 96.16.98.25 a96-16-98-25.de[...]echnologies.com
    http://www.deutsche-bank.de 160.83.8.24 X (ns2.db.com)
    http://www.lloydstsb.com 141.92.130.226 X (ns0.bt.net)
    http://www.nordea.fi 92.43.121.130 X (ns01.tdchosting.dk)
    http://www.postbank.de 195.50.155.73 X (ns1.arcor-ip.de)
    http://www.sparkasse.de 212.34.69.3 rev-212.34.69.3.rev.izb.net
    http://www.trendmicro.com 173.223.21.214 a173-223-21-214[...]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
    http://www.bankofthewest.com 204.44.2.241 X
    http://www.barclays.co.uk 157.83.107.4 X
    http://www.careerbuilder.com 208.88.82.22 X
    DNS external proxy (?): OKYour host ignores external DNS requests. DNS results wildcarding (?): OKYour ISP correctly leaves non-resolving names untouched.
    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 170ms DNS glue policy (?): OK DNS resolver port randomization (?): OK DNS lookups of popular domains (?): OK DNS external proxy (?): OK DNS results wildcarding (?): OK IPv6 Tests +
    DNS support for IPv6 (?): OKYour system does not look up IPv6 addresses by default. Your DNS resolver is not on Google’s IPv6 “whitelist”, which means that Google does not enable IPv6 access to their services for you. IPv6 Connectivity (?): Not ExecutedThe test was not executed. Required functionality was unavailable or not permitted. IPv6 TCP connectivity (?): Not ExecutedYour host was not able to contact our IPv6 server for testing. IPv6 and Your Web Browser (?): No IPv6 SupportYour browser was unable to fetch a test image from an IPv6-only server. IPv4 performance to our IPv4-only server did not differ substantially from our IPv4/IPv6 dual-stacked one. IPv6 Path MTU (?): Not ExecutedThe test was not executed. Required functionality was unavailable or not permitted. IPv6 Traceroute (?): Not ExecutedThe test was not executed. Required functionality was unavailable or not permitted.
    DNS support for IPv6 (?): OK IPv6 Connectivity (?): Not Executed IPv6 TCP connectivity (?): Not Executed IPv6 and Your Web Browser (?): No IPv6 Support IPv6 Path MTU (?): Not Executed IPv6 Traceroute (?): Not Executed Host Properties +
    System clock accuracy (?): OKYour computer’s clock agrees with our server’s clock. Browser properties (?): OKThe following parameters are sent by your web browser to all web sites you visit: User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C)Accept: application/x-ms-application, image/jpeg, application/xaml+xml, image/gif, image/pjpeg, application/x-ms-xbap, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */*Accept Language: es-CRAccept Encoding: gzip, deflateAccept Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7Java identifies your operating system as Windows 7. Uploaded Data (?): OKThe following additional content was uploaded by the applet: raw_http_content
    System clock accuracy (?): OK Browser properties (?): OK Uploaded Data (?): OK

    • http://twitter.com/iFanini Carlos Fanini

      Saludos Luis,

      Si no tienes algún tipo de firewall presente en tu RED, tus resultados indican que tu ISP bloquea ciertos protocolos hacia fuera, es decir, no deja que salgan algunos protocolos al internet. También noté que el test no pudo determinar la velocidad real de tu conexión por lo que tendrás que hacerlo de nuevo. Todo lo demás se ve normal, excepto a la manipulación de los queries al DNS de tu ISP. Eso algo que estoy investigando porque ya lo he visto en varios test y lo encuentro muy extraño.

      • Luis

        Pues Firewall… solo el de Windows. No se si Avast estará bloqueando algun tráfico.

        Pura Vida! por la respuesta. Voy a ver si hago el test otra vez a ver si pesca la velocidad.

  • Michael Ravelo

    Aqui dejo mis resultados,
    summary of Noteworthy Events –
    Major Abnormalities
    You are listed on a significant DNS blacklist
    We received unexpected and possibly dangerous results when looking up important names
    Minor Aberrations
    The NAT’s DNS proxy doesn’t fully implement the DNS standard
    Address-based Tests –
    NAT detection (?): NAT Detected
    Your global IP address is 66.98.28.115 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.

    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.

    Local Network Interfaces (?): OK
    Your computer reports the following network interfaces, with the following IP addresses for each one:
    eth0: (an ethernet interface)
    eth1: (an ethernet interface)
    eth10: (an ethernet interface)
    eth2: (an ethernet interface)
    eth3: (an ethernet interface)
    fe80::d190:57ae:1189:8d7d (a link-local IPv6 address)
    192.168.1.101 (a private IPv4 address)
    eth4: (an ethernet interface)
    eth5: (an ethernet interface)
    eth6: (an ethernet interface)
    eth7: (an ethernet interface)
    eth8: (an ethernet interface)
    eth9: (an ethernet interface)
    lo: (a local loopback interface)
    ::1 (an IPv6 loopback address)
    127.0.0.1 (an IPv4 loopback address)
    net0:
    net1:
    net2:
    net3:
    net4:
    fe80::5efe:c0a8:165 (a link-local IPv6 address)
    net5:
    2001:0:4137:9e76:30ba:3fcd:bd9d:e38c [Michael-PC] (a Teredo IPv6 address)
    fe80::30ba:3fcd:bd9d:e38c [Michael-PC] (a link-local IPv6 address)
    net6:
    ppp0:
    ppp1:
    DNS-based host information (?): Warning
    You are not a Tor exit node for HTTP traffic.
    You are listed on the following Spamhaus blacklists: XBL PBL
    The SORBS DUHL believes you are using a statically assigned IP address.
    Reachability Tests +
    TCP connectivity (?): OK
    UDP connectivity (?): OK
    Traceroute (?): OK
    Path MTU (?): OK
    Network Access Link Properties +
    Network latency measurements (?): Latency: 120ms Loss: 0.0%
    TCP connection setup latency (?): 120ms
    Network background health measurement (?): no transient outages
    Network bandwidth measurements (?): Upload 270 Kbit/sec, Download 1.5 Mbit/sec
    Network buffer measurements (?): Uplink 130 ms, Downlink 260 ms
    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
    We can successfully look up 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 can successfully look up arbitrary names from within the Java applet. This means we are able to conduct all test on your DNS server.
    Direct DNS support (?): OK
    All tested DNS types were received OK
    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 196.3.81.28, which resolves to pri-028-b2.codetel.net.do. Additional nameservers observed for your host: 196.3.81.27
    DNS resolver properties (?): Lookup latency 170ms
    Your ISP’s DNS resolver requires 170 msec to conduct an external lookup. It takes 120 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 0×20 randomization, but will pass names in a case-sensitive manner.
    Your NAT has a built-in DNS proxy. We sent it a DNS request and our server received it from 196.3.81.27.
    Some or all specialized DNS types checked are not properly interpreted by the NAT’s DNS proxy. The following tested queries were blocked/failed:
    EDNS0 (DNS extensions)
    AAAA (IPv6 related) records
    TXT (text) records
    RTYPE=169 (deliberately unknown) records
    Your ISP’s DNS server cannot use IPv6.
    No transport problems were discovered which could affect the deployment of DNSSEC.
    DNS glue policy (?): OK
    Your ISP’s DNS resolver does not accept generic additional (glue) records — good.
    Your ISP’s DNS resolver does not accept additional (glue) records which correspond to nameservers.
    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.

    DNS lookups of popular domains (?): Warning
    4 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 190.167.241.152 152.241.167.190[...].codetel.net.do
    encrypted.google.com 190.167.241.144 144.241.167.190[...].codetel.net.do
    http://www.google.com 190.167.241.147 147.241.167.190[...].codetel.net.do
    partner.googleadservices.com 190.167.241.149 149.241.167.190[...].codetel.net.do
    80 of 80 popular names were resolved successfully. Show all names.
    13 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.
    2 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
    Your host ignores external DNS requests.
    DNS results wildcarding (?): OK
    Your ISP correctly leaves non-resolving names untouched.
    IPv6 Tests +
    DNS support for IPv6 (?): OK
    IPv6 Connectivity (?): Not Executed
    IPv6 TCP connectivity (?): Not Executed
    IPv6 and Your Web Browser (?): No IPv6 Support
    IPv6 Path MTU (?): Not Executed
    IPv6 Traceroute (?): Not Executed
    Host Properties +
    System clock accuracy (?): OK
    Browser properties (?): OK
    Uploaded Data (?): OK

    • http://twitter.com/iFanini Carlos Fanini

      Por tus resultados no veo que sea Codetel que te esté limitando. Lo que si he notado es que los DNS de Codetel manipulan algunos dominios de forma extraña. Lo que puede estar afectado tu juego online es la velocidad de subida que tienes. Muchos ignoran que la velocidad de subida es más importante que la de bajada para el online gaming, video conferencias y voip.

      Has la prueba por lo menos 2 veces y analiza si los resultados son los mismos siempre.

  • Michael Ravelo

    Tengo internet de claro, 1.5 mb, me funciona sin problemas de forma general, sin embargo jugando XBOX 360, especificamente Black Ops el sistema me dice que mi bandwith es de 268kbps, no se si es codetel limitando el ancho de banda o que, necesito ayuda por favor, gracias

    • http://twitter.com/iFanini Carlos Fanini

      Saludos Michael,

      Puede decir que eso puedo variar mucho. Esa velocidad no es la real de conexión sino un estimado. ¿Experimentas algún tipo de Lag cuando juegas? ¿Tienes los puertos abiertos para el XBOX? Contesta esas preguntas para poder orientarme más.

      Gracias por visitarnos.

      • Michael Ravelo

        Si me esta lageando cuando juego, solo llego a un maximo de 3 barras de 4 en el latency , pero usualmente tengo 2. Los puertos del xbox estan abiertos

  • Fernando Cabrera

    Hola que tal, primera vez que entro al blog y la verdad que es muy interesante, muchas gracias por la informacion que nos ofreces.
    Te dejo los resultados del test para que me orientes.
    Saludos desde Uruguay

    Summary of Noteworthy Events –
    Major Abnormalities
    We received unexpected and possibly dangerous results when looking up important names
    Minor Aberrations
    Certain TCP protocols are blocked in outbound traffic
    Fragmented UDP traffic is blocked
    The measured network latency 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
    The NAT’s DNS proxy doesn’t fully implement the DNS standard
    Your computer’s clock is substantially fast
    Address-based Tests +
    NAT detection (?): NAT Detected
    Local Network Interfaces (?): OK
    DNS-based host information (?): OK
    Reachability Tests –
    TCP connectivity (?): Note
    Direct TCP connections to remote FTP servers (port 21) failed.
    This is commonly due to how a NAT or firewall handles FTP traffic, as FTP causes unique problems when developing NATs and firewalls.
    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 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 (?): Note
    Basic UDP access is available.
    The applet was unable to send fragmented UDP traffic. The most likely cause is an error in your network’s firewall configuration or NAT.
    The maximum packet successfully sent was 1472 bytes of payload.
    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 NTP servers (port 123) is allowed.
    Direct UDP access to remote OpenVPN servers (port 1194) is allowed.
    Direct UDP access to remote MSSQL servers (port 1434) is allowed.
    Traceroute (?): OK
    It takes 16 network hops for traffic to pass from our server to your system, as shown below. For each hop, the time it takes to traverse it is shown in parentheses.
    None (0 ms)
    ec2-75-101-160-180.compute-1.amazonaws.com (0 ms)
    None (0 ms)
    *
    *
    *
    *
    xe-9-0-0.edge2.Washington1.Level3.net (1 ms)
    ae-1-60.edge3.Washington4.Level3.net (2 ms)
    TELEFONICA.edge3.Washington4.Level3.net (7 ms)
    Xe8-0-4-0-grtmiabr4.red.telefonica-wholesale.net (146 ms)
    Xe6-1-1-0-grtmiana3.red.telefonica-wholesale.net.123.142.94.in-addr.arpa (27 ms)
    ANTEL-0-0-1-0-grtmiana3.red.telefonica-wholesale.net (38 ms)
    ibr2nap1-1-1.antel.net.uy (171 ms)
    r200-40-16-117.antel.net.uy (173 ms)
    agu1bras1-bb2.antel.net.uy (182 ms)
    Path MTU (?): OK
    The path between our system and your network has an MTU of 1492 bytes. The bottleneck is at IP address 200.40.18.3.
    Network Access Link Properties –
    Network latency measurements (?): Latency: 340ms Loss: 0.5%
    The round-trip time (RTT) between your computer and our server is 340 msec, which is somewhat high. This may be due to a variety of factors, including distance between your computer and our server, a slow network link, or other network traffic.
    We recorded a packet loss of 0.5%. This loss rate is within the range commonly encountered and not usually inducing significant performance problems. Of the packet loss, at least 0.5% of the packets appear to have been lost on the path from your computer to our servers.
    TCP connection setup latency (?): 360ms
    The time it takes your computer to set up a TCP connection with our server is 360 msec, which is somewhat high. This may be due to a variety of factors, including distance between your computer and our server, a slow network link, or other network traffic.
    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 220 Kbit/sec, Download 1.2 Mbit/sec
    Your Uplink: We measured your uplink’s sending bandwidth at 220 Kbit/sec. This rate could be considered somewhat slow, and may affect your user experience if you perform large transfers.
    Your Downlink: We measured your downlink’s receiving bandwidth at 1.2 Mbit/sec. This level of bandwidth works well for many users.
    During this test, the applet observed one reordered packet.
    Network buffer measurements (?): Uplink 1400 ms, Downlink 310 ms
    We estimate your uplink as having 1400 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 310 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
    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
    We can successfully look up 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 can successfully look up arbitrary names from within the Java applet. This means we are able to conduct all test on your DNS server.
    Direct DNS support (?): OK
    All tested DNS types were received OK
    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 200.40.220.213, which resolves to rnsagu4.antel.net.uy.
    DNS resolver properties (?): Lookup latency 430ms
    Your ISP’s DNS resolver requires 430 msec to conduct an external lookup. It takes 210 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 512 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 NAT has a built-in DNS proxy. We sent it a DNS request and our server received it from 200.40.220.213.
    Some or all specialized DNS types checked are not properly interpreted by the NAT’s DNS proxy. The following tested queries were blocked/failed:
    EDNS0 (DNS extensions)
    AAAA (IPv6 related) records
    TXT (text) records
    RTYPE=169 (deliberately unknown) records
    Your ISP’s DNS server cannot use IPv6.
    No transport problems were discovered which could affect the deployment of DNSSEC.
    DNS glue policy (?): OK
    Your ISP’s DNS resolver does not accept generic additional (glue) records — good.
    Your ISP’s DNS resolver does not accept additional (glue) records which correspond to nameservers.
    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.

    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
    ad.doubleclick.net 200.40.0.84 r200-40-0-84.antel.net.uy
    http://www.google.com 200.40.0.83 adistcen1.antel.net.uy
    partner.googleadservices.com 200.40.0.85 r200-40-0-85.antel.net.uy
    80 of 80 popular names were resolved successfully. Show all names.
    6 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.
    7 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
    Your host ignores external DNS requests.
    DNS results wildcarding (?): OK
    Your ISP correctly leaves non-resolving names untouched.
    IPv6 Tests +
    DNS support for IPv6 (?): OK
    IPv6 Connectivity (?): Not Executed
    IPv6 TCP connectivity (?): Not Executed
    IPv6 and Your Web Browser (?): No IPv6 Support
    IPv6 Path MTU (?): Not Executed
    IPv6 Traceroute (?): Not Executed
    Host Properties –
    System clock accuracy (?): Warning
    Your computer’s clock is 185 seconds fast.
    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 5.1; es-ES) AppleWebKit/533.19.4 (KHTML, like Gecko) Version/5.0.3 Safari/533.19.4
    Accept: application/xml,application/xhtml+xml,text/html; q=0.9,text/plain; q=0.8,image/png,*/*; q=0.5
    Accept Language: es-ES
    Accept Encoding: gzip, deflate
    Accept Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
    Java identifies your operating system as Windows XP.
    Uploaded Data (?): OK
    The following additional content was uploaded by the applet:
    raw_http_content

    • http://twitter.com/iFanini Carlos Fanini

      Saludos Fernando,

      Si no tienes ningún tipo de Firewall configurado para tu conexión, tus resultados indican que tu proveedor de Internet bloquea y filtra varios protocolos, pero lo que veo con más gravedad es la manipulación de algunos dominios por el servidor DNS de tu proveedor. Te sugiero que hagas la prueba varias veces para confirmar si los resultados siempre son los mismos.

      Gracias por visitarnos. =)

      • Fernando Cabrera

        Muchas gracias por tu rapida respuesta

        • http://twitter.com/iFanini Carlos Fanini

          De nada. Para eso estamos.

          Saludos,

  • Znarfrivero

    que hago con todo estooooooo???? ayudenme por favoooooooooooor!!!!:
    Summary of Noteworthy Events –
    Minor Aberrations
    Certain TCP protocols are blocked in outbound traffic
    Certain UDP protocols are blocked in outbound traffic
    The measured network latency 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
    Virus filtering appears to be present on your host or network
    The network blocks some or all EDNS replies
    Your computer’s clock is slightly fast
    Address-based Tests +
    NAT detection (?): NAT Detected
    Local Network Interfaces (?): OK
    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) 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 connection succeeded but came from a different IP address than we expected. Instead of the expected IP address, we received this request from 200.108.109.179.
    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 connections to remote HTTPS servers (port 443) succeed, but do not receive the expected content.
    The applet received an empty response instead of our normal banner. This suggests that a firewall, proxy, or filter initially allowed the connection and then terminated it, either because it did not understand our server’s reply or decided to block the service.
    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 connections to remote POP/SSL servers (port 995) succeed, but do not receive the expected content.
    The applet received an empty response instead of our normal banner. This suggests that a firewall, proxy, or filter initially allowed the connection and then terminated it, either because it did not understand our server’s reply or decided to block the service.
    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 (?): Note
    Basic UDP access is available.
    The applet was able to send fragmented UDP traffic.
    The applet was able to receive fragmented UDP traffic.
    UDP access to remote DNS servers (port 53) appears to pass through a firewall or proxy. The applet was unable to transmit an arbitrary request on this UDP port, but was able to transmit a legitimate DNS request, suggesting that a proxy, NAT, or firewall intercepted and blocked the deliberately invalid request.
    Direct UDP access to remote NTP servers (port 123) is allowed.
    Direct UDP access to remote OpenVPN servers (port 1194) is allowed.
    Direct UDP access to remote MSSQL servers (port 1434) is allowed.
    Traceroute (?): OK
    It takes 17 network hops for traffic to pass from our server to your system, as shown below. For each hop, the time it takes to traverse it is shown in parentheses.
    None (0 ms)
    ec2-75-101-160-162.compute-1.amazonaws.com (0 ms)
    None (0 ms)
    *
    *
    *
    *
    xe-0-4-0-7.r02.asbnva02.us.bb.gin.ntt.net (1 ms)
    ae-5.r20.asbnva02.us.bb.gin.ntt.net (17 ms)
    ae-6.r23.nycmny01.us.bb.gin.ntt.net (7 ms)
    ae-1.r06.nycmny01.us.bb.gin.ntt.net (7 ms)
    *
    xe-6-4.r00.nycmny13.us.ce.gin.ntt.net (117 ms)
    None (119 ms)
    None (118 ms)
    *
    *
    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.
    Network Access Link Properties –
    Network latency measurements (?): Latency: 340ms Loss: 0.5%
    The round-trip time (RTT) between your computer and our server is 340 msec, which is somewhat high. This may be due to a variety of factors, including distance between your computer and our server, a slow network link, or other network traffic.
    We recorded a packet loss of 0.5%. This loss rate is within the range commonly encountered and not usually inducing significant performance problems. Of the packet loss, at least 0.5% of the packets appear to have been lost on the path from your computer to our servers.
    TCP connection setup latency (?): 1600ms
    The time it takes for your computer to set up a TCP connection with our server is 1600 msec, which is quite high. This may be due to a variety of factors, including a significant distance between your computer and our server, a particularly slow or poor network link, or problems in your network.
    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 130 Kbit/sec, Download 110 Kbit/sec
    Your Uplink: We measured your uplink’s sending bandwidth at 130 Kbit/sec. This rate could be considered somewhat slow, and may affect your user experience if you perform large transfers.
    Your Downlink: We measured your downlink’s receiving bandwidth at 110 Kbit/sec. This rate could be considered quite slow, and will affect your user experience if you perform large transfers.
    Network buffer measurements (?): Uplink 990 ms, Downlink 3500 ms
    We estimate your uplink as having 990 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 3500 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 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.
    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. Thus, the proxies along your path are able to transparently forward invalid HTTP traffic.
    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)
    netalyzrStatus = running (set by our server)
    Your web browser was unable to fetch an image using IPv6.
    DNS Tests –
    Restricted domain DNS lookup (?): OK
    We can successfully look up 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 can successfully look up arbitrary names from within the Java applet. This means we are able to conduct all test on your DNS server.
    Direct DNS support (?): OK
    All tested DNS types were received OK
    Direct EDNS support (?): Note
    EDNS-enabled requests for small responses are answered successfully.
    EDNS-enabled requests for medium-sized responses remain unanswered. This suggests that a proxy or firewall is unable to handle extended DNS requests or DNS requests larger than 512 bytes.
    EDNS-enabled requests for large responses remain unanswered. This suggests that a proxy or firewall is unable to handle large extended DNS requests or fragmented UDP traffic.
    DNS resolver address (?): OK
    The IP address of your ISP’s DNS Resolver is 200.108.96.212, which resolves to dns1.amx.com.pe. Additional nameservers observed for your host: 200.108.96.213
    DNS resolver properties (?): Lookup latency 459ms
    Your ISP’s DNS resolver requires 459 msec to conduct an external lookup.
    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 0×20 randomization, but will pass names in a case-sensitive manner.
    We were unable to detect a DNS proxy associated with your NAT.
    Your ISP’s DNS server cannot use IPv6.
    No transport problems were discovered which could affect the deployment of DNSSEC.
    DNS glue policy (?): OK
    Your ISP’s DNS resolver does not accept generic additional (glue) records — good.
    Your ISP’s DNS resolver does not accept additional (glue) records which correspond to nameservers.
    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.

    DNS lookups of popular domains (?): OK
    80 of 80 popular names were resolved successfully. Show all names.
    12 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.
    One 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 external proxy (?): OK
    Your host ignores external DNS requests.
    DNS results wildcarding (?): OK
    Your ISP correctly leaves non-resolving names untouched.
    IPv6 Tests +
    DNS support for IPv6 (?): OK
    IPv6 Connectivity (?): Not Executed
    IPv6 TCP connectivity (?): Not Executed
    IPv6 and Your Web Browser (?): No IPv6 Support
    IPv6 Path MTU (?): Not Executed
    IPv6 Traceroute (?): Not Executed
    Host Properties –
    System clock accuracy (?): Warning
    Your computer’s clock is 20 seconds fast.
    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 5.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.107 Safari/534.13
    Accept: application/xml,application/xhtml+xml,text/html; q=0.9,text/plain; q=0.8,image/png,*/*; q=0.5
    Accept Language: es-419,es;q=0.8
    Accept Encoding: gzip,deflate,sdch
    Accept Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
    Java identifies your operating system as Windows XP.
    Uploaded Data (?): OK
    The following additional content was uploaded by the applet:
    raw_http_content

    • http://twitter.com/iFanini Carlos Fanini

      Saludos,

      Si no tienes algún tipo de Proxy o Firewall propio los resultados quieren decir que tu proveedor de Internet está bloqueando ciertos puertos y protocolos. Tu conexión presenta una latencia considera muy alta para que el uso de Voz sobre IP o Juegos en línea funcionen correctamente.

      Te aconsejo que hagas varias pruebas para comprobar que los resultados sean los mismos siempre.

  • Manny

    Hola, me han referido a esta pagina cuando le conté a un amigo mi problema. Resulta que tengo el servicio flash de codetel y funciona bastante bien (sin tomar en cuenta que cuando llueve se cae la conexión :P … no me pregunten porque, ya he revisado 200 veces el cableado) en fin, es bastante estable, pero desde 1 semana aprox. al día de hoy ocurre un evento bastante raro y es que la conexión funciona estable desde la manana hasta aprox. las 10pm que es cuando se cae o funciona fatal… según el Internet conexión test que tienen los speedtouch dice que no me puedo conectar al 196.3.81.5…. cualquier ayuda sera agradecida. Manny.-

    • http://twitter.com/iFanini Carlos Fanini

      Saludos Manny,

      Gracias por visitar nuestro Blog. Al parecer el problema que tienes esta relacionado con los DNS de Codetel. En PC cambia los DNS de Codetel por estos >> 208.67.222.222
      208.67.220.220. Creo que con eso no tendrás más problemas de conexión. Si no sabes como cambiarlos DNS me dejas saber por aquí mismo.

  • http://twitter.com/ddefillo Daniel Defillo

    Otro articulo caido del cielo, gracias Carlos.

    Desde la semana pasada mi servicio de Tricom ADSL de 1Mbps-256Kbps no me deja ni bajar torrents ni jugar World Of Warcraft, he llamado varias veces y me dicen que todo esta bien del lado de ellos que me mandaran un tecnico (el cual seguro llegara antes de Navidad).

    Aqui mi reporte http://n2.netalyzr.icsi.berkeley.edu/restore/id=43ca208a-16067-930c7bf0-4564-4454-877e/rd

    Que verdugos!

    • http://twitter.com/iFanini Carlos Fanini

      Saludos Daniel,

      Si estas pagando por una conexión de 1mbit estas pagando demás. En tu resultado no pasaste de 250kbits. Si puedes trata de hacer la prueba de nuevo para estar seguro. También presenta Buffering excesivo. Para que veas lo que es el Buffering puedes visitar este link >>> http://ejercitogeek.net/2011/01/bufferbloat/ y veras porque es tan grave el problema.

      • http://twitter.com/ddefillo Daniel Defillo
        • http://twitter.com/iFanini Carlos Fanini

          Saludos Daniel,

          ¿Tienes algún tipo de Firewall en tu casa? En ambos resultados dice que te están bloqueando el puerto de Bittorrent. Verifica y déjame saber.

          • http://twitter.com/ddefillo Daniel Defillo

            El unico firewall que tengo es el de windows 7 y los Bittorrents dicen estar autorizados… es mi ISP, no es la primera vez que tengo problemas con ellos, incluso hice un cambio de tecnologia a ADSL para escapar el estar 15 dias al mes sin internet y estuve todo perfecto por casi 6 meses… mucho duraron, lo grave es que vivo a menos de una cuadra de ellos! Asi mismo tengo 1 semana sin cable por una averia masiva, lacual aparentemente solo me afecta a mi, mis vecinos tienen cable…

            Aprovechare que me mudo para cancelar con ellos todos los servicios, mientras sabes si el servicio de Wind de TV e internet es bueno? creo que me voy con ellos…

            Ahh y gracias de veras por tu ayuda!

    • http://cesargarnier.blogspot.com Cesar Garnier

      Daniel,

      Recomendacion personal por mas de 4 anios consecutivos. Utiliza el cliente de uTorrent para descargar tus torrents.

      • http://twitter.com/ddefillo Daniel Defillo

        ese es el que utilizo desde que salio, gracias Cesar!

        • http://cesargarnier.blogspot.com Cesar Garnier

          Daniel,

          Una pregunta, ya seguiste la guía de “µTorrent Connection Setup Guide”. Yo donde quiera que voy sigo esa guía para resolver cualquier inconveniente que tenga en la descarga de mis torrents. Vaya, la mayoría de las veces la configuración no se hace en la PC sino en el router y/o modem de banda ancha que tengan en tu localidad.

          BTW, dices que tienes TRICOM y me gustaria saber el modelo del modem que tienes para ver si puedo ayudarte. Porque tengo mala experiencia con TRICOM tratando de lograr que los clientes torrent funcionen al 100%. No se si son los modem que dan o si es el ISP que tienen buen control sobre este protocolo.

          • http://twitter.com/ddefillo Daniel Defillo

            Cesar, estaba usando mi conexion (desde aporximadamente 6-7 meses) bajando torrents y jugando WoW sin problemas hasta hace casi dos semanas, siempre he utilizado el µTorrent Connection Setup Guide cuando lo instalo o actualizo.

            Mi conexion simplemente un dia dejo de funcionar.

            Consegui el acceso a mi router (ClearAccess-en mi vida habia escuchado de esta marca, pero Amen) e incluso intente habilitando los puertos 6881-6889 pero sigue todo horrible y los torrents y cualquier actualizacion fallan (ubuntu me tiro una actualizacion y fallo asi como tambien WoW no entra al juego porque se desconecta al intentar despues de un buen rato tratando)

            Me habia pasado algo similar con el Cable modem y siempre me hablaban de averia masiva que aparentemente solo me afectaba a mi y otras veces era que el nodo se dañaba por el alto trafico que tenia, me habian recomendado el cambio de tecnologia a ADSL como solucion de todos mis problemas y 6 meses despues se empiezan a repetir… con la agravante de que tengo sin cable esta semana entera por una averia masiva que ninguno a de mis vecinos afecta.

            El tecnico no acaba de llegar y mientras uno paga al dia por un servicio que no esta recibiendo. Mi unico consuelo es que al menos me funciona algo de internet para poder desahogar mi frustracion.

  • Fuegolin
    • http://twitter.com/iFanini Carlos Fanini

      Por tus resultados puedo decirte que estamos en el mismo bote. Buffer excesivo lo que hace que no pueda hacer una video conferencia con buena calidad. No se porque Wind Telecom tiene la mayoría de sus IP blacklisted como spammers. Algo que también he podido notar es que ahora no logro pasar de 10mbits y en tu prueba pasa lo mismo también. Hice otras pruebas desde una PC con Linux y pude detectar que también están limitando la velocidad en ciertos protocolos como HTTP y FTP. Antes podía ver videos en Youtube sin problema y ahora no.

      • http://cesargarnier.blogspot.com Cesar Garnier

        Carlos,

        Sobre tu conexion de Wind Telecom. Estas notando que estan limitando el ancho de banda por conexion? Que tanto se ha degradado el servicio? Me interesa saber mas, ya que tengo en agenda de unos 7 dias hacer una instalacion de servicio de internet en mi residencia.

        • http://twitter.com/iFanini Carlos Fanini

          Cesar,

          En estos últimos días ha presentado varias averías. Hoy ha vuelto a la normalidad, pero tengo la sospecha de que aveces limitan las conexiones en horas pico. Hoy haré una prueba más profunda para ver si puedo volarme esas restricciones.

  • http://twitter.com/iFanini Carlos Fanini

    Es interesante que la mayoría de ISP tienen sus trucos sucios que van desde bloqueandote puertos y protocolos a manipulación de las consultas que haces a sus servidores DNS.

  • http://twitter.com/purocodigo Puro Codigo

    Carlos: Que tan confiable es Netalyzr ? El firewall Eset Smart Security lo detecta como malware y envia el aplet a cuarentena. Apenas le hice click y di un vistazo. Luego revisaré mas a fondo.

    Melvyn

    • http://twitter.com/iFanini Carlos Fanini

      Hice varias pruebas en diferente equipos y nunca vi ninguna alerta. La mayoría de los equipos corren Windows. Es muy confiable, es Berkeley =)

      • http://twitter.com/purocodigo Puro Codigo

        Hoy volvi a revisar. La alerta de virus que sale es por EICAR: http://en.wikipedia.org/wiki/EICAR_test_file, dejé que el test siga corriendo a ver que dicen los restultados y comparar Wind/Claro.

  • http://twitter.com/iFanini Carlos Fanini

    Miren que interesante. Mientras conectado a una conexión de Codetel, si hago un dns lookup de http://www.google.com devuelve una IP de codetel.

    Nombre: http://www.l.google.com
    Address: 190.167.241.147
    Aliases: http://www.google.com

    Nombre: 147.241.167.190.d.dyn.codetel.net.do
    Address: 190.167.241.147

    Name IP Address Reverse Name/SOA
    ad.doubleclick.net 190.167.241.152 152.241.167.190[...].codetel.net.do
    encrypted.google.com 190.167.241.144 144.241.167.190[...].codetel.net.do
    http://www.google.com 190.167.241.147 147.241.167.190[...].codetel.net.do
    http://www.google-analytics.com 190.167.241.144 144.241.167.190[...].codetel.net.do
    partner.googleadservices.com 190.167.241.149 149.241.167.190[...].codetel.net.do

    Name IP Address Reverse Name/SOA
    http://www.barclays.co.uk 212.140.250.32 X (ns0.bt.net)
    http://www.bing.com 190.167.241.98 98.241.167.190.[...].codetel.net.do
    http://www.deutsche-bank.de 160.83.8.24 X (ns2.db.com)
    http://www.f-secure.com 190.167.241.83 83.241.167.190.[...].codetel.net.do
    http://www.irs.gov 190.167.241.81 81.241.167.190.[...].codetel.net.do
    http://www.lloydstsb.com 141.92.130.226 X (ns0.bt.net)
    http://www.mbna.com 63.236.19.110 X (ns0.teb.qwest.net)
    http://www.nordea.fi 92.43.121.130 X (ns01.tdchosting.dk)
    http://www.sparkasse.de 212.34.69.3 rev-212.34.69.3.rev.izb.net
    tinyurl.com 216.218.139.86
    http://www.trendmicro.com 173.222.161.214 a173-222-161-21[...]echnologies.com
    http://www.visa.com 190.167.241.82 82.241.167.190.[...].codetel.net.do

  • Anonimo

    muy interesante.

  • TECDOM
    • http://twitter.com/iFanini Carlos Fanini

      Por tus resultados tu proveedor también te está bloqueando algunos protocolos y las consultas a su servidor DNS son muy lentas. También presenta buffering excesivo y puede afectarte mucho cuando juegas en línea o uses algún servicio de VOIP.

  • http://cesargarnier.blogspot.com Cesar Garnier

    Realice la prueba con mi conexión de banda ancha 3G Claro en el parqueo de MegaCentro. No se si los resultados serán los mismos si hago la prueba cerca de una central de Claro. Pero, de todos modos quiero compartir los resultados de mi prueba.

    Datos sobre la prueba realizada:

    1. Datos segun el cliente de conexion de banda ancha 3G. (http://flic.kr/p/9d4Tsa)
    2. Datos segun el website Speed Test. (http://flic.kr/p/9d4Tun)
    3. Datos segun el website ICSI Netalyzr. (http://n3.netalyzr.icsi.berkeley.edu/restore/id=ae81b058-21502-6c9de9f4-3928-4122-b9aa/rd)

    Nota: no pude detenerme hacer el análisis completo de la información por trabajo, pero lo comparto por si alguien desea mas información.

    • http://twitter.com/iFanini Carlos Fanini

      Saludos Cesar,

      Gracias por todas las pruebas.

  • Vmbatista1969
  • Luis Oneal

    bueno aqui esta mi resultado de mi analizys yo pienso que mi proveedor de internet me esta limitando la conexion mas del 50% espero estar equivocado……

    http://n3.netalyzr.icsi.berkeley.edu/summary/id=ae81b058-21487-c52009c2-d152-4b00-8ebb

    • http://cesargarnier.blogspot.com Cesar Garnier

      Estuve revisando los detalles de tu prueba. Podrías enriquecer el tema ofreciéndonos información sobre tu proveedor de servicio y el servicio contratado que tienes. Y segundo estas utilizando los servicios de OpenDNS o algun servicio de DNS alterno al que tienes con tu proveedor de servicio?

    • http://twitter.com/iFanini Carlos Fanini

      Saludos Luis,

      Tu conexión también presenta bloqueos de diferente protocolos y existe un servidor proxy entre tu y tu proveedor de Internet. Tu conexión presente mucha latencia y eso es grave para jugar en línea y hablar por Skype y otros servicios de VOIP.