
We try to be as careful as possible to avoid things like opt-in confirmations or messages sent by malware which typically use a genuine message thread and attach malware to these, therefore the domains contained would be genuine.Īll domains are stripped to their “organizational domain” using the Mozilla Public Suffix List. If any short URLs are found, these are extracted and the domains that these URLs point to are also listed. (Read more on our transaction from the terminologies blacklist and whitelist in this blog post) Any bare IPs that are seen in anchor tags are also listed. The domain blocklist uses messages hitting our main trap pools, however, exceptions are made to allow other trap types to contribute where we see patterns in the URLs that indicate Phishing, Compromised websites, Freenom TLDs, newly observed domains, or where the domain is commonly used for abuse (typically free hosting or DDNS services that offer free sub-domains).ĭomains and URLs are extracted from these messages, domains on the white/welcome-list are excluded and all other the remaining domains are then listed. To begin, I’ll need to refer you back to part 1 of our series and specifically to the different trap types we use. This list is built solely by messages hitting our trap infrastructure and is 100% automated. This time we’re looking at our Domain Blocklist. Welcome to part 5 of our series of blog posts dissecting each of the datasets available as part of Abusix Mail Intelligence. Protect your mail servers and user’s inboxesīe safe and don’t take the risk of getting sued Protect your complex network infrastructures Protect sensitive data from cyber attacks Help fight spam by adding your unused domains Report network abuse direct to network owners The industry standard for sharing abuse reports

The free IP/domain lookup and delisting service
#MAC EMAIL BLACKLIST FOR A DOMAIN FULL#
Orchestrate and automate your full security and abuse response Protect your mail servers & customers’ inboxes from spam
