[Petronia]

2)Here
4)running it again

Spoiler: 

Result Summary +/– (help)
cpc5-oxfd18-2-0-cust283.4-3.cable.virginmedia.com / 217.137.121.28

Minor Aberrations
•Certain TCP protocols are blocked in outbound traffic
•Certain UDP protocols are blocked in outbound traffic
•The network blocks some or all EDNS replies
•Your computer's clock is slightly slow

Address-based Tests +
NAT detection (?): NAT DetectedYour global IP address is 217.137.121.28 while your local one is 192.168.0.3. You are behind a NAT. Your local address is in unroutable address space.
Your machine numbers TCP source ports sequentially. The following graph shows connection attempts on the X-axis and their corresponding source ports used by your computer on the Y-axis.

TCP ports are not renumbered by the network.
Local Network Interfaces (?): OKYour computer reports the following network interfaces, with the following IP addresses for each one: eth0: (an ethernet interface)eth1: (an ethernet interface)eth10: (an ethernet interface)eth11: (an ethernet interface)eth12: (an ethernet interface)eth2: (an ethernet interface)eth3: (an ethernet interface)fe80::408f:a338:d809:7356 [Daniel-PC] (a link-local IPv6 address)192.168.0.3 [Daniel-PC] (a private IPv4 address)eth4: (an ethernet interface)eth5: (an ethernet interface)eth6: (an ethernet interface)eth7: (an ethernet interface)eth8: (an ethernet interface)eth9: (an ethernet interface)lo: (a local loopback interface)::1 (an IPv6 loopback address)127.0.0.1 (an IPv4 loopback address)net0: net1: net2: net3: net4: 2001:0:5ef5:79fd:1c20:21b1:2676:86e3 [Daniel-PC] (a Teredo IPv6 address)fe80::1c20:21b1:2676:86e3 [Daniel-PC] (a link-local IPv6 address)net5: net6: fe80::5efe:c0a8:3 (a link-local IPv6 address)net7: ppp0: ppp1: DNS-based host information (?): OKYou are not a Tor exit node for HTTP traffic. You are listed on the Spamhaus Policy Based Blacklist, meaning that your provider has designated your address block as one that should only be sending authenticated email, email through the ISP's mail server, or using webmail. The SORBS DUHL believes you are using a statically assigned IP address.
NAT detection (?): NAT Detected Local Network Interfaces (?): OK DNS-based host information (?): OK

Reachability Tests –
TCP connectivity (?): NoteDirect TCP access to remote FTP servers (port 21) is allowed. Direct TCP access to remote SSH servers (port 22) is allowed. Direct TCP access to remote SMTP servers (port 25) succeeds, but does not return the expected content.

This suggests that your network enforces a mandatory SMTP proxy which may or may not allow you to send email directly from your system. This is probably a countermeasure against malware abusing infected machines for generating spam. You ISP also likely provides a specific mail server that is permitted. Also, webmail services remain unaffected.

The applet received an empty response instead of our normal banner. This suggests that a firewall, proxy, or filter initially allowed the connection and then terminated it, either because it did not understand our server's reply or decided to block the service.
Direct TCP access to remote DNS servers (port 53) is blocked.

The network you are using appears to enforce the use of a local DNS resolver.
Direct TCP access to remote HTTP servers (port 80) is allowed. Direct TCP connections to remote POP3 servers (port 110) succeed, but do not receive the expected content.
The applet received an empty response instead of our normal banner. This suggests that a firewall, proxy, or filter initially allowed the connection and then terminated it, either because it did not understand our server's reply or decided to block the service.
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 connections to remote IMAP servers (port 143) succeed, but do not receive the expected content.
The applet received an empty response instead of our normal banner. This suggests that a firewall, proxy, or filter initially allowed the connection and then terminated it, either because it did not understand our server's reply or decided to block the service.
Direct TCP access to remote SNMP servers (port 161) is allowed. 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 allowed. Direct TCP access to remote secure IMAP servers (port 585) is allowed. Direct TCP access to remote authenticated SMTP servers (port 587) is allowed. 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 (?): NoteBasic UDP access is available.
The applet was able to send fragmented UDP traffic.

The applet 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 blocked.

The network you are using appears to enforce the use of a local DNS resolver.
Direct UDP access to remote NTP servers (port 123) is allowed. Direct UDP access to remote OpenVPN servers (port 1194) is allowed. Direct UDP access to remote MSSQL servers (port 1434) is allowed.

Traceroute (?): OKIt takes 16 network hops for traffic to pass from our server to your system, as shown below. For each hop, the time it takes to traverse it is shown in parentheses.

1.None (0 ms)
2.ec2-75-101-160-172.compute-1.amazonaws.com (0 ms)
3.None (0 ms)
4.*
5.*
6.*
7.*
8.ge-4-1-0.mpr1.iad10.us.mfnx.net (1 ms)
9.xe-3-0-0.cr1.dca2.us.above.net (5 ms)
10.xe-0-0-0.cr2.dca2.us.above.net (3 ms)
11.xe-4-1-0.mpr1.lhr3.uk.above.net (75 ms)
12.xe-1-1-0.mpr2.lhr3.uk.above.net (77 ms)
13.None (81 ms)
14.brnt-bb-1b-as2-0.network.virginmedia.net (140 ms)
15.oxfd-core-1b-ge-000-0.network.virginmedia.net (101 ms)
16.oxfd-cmts-18-gigaether-151.network.virginmedia.net (87 ms)

Part 1, since it was so long that it disallowed me so i had to split it in 2