Agree with what our friend Para-Noid reports, this lies probably at the root of the avast! detection.
Other issues also needs tackling by webmaster and or hosting party alike.
Your site is a multiple IP site: issues for 54.148.211.128 → https://urlquery.net/report.php?id=1421946896860
Not so far as I can establish for 54.148.80.200 There was also a third IP used in the past.
Eddy, thank you for the links, but I can't see how they are related to my problem.
If you don't understand the results it is time you hire someone who does know. It is really not hard to understand. The scans show multiple issues that you have to fix.
Eddy, there are Domain-related issues and URL-related issues.
When dealing with domain-related issues, one should check the domain. For example, when conducting DNS checks.
When dealing with url-related issues, one should check the host/url. For example, when checking for malware.
The URL:Mal issue seems to be a domain-related one, since all our sites (for example, status.bigstash.co hosted on tumblr and blog.bigstash.co hosted on ghost.org) are also blocked. Any domain checks I’ve seen (the domain is “big stash.co”) do not raise an issue that will explain why the whole domain is blocked by Avast.
We’ve tried contacting Avast using all the available forms, but we’ve had no response. This is getting out of hand, and I’m very angry and disappointed by Avast.
Obviously, the only way to get someone at Avast to deal with this is through our lawyers.
We are still being confronted with a “End-user Non-MTA IP address” -
The first one is Spamhaus’ PBL list which is described as blocking mails from “Non-MTA IP address ranges set by outbound mail policy.”, which as far as I can see requires that the the network administrators add their networks to the list. Since the IP addresses have not been added to their list as being Non-MTA/dynamic IP addresses, I can’t see any logic in them randomly failing with that error code?