HostExploit states Oversee.net is improving, making a case study
HostExploit applauds Oversee.net for fixing problems that landed it at top spot at recent “Bad Hosts” list.
HostExploit, a group that compiles a list of what it calls “Bad Hosts”, no longer lists Oversee.net as the #1 bad host.
In its fourth quarter note, the group states Oversee.net is now ranked as the #12 bad host.
Why? It’s kind of hard to tell. Last quarter I reached out to both Oversee.net and HostExploit regarding the ranking. I heard back from neither so I guess I’m on my own to interpret the results.
But HostExploit applauds Oversee.net in its latest note, stating:
For a responsible host, the shock of finding they are ranked unusually high, or even worse in the #1 position, can be enough to prompt immediate remedial action.
Take, for example, the Q3 2011 #1 overall Bad Host (#1 for both Badware and Infected sites) AS33626 Oversee.net. This client oriented reseller swiftly investigated the causes behind its undesired status. The introduction of a clean-up program and fresh procedures promptly reversed the trend. (More on this in a future case study.)
The clean-up for Oversee.net progresses with an added confidence that their high ranking will drop further and take them off the #1 spot for badware.
Indeed, Oversee.net is still ranked #1 for badware. But the note notes that it continues to work on negating false positives for badware on parked domains. (Oversee.net is parent firm of domain parking firm DomainSponsor.)
Sedo is also on the overall “bad” list at #39. Google is ranked #43.
