There’s a website that I want to visit and recently when I’ve attempted to open the URL I get a message of “This domain has been blocked” on a blank page. I’m using Win2k on an elderly machine, I don’t have the domain blocked in my hosts file and I’ve flushed my DNS several times to no avail and when I ping the domain it works! Plus I’m not using an active antivirus (AVG Free 8 point whatever is installed) nor am I using a firewall program.
Being marginally smarter than the average bear, I used the IP address instead of the domain name and I can visit this website.
Funny thing, when I open the website with Firefox under FreeBSD using the same ISP the name gets resolved and the site opens normally without me having to resort to an unfriendly IP address.
What is going on here? Are there any fixes so I can visit it under Win2k using the domain name rather than the IP?
Firefox 2.0 w/ Win2k and BSD.
Apparently I am unable to delete my own post nor am I capable of editing my post. No big deal but just sayin’ since I don’t want to be yelled at for flooding or whatever you guys might call it.
Find your localhost file (you should be able to find the location quite easily on google if you don’t know where), open it with notepad and see if anything is muddying it up.
Hell, search for the DNS on Google, the spiders say it’s blocked as well. I’d say it’s some sort of weird issue on their end.
Personally firefox tells me its IP is invalid though (it is responding to ping however).
are you using 216.8.179.23? Because that’s not getting me any results.
Edit: Are you sure you’re not talking about 420chan.org? Because that site is actually responding. I tried it because 4chan is similarly a .org website.
Sounds like a DNS issue - it seems to me (without investigation, since I am at work) that the DNS servers are redirecting the connection to give the response that you are seeing.
This could be via a malicious DNS Poisoning attack, or it could be because the actual site is hosting some malware, and someone with control of the DNS (maybe your ISP or their DNS provider, or the root DNS provider) has decided that everyone is better off not going there, and has added the redirection.
If it is a DNS Poisoning attack, it should get sorted eventually. If it is a DNS provider image, the webserver admin will have to sort out the problem and get the DNS Providers to remove the redirection.
Running as a working chan through last May. In June, this appears:
In July:
In September it’s finally back online. Sometime between early October and early December, though …
The chan was back online again for Christmas. However, it went offline again before April 2008. The last archive, in May, had the “Domain Temporarily Suspended” message.