Blocking an unwanted website visitor with cPanel IP Blocker

Use a verified source address from trustworthy logs. A CDN or reverse proxy can change the address seen at the origin, so establish whether real visitor addresses are restored before creating a rule. Keep your own current access available.

1. Open IP Blocker in cPanel and review existing entries before adding another one.
2. Enter the exact unwanted IP address when possible. Use a range or CIDR only when you understand every address it covers; a broad prefix can block many unrelated visitors.
3. Choose Add, then inspect the resulting range in the blocked-address table to verify its boundaries.
4. Test the website from an unaffected network and review fresh requests in the logs. Do not assume a blocked bot will continue using one permanent address.
5. To remove an accidental block, choose its Delete action and confirm Remove IP. Record why the rule was created and when it should be reviewed.

Legitimate users should still reach the site, while matching web requests receive the intended denial. If a proxy is involved, verify the rule acts on the visitor rather than the shared proxy address.

For distributed attacks or login abuse, use appropriate WAF, application and provider controls instead of endlessly adding broad blocks. If you block your own web access, sign in through an authorised management path and remove the rule, or ask support to review the exact entry.

• Password-protecting a website folder with cPanel Directory Privacy
• Diagnosing a legitimate request blocked by ModSecurity in cPanel
• Using Cloudflare Under Attack mode during a web attack
• Preventing unwanted image hotlinking with cPanel

• cPanel documentation