Yahoo: Since you can get to my web site but I cannot I don't know what to say. I tried serveral times through various proxies at proxy.org and ALL of them will get me to SecureMecca.com. But I still cannot make it through native which is what MUST be done for people to pull down the downloads I have there. I have NO problems ftp'ing to the web site. The breakdown occurred shortly after I uploaded my PAC filter files and was also able to get them via wget to compare them at about 2011-08-06 15:02 UTC Shortly thereafter I was no longer able to reach the web site. I still cannot reach it as of: 2011-08-07 02:54 UTC PLEASE DO NOT CALL ME! When I can reach my web site I will replace this message with one that says: IT WORKS! The next item is an email message from somebody in London that also cannot make it into securemecca.com.com. ============================================================== From: "Steven Burn" REDACTED To: Cc: "'Rodney'" REDACTED "'Airelle'" REDACTED References: <4E3D6F3C.3030908@securemecca.com> In-Reply-To: <4E3D6F3C.3030908@securemecca.com> Subject: RE: removals Date: Sat, 6 Aug 2011 17:50:45 +0100 Organization: Ur I.T. Mate Group Message-ID: <00d601cc5458$fcf6cdf0$f6e469d0$@co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcxUWAS5PkBQBPCYQ8q4Z1J34ZCNqQAAMkoQ Content-Language: en-gb Henry, Just checked and your securemecca site is down from here. Regards Steven Burn Ur I.T. Mate Group www.it-mate.co.uk > For some reason I cannot even see my web site any more: > > http://www.securemecca.com/hdate.txt > http://www.securemecca.com/pdate.txt > > I suspect it is Comcast's Dambala Anti-bot software. Could > you people going through some other ISP than Comcast verify > this for me? > > HHH > -- > I hear and I forget. I read and I remember. I do and > I understand. - paraphrase of Confucius ============================================================== It STILL DOES NOT WORK! Here is what happens when I do a simple wget in an xterm: $ wget --tries=3 www.securemecca.com/hdate.txt --2011-08-07 14:54:45-- http://www.securemecca.com/hdate.txt Resolving www.securemecca.com... 68.180.151.96 Connecting to www.securemecca.com|68.180.151.96|:80... connected. HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers. Retrying. --2011-08-07 14:54:46-- (try: 2) http://www.securemecca.com/hdate.txt Connecting to www.securemecca.com|68.180.151.96|:80... connected. HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers. Retrying. --2011-08-07 14:54:49-- (try: 3) http://www.securemecca.com/hdate.txt Connecting to www.securemecca.com|68.180.151.96|:80... connected. HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers. Giving up. In the browser it just INSTANTLY gives up. Now I can understand a browser caching problem which is why I used wget to illustrate the problem. I AM NOT THE ONLY ONE EXPERIENCING THESE PROBLEMS! You can see from the above the experience that Steven Burn in the UK is having. Here is a far more complete analysis by Airelle in Strasbourg, France: ============================================================== Hello, > > Also, for some reason I cannot even see my web site any more: > > http://www.securemecca.com/hdate.txt > > http://www.securemecca.com/pdate.txt > > Could you people going through some other ISP than Comcast verify this for me? See the log (I tried several times). Regards, Airelle HHH.log nslookup hostsfile.org Server: 89.2.0.1 Address: 89.2.0.1#53 Non-authoritative answer: Name: hostsfile.org Address: 74.208.21.21 traceroute to hostsfile.org (74.208.21.21), 30 hops max, 60 byte packets 1 10.52.128.1 (10.52.128.1) 15.562 ms 15.706 ms 15.815 ms 2 213-245-252-113.rev.numericable.fr (213.245.252.113) 15.942 ms 16.024 ms 16.153 ms 3 the1rj-ae2.0.numericable.net (80.236.7.121) 30.052 ms 29.788 ms 34.530 ms 4 ae-0-0.bb-a.bv.crb.fr.oneandone.net (212.227.120.34) 35.018 ms 35.421 ms 35.783 ms 5 so-4-1.bb-c.fil.qas.us.oneandone.net (212.227.120.38) 116.363 ms 119.071 ms 119.505 ms 6 te-2-2.bb-c.ms.mkc.us.oneandone.net (74.208.6.101) 162.945 ms 154.403 ms 149.058 ms 7 te-1-4.bb-c.slr.lxa.us.oneandone.net (74.208.6.106) 149.183 ms 154.627 ms 154.353 ms 8 ae-1.gw-dista-a.slr.lxa.oneandone.net (74.208.1.105) 161.023 ms 160.751 ms 160.456 ms 9 vl-987.gw-psnt1a.slr.lxa.us.oneandone.net (74.208.1.140) 161.419 ms 161.117 ms 160.924 ms 10 74.208.21.21 (74.208.21.21) 161.554 ms 163.169 ms 162.679 ms nslookup securemecca.com Server: 89.2.0.1 Address: 89.2.0.1#53 Non-authoritative answer: Name: securemecca.com Address: 68.180.151.74 traceroute to www.securemecca.com (68.180.151.74), 30 hops max, 60 byte packets 1 10.52.128.1 (10.52.128.1) 12.194 ms 12.303 ms 12.489 ms 2 213-245-252-113.rev.numericable.fr (213.245.252.113) 12.644 ms 12.815 ms 12.890 ms 3 cbv1rj-ae5.0.numericable.net (80.236.6.92) 31.603 ms 31.310 ms 31.043 ms 4 xe0-0-0.tcr1.telx.nyc.as8218.eu (83.167.63.141) 104.046 ms 102.875 ms 103.023 ms 5 yahoo.tienyc.telxgroup.net (206.126.115.19) 107.686 ms 107.839 ms 108.024 ms 6 ae-1-d181.pat1.dax.yahoo.com (216.115.104.114) 114.946 ms 105.576 ms 107.860 ms 7 ae-7.pat2.che.yahoo.com (216.115.100.137) 145.673 ms 126.013 ms as-0.pat2.da3.yahoo.com (216.115.101.155) 159.687 ms 8 ae-6.pat1.dnx.yahoo.com (216.115.96.207) 197.022 ms 196.762 ms as-1.pat2.sjc.yahoo.com (216.115.101.151) 195.567 ms 9 ae-1-d151.msr2.sp1.yahoo.com (216.115.107.79) 196.542 ms ae-1-d171.msr2.sp1.yahoo.com (216.115.107.87) 195.725 ms 196.130 ms 10 gi-1-35.bas-b2.sp1.yahoo.com (98.136.16.37) 195.976 ms gi-1-43.bas-b2.sp1.yahoo.com (209.131.32.37) 195.839 ms gi-1-48.bas-b2.sp1.yahoo.com (209.131.32.55) 195.547 ms 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * ============================================================== YOU HAVE A SERIOUS PROBLEM WITH YOUR ROUTING! There are two cases opened on this. This first one shows that it is resolved: Case 12075238 (KMM27170272V71449L0KM) The second gives a lot of PC garbage that is is not applicable to me (I work strictly from Linux). But even worse is that it still does not resolve the problem which is on your end: Troubleshooting (KMM27170858V18522L0KM) Do not ask me why it will work with the multiple proxies I tried (all of them I tried can make it) but not with three different ISPs. I suspect it could be because of a different route in but I don't have a map of your network to understand that. All I know is that proxies are normally not set up behind some ISP. They are actually out on the Internet itself. I can try mtr on Linux behind Comcast but I a pretty sure that will match Airelle's output. No it didn't. I ran it three times using: mtr -c 1 --report securemecca.com > mtrlog.txt Here is the output of the three runs in order, the first two with a hole punched through both ways for HTTP (80) and port 0-12 since I am using ICMP for the first two. My man pages doesn't show what port mtr uses but I assume since it uses ICMP 0-12 should handle it. For the last route trace I removed all of the exclusions in the firewall. HOST: GandalfTheWhite Loss% Snt Last Avg Best Wrst StDev 1.|-- world 0.0% 1 0.7 0.7 0.7 0.7 0.0 2.|-- 76.27.40.1 0.0% 1 12.2 12.2 12.2 12.2 0.0 3.|-- te-9-4-ur01.orem.ut.utah. 0.0% 1 8.4 8.4 8.4 8.4 0.0 4.|-- te-8-1-ar01.saltlakecity. 0.0% 1 10.0 10.0 10.0 10.0 0.0 5.|-- 69.139.247.14 0.0% 1 10.5 10.5 10.5 10.5 0.0 6.|-- te-0-0-0-1-cr01.denver.co 0.0% 1 23.6 23.6 23.6 23.6 0.0 7.|-- 4.79.82.53 0.0% 1 35.9 35.9 35.9 35.9 0.0 8.|-- vlan51.ebr1.Denver1.Level 0.0% 1 45.8 45.8 45.8 45.8 0.0 9.|-- ae-3-3.ebr2.SanJose1.Leve 0.0% 1 46.4 46.4 46.4 46.4 0.0 10.|-- ae-62-62.csw1.SanJose1.Le 0.0% 1 46.9 46.9 46.9 46.9 0.0 11.|-- ae-13-60.car3.SanJose1.Le 0.0% 1 47.9 47.9 47.9 47.9 0.0 12.|-- YAHOO-INC.car3.SanJose1.L 0.0% 1 49.0 49.0 49.0 49.0 0.0 13.|-- ae-0-d161.msr1.sp1.yahoo. 0.0% 1 48.7 48.7 48.7 48.7 0.0 14.|-- gi-1-34.bas-b1.sp1.yahoo. 0.0% 1 49.5 49.5 49.5 49.5 0.0 15.|-- securemecca.com 0.0% 1 49.9 49.9 49.9 49.9 0.0 HOST: GandalfTheWhite Loss% Snt Last Avg Best Wrst StDev 1.|-- world 0.0% 1 0.7 0.7 0.7 0.7 0.0 2.|-- 76.27.40.1 0.0% 1 21.1 21.1 21.1 21.1 0.0 3.|-- te-9-4-ur01.orem.ut.utah. 0.0% 1 9.5 9.5 9.5 9.5 0.0 4.|-- te-8-1-ar01.saltlakecity. 0.0% 1 25.7 25.7 25.7 25.7 0.0 5.|-- 69.139.247.14 0.0% 1 9.0 9.0 9.0 9.0 0.0 6.|-- te-0-0-0-1-cr01.denver.co 0.0% 1 22.1 22.1 22.1 22.1 0.0 7.|-- 4.79.82.53 0.0% 1 36.6 36.6 36.6 36.6 0.0 8.|-- vlan51.ebr1.Denver1.Level 0.0% 1 37.2 37.2 37.2 37.2 0.0 9.|-- ae-3-3.ebr2.SanJose1.Leve 0.0% 1 68.5 68.5 68.5 68.5 0.0 10.|-- ae-62-62.csw1.SanJose1.Le 0.0% 1 54.7 54.7 54.7 54.7 0.0 11.|-- ae-13-60.car3.SanJose1.Le 0.0% 1 48.7 48.7 48.7 48.7 0.0 12.|-- YAHOO-INC.car3.SanJose1.L 0.0% 1 47.9 47.9 47.9 47.9 0.0 13.|-- ae-0-d171.msr2.sp1.yahoo. 0.0% 1 49.0 49.0 49.0 49.0 0.0 14.|-- gi-1-40.bas-b2.sp1.yahoo. 0.0% 1 50.0 50.0 50.0 50.0 0.0 15.|-- securemecca.com 0.0% 1 50.0 50.0 50.0 50.0 0.0 HOST: GandalfTheWhite Loss% Snt Last Avg Best Wrst StDev 1.|-- world 0.0% 1 0.7 0.7 0.7 0.7 0.0 2.|-- 76.27.40.1 0.0% 1 23.7 23.7 23.7 23.7 0.0 3.|-- te-9-4-ur01.orem.ut.utah. 0.0% 1 8.4 8.4 8.4 8.4 0.0 4.|-- te-8-1-ar01.saltlakecity. 0.0% 1 10.0 10.0 10.0 10.0 0.0 5.|-- 69.139.247.14 0.0% 1 10.5 10.5 10.5 10.5 0.0 6.|-- te-0-0-0-1-cr01.denver.co 0.0% 1 23.9 23.9 23.9 23.9 0.0 7.|-- 4.79.82.53 0.0% 1 35.6 35.6 35.6 35.6 0.0 8.|-- vlan51.ebr1.Denver1.Level 0.0% 1 53.1 53.1 53.1 53.1 0.0 9.|-- ae-3-3.ebr2.SanJose1.Leve 0.0% 1 46.3 46.3 46.3 46.3 0.0 10.|-- ae-62-62.csw1.SanJose1.Le 0.0% 1 46.8 46.8 46.8 46.8 0.0 11.|-- ae-13-60.car3.SanJose1.Le 0.0% 1 47.4 47.4 47.4 47.4 0.0 12.|-- YAHOO-INC.car3.SanJose1.L 0.0% 1 49.0 49.0 49.0 49.0 0.0 13.|-- ae-0-d171.msr2.sp1.yahoo. 0.0% 1 50.0 50.0 50.0 50.0 0.0 14.|-- gi-1-35.bas-b2.sp1.yahoo. 0.0% 1 48.4 48.4 48.4 48.4 0.0 15.|-- securemecca.com 0.0% 1 48.3 48.3 48.3 48.3 0.0 According to mtr I SHOULD be able to get there. But in addition to clearing the cache manually in Firefox (close the browser, cd into the: ~/.mozilla/firefox/${8-digit-hash}/Cache folder and recursively remove everything (rm -fr *), then cd .. rm -f *.mfasl Then started Firefox again (there cannot be any history because I removed it manually, not trusting Firefox to do it for me which it is supposed to do anyway when I close the browser. I flush EVERYTHING on browser close. But I still get blocked. I also tried it with both Opera and Chrome with the exact same results. Blocked. DAH (hhh)