Viewing 2 replies - 1 through 2 (of 2 total)
  • Same here. Seems like FDAS recognizes Sucuri as malicious and blocks it. However, the real culprit is the XBL list of Spamhaus, where 173.255.233.124 (the IP Sucuri used to test my site when I just tried) is registered on the CBL: https://cbl.abuseat.org/lookup.cgi?ip=173.255.233.124

    Note that Sucuri will report that your site is infected with malware, since it evaluates 500 errors as a symptom of that. Deactivating FDAS and running the test again results in a “normal” diagnosis.

    Plugin Author petervanderdoes

    (@petervanderdoes)

    Two ways to fix it:
    – Add the IP’s of the security sites to the whitelist.
    – Don’t use SpamHaus for checking.

    You can also contact the security website and inform them their IP is listed in a spam list.

    There’s not much that can be done at plugin level.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Getting sucuri flags with this plugin’ is closed to new replies.