Summary of Noteworthy Events +   –
Minor Aberrations –
Certain TCP protocols are blocked in outbound traffic
The network latency and packet loss were somewhat high
The time to set up a TCP connection was somewhat high
The network indicated bursts of packet loss
Your computer's clock is slightly slow
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 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 blocked.
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 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 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 blocked.
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: 470 ms, Loss: 10.0% –
The round-trip time (RTT) between your computer and our server is 470 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 10%. This loss is very significant and will lead to serious performance problems. It could be due either to very high load on our servers due to a large number of visitors, or problems in your network. Of the packet loss, at least 10.0% of the packets appear to have been lost on the path from your computer to our servers.
TCP connection setup latency (?): 2500ms –
The time it takes for your computer to set up a TCP connection with our server is 2500 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 (?): 39 transient outages, longest: 18.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 39 such outages. The longest outage lasted for 18.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 380 Kbit/s, Download 3.2 Mbit/s +
Network buffer measurements (?): Note +
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 250 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 (?): 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 (?): Warning –
Your computer's clock is 5 seconds slow.
Browser properties (?): OK +
Uploaded data (?): OK +
Feedback +   –
User-provided feedback –
Kindly take a moment to answer a few questions. All fields are optional. You can submit your feedback once the tests complete. If you would like to contact us with questions about your results, please send email with your session ID, or get in touch on the mailing list.
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?
WiFi
Wired
Tethered via USB
Tethered via WiFi
Where are you right now?
At home
At work
In a public setting (wifi hotspot, internet cafe, etc)
Other (please describe)