IP and Domain
Reputation Checker
3

103.213.118.46 has 3 listings

Robot speaking
Robot speaking

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).

1.
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.

103.213.118.46 is listed on the Spamhaus XBL

Why was this IP listed?

A device (computer, server, mobile phone, etc), or an app on a device that is using 103.213.118.46 is infected, badly misconfigured, or compromised. It is making SMTP connections with multiple unrelated HELO values on port 25.

The most recent detection was on: September 21 2023, 10:10:00 UTC (+/- 5 minutes). The observed HELO values were 142.250.152.27, 64.233.187.27, 142.250.153.26, 74.125.200.27, 173.194.79.26.

If all the domains are familiar to you or belong to your customers, check the configuration first. If it is a Plesk host, our FAQ about misconfigured Plesk instances might help.

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

XBL listings expire automatically some time after the last detection. If necessary, once the security issue is solved, you can request removal.

2.
Policy Blocklist (PBL) - This is for information only. No action is required (unless you run your own mail server).

This IP is listed in the Policy Blocklist (PBL)

Don’t panic!

The inclusion of your IP address on the Policy Blocklist (PBL) is standard for the vast majority of internet users and is not the result of your actions. Here are some key PBL facts for your understanding:

  • Being on this list does not mean you won’t be able to send emails.
  • You do not need to request removal from PBL.
  • This listing is controlled by your Internet Service Provider (ISP), not Spamhaus.
  • Your ISP lists ranges of IP addresses that shouldn’t be sending email directly to the internet.
  • Typically, IPs of broadband or dial-up customers will be included in this list.
  • This is part of Internet best practices enacted to protect all users.

Run your own mail server?

If you run your own mail server, and require removal from the PBL, please click on “Show Details” to review your ISP’s policy. Once you have reviewed the policy, please tick the “I am running my own mail server” check-box at the bottom of the page to enable removal.

NOTE: Exclusions are only valid for 1 year. If your IP gets listed on another Spamhaus Blocklist, it will automatically be relisted on the PBL.

103.213.118.0/24 is listed on the Policy Block List (PBL)

Outbound Email policy of The Spamhaus Project for this IP range

This IP address range has been identified by Spamhaus as not meeting our policy for IP addresses permitted to deliver unauthenticated 'direct-to-mx' email to PBL users.

Important: If you are using any normal email software (such as Outlook, Entourage, Thunderbird, Apple Mail, etc.) and you are being blocked by this Spamhaus PBL listing when you try to send email, the reason is simply that you need to turn on "SMTP Authentication" in your email program settings. For help with SMTP Authentication or ways to quickly fix this problem click here.

Removal procedure

If you are not using normal email software but instead are running a mail server and you are the owner of a Static IP address in the range 103.213.118.0/24 and you have a legitimate reason for operating a mail server on this IP, you can automatically remove (suppress) your static IP address from the PBL database.

About The PBL

The Spamhaus Policy Block List (PBL) is an international anti-spam system maintained by The Spamhaus Project in conjunction with Internet Service Providers and is used by Internet networks to enforce inbound email policies. The PBL database lists end-user IP address ranges which should not be delivering unauthenticated email to any mail server except those provided for specifically for that customer's use. The PBL lists only IP addresses (not domains or email addresses).

For full information on how the PBL operates please see the PBL Home page and the PBL Frequently Asked Questions.

Next steps