On 3/1/2019 1:07 PM, RW wrote:
Sure, but had it turned-out that most of these domains didn't have the A record necessary for your HTTP test, it wouldn't have been worth doing anything more complicated.
I've noticed a lot of the spam domains appear to point to actual web servers but throw 403 or 503 errors, which A records wouldn't help with and has been taken into account here. As for being "more complicated" - it's basically done and running in my test environment for final tweaking haha, so bit late now :P It was only a day's work to put everything together including the DNS service and caching layer, so meh. Unless you mean complicated in the sense that it's more technically complicated as opposed to effort wise.
You don't need an A record for email. The last time I looked it just tests that there's enough DNS for a bounce to be received, so an A or MX for the sender domain.
I'm confusing different tests here, you can disregard my previous message.
