Listings - Reputation Checker

Please don’t be alarmed! We understand finding your IP address or domain on a blocklist can be worrying. This website will give you information about why you are listed, and what you can do to ensure you don’t get listed again.

Where it is possible to request removal, we will help you through the process. However, if your IP is listed on the Spamhaus Blocklist (SBL), removal can only be requested by your Internet Service Provider (ISP).

eXploits Blocklist (XBL) & CSS Blocklist (CSS) - Why is this IP address listed?

The machine using this IP is infected with malware that is emitting spam, or is sharing a connection with an infected device.

As a result, this IP is listed in the eXploits Blocklist (XBL) and the CSS Blocklist (CSS)

Click on Show Details to see if you can request a delisting from this blocklist. This will also display any further information we have relating to this listing.

Show Details

Why was this IP listed?

A device using 2a01:7e01::/64 is infected with malware and is emitting spam.

2a01:7e01::/64 is making SMTP connections with HELO values that indicate a problem, usually a spambot but can also be caused by a misconfiguration.

Technical information

The most recent connections we have seen:

(IP, UTC timestamp, HELO value)

2a01:7e01:: 2022-11-29 14:20:00 server.example.com

Notable things about the HELOs:

They are often dynamic-looking rDNS, and claim to be from geographically very different networks
They can include impossible HELOs like "gmail.com", "outlook.com", "comcast.net" - Gmail, Outlook and Comcast do not use these. These are all fake.
The cause of this problem is frequently found to be coming from an phone or laptop with "free" VPN or channel unlocker, "free" streaming apps.

If this is a misconfiguration of a HELO setting or a Plesk host, that should be corrected.

HELO/EHLO & DNS CHECKS:

You can test a server's HELO configuration by sending an email from it to helocheck@abuseat.org. A bounce that contains the required information will be returned immediately. It will look like an error, but it is not. Examine the contents of this email.

If the HELO/EHLO value does NOT exist in DNS, that should be corrected
If the HELO/EHLO value is NOT correct, that should be fixed
If the HELO/EHLO is using a domain that does NOT exist, that should be corrected
If the IP does not have valid and reasonable rDNS, that should be corrected.

NOTE: This check does not currently work on IPv6. This is only a syntax check, NOT a verification that the problem has been resolved. Does the HELO match expectations? Does it have DNS?

If the HELO settings are correct, then there is a spambot or some other kind of malware!

What should be done about it?

If this is a shared server, please call your hosting company or ISP!

These listings are the result of what we believe to be a security issue that results in spam being sent from your network. To stop ongoing listings and to secure your network, devices, and data, we recommend both prevention and remediation of the issue.

We hope the following information might be of help.

Prevention

We very strongly advise securing your router/firewall to deny any outbound packets on port 25, except those coming from any email servers (if any) on your local network. Remote sending of email to servers on the Internet will still work if web-based, or configured properly using port 587 with SMTP-AUTH.

If you are not running your own mail server, you should be using your ISP's mail servers with SMTP authentication, and your router should be set to deny outbound traffic on port 25. Your ISP can help you set that up if needed.
If you are using your ISP's mail servers and they are blocking you from those servers, please call them for a resolution. Your router should also be set to deny outbound traffic on port 25. Your ISP can help with that.
If you are running your own mail server, please contact your ISP for help with getting set up on an appropriate static IP and valid DNS/rDNS for that purpose, to configure SMTP authentication on port 587, and then to limit outbound port 25 only to the use of that server.

Limiting port 25 access is a best practice. Please call your ISP or IT department for assistance with configuring your router or firewall correctly.

Remediation

The device(s) or computer(s) that caused this issue should be found and secured. The following information should address most cases, but please seek professional assistance if it is necessary:

The cause of this problem is frequently found to be coming from an phone or laptop with "free" VPNs, channel unlockers, streaming type apps installed.
Programs like Windows Defender, Windows Malicious Software Removal Tool (MSRT), Malwarebytes, Norton Power Eraser, CCleaner and/or McAfee Stinger can help. There is also a version of Malwarebytes for Mac/OSX. These tools are free of charge!
Update your enterprise anti-virus/anti-malware programs, and run full scans on every device that is available
If you have a CMS or website, ensure it is up to date. All plug-ins, extensions & patches for it should be updated and maintained
We can only see what's coming from the NAT (public) IP; anything inside your network is visible only to you. Packet capture is the best way to identify which devices are generating unwanted traffic. In general, only mailservers are supposed to generate traffic to port 25, as mail clients rely on the dedicated ports 587 or 465.
If this IP address is a NAT gateway, firewall or router: in some cases, the compromised device can also be the router/firewall itself. Please consult the documentation of your device regarding how to make sure its software is up to date, and how to ensure that the device is properly secured.

Spamhaus has a "hacked or compromised devices" FAQ with tips and links to help in this situation.

XBL listings expire automatically after the last detection. If necessary, once the security issue is solved, you can update an existing ticket to request removal.

Removal from XBL

Once the security issue on 2a01:7e01::/64 has been resolved, you can request removal: