Sometimes you do not want to wait for the automatic thresholds. Someone is scanning your site, or a client’s ex employee is still hammering an old API credential. Ban IP blocks an address outright.

The ban is applied at application level on the visitor’s IP. Once an IP is on the list, it loses access to the panel, the API and SMPP, and gets an error page instead.

Adding IPs

  1. Open Ban IP and click Add.
  2. The modal shows your own current IP at the top. Read it before you type, because banning yourself is an easy mistake and an annoying one to undo.
  3. Enter the IP, or several at once. Comma separated or one per line both work.
  4. Click Save Changes.

Managing the list

Search by IP and set how many records to show per page. The table gives you ID, the banned IP, and the timestamp it was added, with edit and delete per row. Tick rows to delete in bulk, and use Export to keep a copy.

How this differs from the security dashboard

The Security Events dashboard blocks IPs based on failed login patterns and keeps them in its own Blocked IPs list. Ban IP is the manual list you control. Use Ban IP when you already know the address and have a reason, for example an abusive scanner, a competitor scraping your signup pages, or a client who asked you to cut off an old office IP.

A few habits worth keeping

  • Write down why. The table does not have a reason column, so keep a short note elsewhere with the IP, the date and the reason. In six months nobody remembers.
  • Review the list quarterly. Addresses get reassigned, and a ban from two years ago can block a new customer.
  • Be careful with shared IPs. Banning a mobile carrier NAT address or a corporate gateway blocks far more people than you intend.
  • Check with the client first before banning anything that looks like one of their office ranges.

Related articles