I’ve been writing on this blog for a few years now and never really run into too major of a problem. But today I saw something that surprised me. A friend went to an article I had just written where I had posted the 220 State Parks that Arnold had noted to be closed and he was blocked:
Just so you know I get this when I click on the link:
Trend Micro URL Filter has blocked the requested Web URL by Credibility Level.
URL: http://litwc.com/2009/06/04/a-list-of-220-california-state-parks-possibly-closed/… Read More
Category: Hacking / Proxy Avoidance
Credibility Level: Dangerous
Now in looking I could find no place on their site to try and resolve this easily. So I posted a request through their sales desk:
Hello, my name is Patrick Havens.
I’ve just had a friend notify me that my site was blocked by your Trend Micro URL Filter.
– QUOTE –
Trend Micro URL Filter has blocked the requested Web URL by Credibility Level.URL: http://litwc.com/2009/06/04/a-list-of-220-california-state-parks-possibly-closed/… Read More
Category: Hacking / Proxy Avoidance
Credibility Level: Dangerous
—————
Considering the fact that domain actually has a secure certificate, and has been in existence for years. Plus the fact that blog has been around for years I’m not sure how the credibility is in question. Plus I’m not sure how it got labeled for Hacking/Proxy Avoidance. I do touch on a number of subjects, but off hand I can’t remember an article related as such. But to be considered “Dangerous”?
Please let me know how I can “safelist” my site.
As you can sorta see I’m at a loss for words per say. I do have the request in, and I hope to see this resolved soon.
Tags: Blocked Blogs, Blocked Sites, Blogging, Censorship, Help, Trend Micro, URL Filtering
They got back to me today. And they asked for some basic information. We’ll see what comes up.
How did this turn out ?
I just had this happen with a site that was new, which blew me away.
It took a couple weeks but they finally called me up and told me that they had fixed it.
I contacted the friends who had, had the issues and they where able to get to the site again.
One fix I had been able to get them to do was go to the secure version of this site. Not sure why that worked, but it did.