Wykryte błędy:
⦁ Major Abnormality Your ISP's DNS server is slow to lookup names ⦁ Minor Aberrations – Certain TCP protocols are blocked in outbound traffic The network indicated bursts of packet loss We received unexpected and possibly dangerous results when looking up important names Your web browser has a problem accessing IPv6 sites ⦁ 3 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. Name IP Address Reverse Name/SOA smartzone.comcast.net 68.87.20.7 X wireless.att.com 135.209.168.22 X www.yahoo.com 46.228.47.115 X ⦁ Your ISP's DNS resolver requires 1100 ms to conduct an external lookup. It takes 270 ms for your ISP's DNS resolver to lookup a name on our server. This is particularly slow, and you may see significant performance degradation as a result. ⦁ Background measurement of network health (?): 2 transient outages, longest: 1.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 2 such outages. The longest outage lasted for 1.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 buffer measurements (?): Note An unspecified error occurred during the test. You may want to re-run the tests to ensure the problem is temporary ⦁ IPv4, IPv6, and your web browser (?): IPv6 connectivity problem –Your browser successfully fetched a test image from our IPv6 server. Unfortunately, this is substantially slower than IPv4: it took 0.5 seconds longer to fetch the image over IPv6 compared to IPv4. Your browser prefers IPv4 over IPv6. ⦁ Direct TCP access to remote SMTP servers (port 25) is prohibited. This means you cannot send email via SMTP to arbitrary mail servers. Such blocking is a common countermeasure against malware abusing infected machines for generating spam. Your ISP likely provides a specific mail server that is permitted. Also, webmail services remain unaffected. 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 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.
