[gvb]

At a previous job, I had this problem as well. A few filter providers block extremely aggressively and are totally unresponsive to requests.

I ended up "routing around" their brokenness by using an email delivery service (search for "email delivery service") for emails that went to domains for whom they provided filtering service.

The one I used ended up being bought by dyn https://dyn.com/email/ - the service worked well several years ago, no idea if they are still good. Amazon has SES (https://aws.amazon.com/ses/). There are quite a few others.

[joshpangell]

Thanks. It isn't email that is getting blocked, viewing the domain in a browser. Looks like the domain potentially used to host malware.

[r12477]

If this is the case, how feasible is it to adopt a new domain name? I understand that this may not be desirable, but given what appears to have been a maligned history, it may be the most prudent course of action to ensure that your new product does not suffer from guilt-by-association.

[joshpangell]

That'd be a last resort if we can't get it somehow whitelisted. But since the product isn't live, it is technically still possible.

[KayL]

Huh? Then how do you know other security products haven't blocked it? I'd say change it if it has bad records. And I'd do some research to see what that Domain used for before.