Summary of Noteworthy Events + – Minor Aberrations – Fragmented UDP traffic is blocked The time to set up a TCP connection was somewhat high The network indicated bursts of packet loss Network packet buffering may be excessive Not all DNS types were correctly processed 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 tested + Reachability Tests + – TCP connectivity (?): OK + UDP connectivity (?): Note – Basic UDP access is available. The client 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 client was unable to receive fragmented UDP traffic. The most likely cause is an error in your network's firewall configuration or NAT. The maximum packet successfully received was 1472 bytes of payload. 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 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: 100 ms, Loss: 0.0% + TCP connection setup latency (?): 1900ms – The time it takes for your computer to set up a TCP connection with our server is 1900 ms, 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. Background measurement of network health (?): 1 transient outages, longest: 10.6 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 1 such outages. The longest outage lasted for 10.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 1.9 Mbit/s, Download >20 Mbit/s + Network buffer measurements (?): Uplink 1400 ms, Downlink 180 ms – We estimate your uplink as having 1400 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 180 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 + Sensitive proxy-introduced HTTP headers (?): OK + DNS Tests + – Restricted domain DNS lookup (?): OK + Unrestricted domain DNS lookup (?): OK + DNS resolver address (?): OK + DNS resolver properties (?): Lookup latency 240 ms + Direct probing of DNS resolvers (?) – Your system is configured to use 2 DNS resolver(s). The resolver at 77.244.98.19 (resolver1-1.inexio.net) could not process the following tested types: Large (~3000B) TXT records fetched with EDNS0 Requests from this resolver come from 77.244.98.20. This resolver requires 238 ms to fetch a result from our server and 113 ms to return a result from its cache. It validates DNSSEC. It provides DNSSEC records upon request. It does not wildcard NXDOMAIN errors. The resolver reports a number of additional properties. Show them. The resolver at 77.244.99.19 (ns2.inexio.net) could not process the following tested types: Large (~3000B) TXT records fetched with EDNS0 Requests from this resolver come from 77.244.99.19. This resolver requires 201 ms to fetch a result from our server and 22 ms to return a result from its cache. It validates DNSSEC. It provides DNSSEC records upon request. 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 (?): OK + DNS results wildcarding (?): OK + 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