The ICSI Netalyzr Start » Analysis » Results Result Summary + – (help) pool-{edited for privacy}.phlapa.fios.verizon.net / {edited for privacy} Recorded at 13:40 EST (18:40 UTC), Dec 15 2013. Permalink. Client/server transcript. Summary of Noteworthy Events + – Major Abnormalities – Your DNS resolver returns IP addresses for names that do not exist Minor Aberrations – Certain UDP protocols are blocked in outbound traffic The packet loss was somewhat high The network indicated bursts of packet loss Address-based Tests + – NAT detection (?): NAT Detected + Local Network Interfaces (?): OK + DNS-based host information (?): OK + NAT support for Universal Plug and Play (UPnP) (?): Yes + Reachability Tests + – TCP connectivity (?): OK + UDP connectivity (?): Note – Basic UDP access is available. The client was able to send fragmented UDP traffic. The client was able to receive fragmented UDP traffic. UDP access to remote DNS servers (port 53) appears to pass through a firewall or proxy. The client was unable to transmit a non-DNS traffic 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 NetBIOS NS servers (port 137) is allowed. Direct UDP access to remote NetBIOS DGM servers (port 138) is allowed. Direct UDP access to remote IKE key exchange servers (port 500) is allowed. Direct UDP access to remote OpenVPN servers (port 1194) is allowed. Direct UDP access to remote Slammer servers (port 1434) is allowed. Direct UDP access to remote L2 tunneling servers (port 1701) is allowed. Direct UDP access to remote IPSec NAT servers (port 4500) is allowed. Direct UDP access to remote RTP servers (port 5004) is allowed. Direct UDP access to remote RTCP servers (port 5005) is allowed. Direct UDP access to remote SIP servers (port 5060) is allowed. Direct UDP access to remote VoIP servers (port 7078) is allowed. Direct UDP access to remote VoIP servers (port 7082) is allowed. Direct UDP access to remote SCTP servers (port 9899) is allowed. Direct UDP access to remote Steam gaming servers (port 27005) is allowed. Direct UDP access to remote Steam gaming servers (port 27015) is allowed. Traceroute (?): OK + Path MTU (?): OK + Hidden Proxy Detection (?): OK + Network Access Link Properties + – Network performance (?): Latency: 62 ms, Loss: 2.5% – The round-trip time (RTT) between your computer and our server is 62 ms, which is good. We recorded a packet loss of 2.5%. This loss rate can result in noticeable performance problems. It could be due either to significant load on our servers due to a large number of visitors, or problems with your network. Of the packet loss, at least 2.0% of the packets appear to have been lost on the path from your computer to our servers. TCP connection setup latency (?): 63ms + Background measurement of network health (?): 4 transient outages, longest: 8.0 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 8.0 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 >20 Mbit/s, Download >20 Mbit/s + Network buffer measurements (?): Uplink is good, Downlink is good + 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 120 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 199.101.28.20, which resolves to search.dnsassist.verizon.net. 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 199.101.28.20. www.{random}.org is mapped to 199.101.28.20. **bleep**.{random}.com is correctly reported as an error. www.yahoo.cmo [sic] is mapped to 199.101.28.20. nxdomain.{random}.netalyzr.icsi.berkeley.edu is correctly reported as an error. 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
↧