It would take a heck of a lot but their redirect search server appears to have gotten slower. They have also stopped resolving some bogus domain names to the wildcard that they still were resolving to the wildcard ealier yesterday. For instance, verislime.com and a lot of other unfavorable references to verisign that resolved to the wildcard now result in an immediate intentional disconnection from DNS server. Thus, this suggests to me a lot of the hits to their site have been people screwing around checking how it works, working on blocking, and making a comment about versign in the process. The only reason to block it is to reduce the load since they figure these people won't user the search anyway. Here some results. First one that resolved yesterday but doesn't now and another that still does:
$ nslookup www.verislime.com
** server can't find www.verislime.com: SERVFAIL
$ nslookup www.verislime2.com
Any if that doesn't look familar:
$ nslookup 220.127.116.11
18.104.22.168.in-addr.arpa name = sitefinder-idn.verisign.com.
A lot of other unfavorable versign bogus urls not longer resolve too.