Got a hissy URL error from offensive url

Went here to analyze code with jsunpack: -http://htpcapital.com/main.php?page=98d3bf6d08596d13
Then I get this Returned: (referer=www.google.com/trends/hottrends) failure: <urlopen error [Errno 104] Connection reset by peer>
I get ping resuts on the second trial, after a hiss: — PING htpcapital.com (79.137.237.67) 56(84) bytes of data. —
64 bytes from 79.137.237.67: icmp_req=1 ttl=54 time=134 ms
64 bytes from 79.137.237.67: icmp_req=2 ttl=54 time=132 ms
64 bytes from 79.137.237.67: icmp_req=3 ttl=54 time=138 ms
64 bytes from 79.137.237.67: icmp_req=4 ttl=54 time=135 ms

htpcapital.com ping statistics —
packets transmitted 4
received 4
packet loss 0 %
time 3004 ms

— Round Trip Time (rtt) —
min 132.906 ms
avg 135.176 ms
max 138.323 ms
mdev 2.061 ms

Traceroute: traceroute to 79.137.237.67 (79.137.237.67), 30 hops max, 60 byte packets
1 * * *
2 hos-tr2.juniper1.rz10.hetzner.de 213.239.224.33 de 52.781 ms 52.780 ms
hos-tr4.juniper2.rz10.hetzner.de 213.239.224.97 de 0.157 ms
3 hos-bb1.juniper4.ffm.hetzner.de 213.239.240.230 de 6.157 ms 6.139 ms
hos-bb1.juniper1.ffm.hetzner.de 213.239.240.224 de 4.782 ms
4 sr1.stk1.ip.di-net.ru 80.81.194.74 de 25.433 ms 25.413 ms 25.418 ms
5 vl-724.br1.msk1.ip.di-net.ru 213.248.3.252 ru 43.717 ms 43.711 ms 43.693 ms
6 vl-711.br2.msk1.ip.di-net.ru 213.248.3.136 ru 43.669 ms 43.574 ms 42.983 ms
7 te4-6.sr2.msk4.ip.di-net.ru 213.248.3.129 ru 43.184 ms 43.630 ms 43.456 ms
8 vl-708.sr3.msk7.ip.di-net.ru 213.248.3.131 ru 43.906 ms 44.185 ms 43.433 ms
9 vl-709.sr5.msk7.ip.di-net.ru 213.248.3.133 ru 43.420 ms 43.410 ms 43.647 ms
10 * * *
11 * * *

Is this firewall related, or just the offensive url with name=“Twitter” scrolling=“auto” frameborder=“no” align=“center” height = “1px” width = “1px”>

Do not see any reports on 79.137.237.67 misbehaving

Anyone?

polonus

Howdy,

It is not with me. My path MTU is exactly and neatly the default 1500 bytes. That has not changed, as that is the most likely cause of these kind of hick-ups. When I get an answer form the “learned g33ks” at ICSI Netalyzer at berkeley.edu, I might let you know what caused it or it must have been something local at jsunpack…

polonus