My results are pasted below. So tired of emails disappearing using iBurst or receiving emails 2 weeks after they were sent. Will be cancelling iBurst as soon as Telkom have finished installing the ADSL line ... after waiting for over 4 years for it!
Result Summary + – (help)
iburst-41-213-38-161.iburst.co.za / 41.213.38.161
Recorded at 12:05 EDT (16:05 UTC), Mar 23 2012. Permalink. Referrer. Client/server transcript.
Summary of Noteworthy Events + –
Major Abnormalities –
We detected an HTTP proxy that may be vulnerable to attack
Minor Aberrations –
The network path does not reply when it needs to fragment traffic
The measured network latency was somewhat high
The measured time to set up a TCP connection was somewhat high
Network bandwidth may be low
Network packet buffering may be excessive
We detected an HTTP proxy due to on IP address differences
We detected an HTTP proxy due to added or changed HTTP traffic
The detected HTTP proxy blocks malformed HTTP requests
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 (?): OK +
UDP connectivity (?): OK +
Traceroute (?): OK +
Path MTU (?): Warning –
The path between your network and our system supports an MTU of at least 1500 bytes, and the path between our system and your network has an MTU of 1392 bytes. The path MTU bottleneck that fails to properly report the ICMP "too big" is between 213.248.95.178 and *. The path between our system and your network does not appear to report properly when the sender needs to fragment traffic.
Network Access Link Properties + –
Network latency measurements (?): Latency: 350ms Loss: 1.5% –
The round-trip time (RTT) between your computer and our server is 350 msec, 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 1.5%. This loss rate is within the range commonly encountered and not usually inducing significant performance problems. Of the packet loss, at least 1.5% of the packets appear to have been lost on the path from your computer to our servers.
TCP connection setup latency (?): 360ms –
The time it takes your computer to set up a TCP connection with our server is 360 msec, 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.
Network background health measurement (?): no transient outages +
Network bandwidth (?): Upload 10.0 Kbit/sec, Download 470 Kbit/sec –
Your Uplink: We measured your uplink's sending bandwidth at 10.0 Kbit/sec. This rate could be considered quite slow, and will affect your user experience if you perform large transfers.
Your Downlink: We measured your downlink's receiving bandwidth at 470 Kbit/sec. This rate could be considered somewhat slow, and may affect your user experience if you perform large transfers.
Network buffer measurements (?): Uplink 350 ms, Downlink 1200 ms –
We estimate your uplink as having 350 msec of buffering. This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic.
We estimate your downlink as having 1200 msec 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 downloads. With such a buffer, real-time applications such as games or audio chat can work quite poorly when conducting large downloads at the same time.
HTTP Tests + –
Address-based HTTP proxy detection (?): Warning –
Your HTTP connections come from 196.2.126.176 while non-HTTP connections originate from 41.213.38.161, indicating that your HTTP traffic is passing through a proxy.
Content-based HTTP proxy detection (?): Warning –
Changes to headers or contents sent between the applet and our HTTP server show the presence of an otherwise unadvertised HTTP proxy.
The following headers had their capitalization modified by the proxy:
Content-Type: text/html
Content-Length: 708
Last-Modified: Fri
23 Mar 2012 16:05:45 GMT
Set-Cookie: netAlizEd=BaR; path=/; domain=netalyzr.icsi.berkeley.edu
Connection: keep-alive
The following headers were added by the proxy to HTTP responses:
X-Cache-Lookup: [MISS from fe04.iburst.co.za:3128]
X-Cache: [MISS from fe04.iburst.co.za]
Proxy-Connection: ke*ep-alive
The detected proxy reordered the headers sent from the server.
The detected HTTP proxy changed either the headers the applet sent or the HTTP response from the server. We have captured the changes for further analysis.
The detected HTTP proxy may cause your traffic to be vulnerable to CERT Vulnerability Note 435052. An attacker might be able to use this vulnerability to attack your web browser.
HTTP proxy detection via malformed requests (?): Warning –
Deliberately malformed HTTP requests do not arrive at our server. This suggests that the proxy we detected on your network path was either unable to parse or refused to forward the deliberately bad request.
Filetype-based filtering (?): OK +
HTTP caching behavior (?): Failed to complete +
JavaScript-based tests (?): OK +
DNS Tests + –
Restricted domain DNS lookup (?): OK +
Unrestricted domain DNS lookup (?): OK +
Direct DNS support (?): OK +
Direct EDNS support (?): OK +
DNS resolver address (?): OK +
DNS resolver properties (?): Lookup latency 450ms +
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 (?): +
IPv6 Tests + –
DNS support for IPv6 (?): OK +
IPv4, IPv6, and your web browser (?): No IPv6 support +
IPv6 connectivity (?): No IPv6 support +
Host Properties + –
System clock accuracy (?): OK +
Browser properties (?): OK +
Uploaded data (?): OK +
Feedback + –
User-provided feedback +
ID 43ca253f-3817-1c10f749-be0d-4ed2-9c2b
