hardware ICSI Netalzyr

[Ouma Shu 159]

Fiz um teste no site ICSI pra ver como estava minha internet, e deu isso:

 

 

Summary of Noteworthy Events + –

• Major Abnormalities –

Your DNS resolver returns IP addresses for names that do not exist

 

Minor Aberrations –

• Certain TCP protocols are blocked in outbound traffic

• The network latency was somewhat high

• The time to set up a TCP connection was somewhat high

• Network packet buffering may be excessive

 

Address-based Tests + –

NAT detection (?): NAT Detected +

Local Network Interfaces (?): OK +

DNS-based host information (?): OK +

NAT support for Universal Plug and Play (UPnP) (?): 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 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 blocked.

Direct TCP access to remote secure IMAP servers (port 585) is allowed.

Direct TCP access to remote authenticated SMTP servers (port 587) is allowed.

Direct TCP access to remote IMAP/SSL servers (port 993) is allowed.

Direct TCP access to remote POP/SSL servers (port 995) is allowed.

Direct TCP access to remote OpenVPN servers (port 1194) is allowed.

Direct TCP access to remote PPTP Control servers (port 1723) is allowed.

Direct TCP access to remote SIP servers (port 5060) is allowed.

Direct TCP access to remote BitTorrent servers (port 6881) is allowed.

Direct TCP access to remote TOR servers (port 9001) is allowed.

UDP connectivity (?): OK +

Traceroute (?): OK +

Path MTU (?): OK +

Hidden Proxy Detection (?): OK +

 

Network Access Link Properties + –

Network performance (?): Latency: 420 ms, Loss: 0.5% –

The round-trip time (RTT) between your computer and our server is 420 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.

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

The time it takes your computer to set up a TCP connection with our server is 430 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 (?): no transient outages +

Network bandwidth (?): Upload 480 Kbit/s, Download 4.3 Mbit/s +

Network buffer measurements (?): Uplink 1300 ms, Downlink 390 ms –

We estimate your uplink as having 1300 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 390 ms 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 +

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 +

DNS resolver address (?): OK +

DNS resolver properties (?): Lookup latency 550 ms +

Direct probing of DNS resolvers (?): +

DNS glue policy (?): OK +

DNS resolver port randomization (?): OK +

DNS lookups of popular domains (?): OK +

DNS external proxy (?): OK +

DNS results wildcarding (?): Warning –

Your ISP's DNS server returns IP addresses even for domain names which should not resolve. Instead of an error, the DNS server returns an address of 92.242.140.20, which resolves to unallocated.barefruit.co.uk. You can inspect the resulting HTML content here.

There are several possible explanations for this behavior. The most likely cause is that the ISP is attempting to profit from customer's typos by presenting advertisements in response to bad requests, but it could also be due to an error or misconfiguration in the DNS server.

The big problem with this behavior is that it can potentially break any network application which relies on DNS properly returning an error when a name does not exist.

The following lists your DNS server's behavior in more detail.

• www.{random}.com is mapped to 92.242.140.20.

• www.{random}.org is mapped to 92.242.140.20.

• fubar.{random}.com is mapped to 92.242.140.20.

•

É necessário se cadastrar para acessar o conteúdo.

• Entre
• ou
• Cadastre-se

[sic] is mapped to 92.242.140.20.

• nxdomain.{random}.netalyzr.icsi.berkeley.edu is mapped to 92.242.140.20.

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

Direct probing of DNS roots (?): OK +

 

IPv6 Tests + –

DNS support for IPv6 (?): OK +

IPv4, IPv6, and your web browser (?): No IPv6 support +

IPv6 connectivity (?): No IPv6 support +

 

Network Security Protocols + –

DNSSEC Support from the DNS Roots (?): OK +

 

Host Properties + –

System clock accuracy (?): OK +

Browser properties (?): OK +

Uploaded data (?): OK

 

 

Legenda:

Problemas Sérios

Problemas Normais

 

Alguém entende algo e me diz se da pra arrumar isso eu mesmo, sem chamar um técnico ? (caso sejam problemas sérios)