The ability to submit "override votes" to update the domain tagging system according to DNS admins changing the sub-domains for specific services. For example, let's say the webmail service for example.com is located at mail.example.com, and was then changed to webmail.example.com by the DNS/web admins at example.com. The tag "webmail" would need to be removed from mail.example.com and applied to webmail.example.com.
This would also apply to the "parked domains" tag as well, since a legitimate site that goes live will need to be untagged as "parked".
1 Comment
This would also apply to the "parked domains" tag as well, since a legitimate site that goes live will need to be untagged as "parked".
1 Comment
re
"a legitimate site that goes live will need to be untagged as parked"
Parked domains? Literally millions of these exist. Enumerating (submitting) them seems like a HUGE waste of resources. Trying to track/update the change in status for all of 'em seems like an exercise in futility.
In contrast, there are relatively few servers warehousing sites for parked domains. Rather than neverending tagging, someone on staff at OpenDNS could monitor the common denominator(s) for the domains submitted to date, via reverse lookup. Alternatively, considering that most 'attempted monetization via parked page search engine trap' redirection utilizes 'HTTP header 302 response'...
...compilation of a short list of 'actual destination' domains would yield a practical, manageable number of blocklist entries. When a particular domain 'goes live' and no longer redirects to a flagged destination, voila. In other words -- no, "manually untagging it" wouldn't be necessary.