Is the "rogue_anti-spyware" website down, or is it just my ISP having trouble?

Can't seem to get any webpage on visiting:

http://www.spywarewarrior.com/rogue_anti-spyware.htm

 

Weird, it doesn't work for me either. In fact, the whole spywarewarrior.com site seems to be down.

 

I get the 'Not Found' page when I click on the link.

 

It's not quite right on my end across the river from Ron

 

The IP gives the same result as above....204.14.90.22

 

Ah hah....there is a www.spywarewarrior.com but I normally get to Suzi's site via spywarewarrior.com....with out WWW

Everything is fine with http://spywarewarrior.com on this end.

 

Getting the same site as you when visiting the http://www.spywarewarrior.com

But when visiting:
http://www.spywarewarrior.com/rogue_anti-spyware.htm

I get this:

 

Using http://spywarewarrior.com I get this:

 

To me it seems that the file rogue_anti-spyware.htm or it's Folder is inaccessible, but what do you think. Because I got the following from that traceroute (below). I think it is strange that some users are cut off from this information, and others are accessing it without problems. Has the webserver administrator set special limitations on the server?:

 

Wierd, it now seems up and going on my end. It did not last long after all.

 

Nope, I did not clear the browsers cache. I experienced all my earlier postings without doing a cleanup of the cache.

 

Well, sorry but... don't you people find it a little strange that from www.dnsstuff.com you all get the same traceroute if you put in the same target host?

That's because the traceroute shows you the packets from 66.36.240.2 to the target destination instead of the route from YOUR OWN HOST to the target destination... duh.

 

It all seems to have now cleared up on this end but it does seem to take just a little longer to actually get there @ this moment in time ?

Thanks for that fine bit of input....Duh

 

Well, still, why would anyone want to do a traceroute from another host in this case? I mean seriously... doing a trace from there only shows you whether it can be reached or not from there.

 

Some of us did not just do a traceroute from this Host you speak of. Some of us did a simple tracert which gave the IP as 204.14.90.22. It's not the info you shared....it's how it was shared

In any case all is now well on this end.

 

Well, my little criticism was obviously related to the fact that posting the image with a traceroute result from dnsstuff.com multiple times is not really useful, since they obviously all are almost identical.

It's fine on this end too anyway.

 

@ Minak,

I have pulled some related posts from this thread concerning what you wanted to discuss and created the below thread for you.

This thread---> Bazooka Adware\Spyware scanner

 

Hi, all. As an admin at SWW, I've contacted Oldfrog (another admin) who has access to be able to check this out to see what is going on.

 

Thanks all. Interesting to here more details, MadameX.