It can be quickly ruled out by following the steps below. Learn what to do if you can’t access your website, hPanel, or WordPress admin because your IP address has been blocked by Hostinger’s firewall.<\/p>
Why can an IP be blocked?<\/h2>
Hostinger uses an automated firewall and third-party security tools to protect our servers from malicious traffic. If your IP address is associated with suspicious activity — such as repeated failed login attempts, high request volume, or previous reports from other websites — it may be automatically flagged and blocked.<\/p>
This can happen even if you are a legitimate user. Common reasons include:<\/p>
- \n
- Your device or network was previously affected by malware<\/strong> that sent suspicious requests.<\/li>\n
- You share a network (office, school, or public wifi) with someone whose activity triggered the block<\/strong>.<\/li>\n
- A plugin or tool on your website sent an unusually high number of requests to the server.
\nYour IP has a history of abuse<\/strong> reported through third-party databases like AbuseIPDB, Greynoise, or Bitninja.<\/li>\n<\/ul>Troubleshooting a blocked IP<\/h2>
Step 1 – Confirm your current IP address<\/h3>
Before contacting support, confirm what your actual IP address is. Your IP can change, especially on mobile or home connections, so do not rely on a previously noted address.<\/p>
Visit What is My IP<\/a> while connected to the same network you use to access your website or hPanel.<\/p>
Step 2 – Check your IP reputation<\/h3>
You can check whether your IP has been flagged in security databases. This will help you understand the severity of the block and what options are available to you.
\nWe recommend checking the following tools:<\/p>- \n
- AbuseIPDB<\/a>: shows reports submitted by websites and services across the internet.<\/li>\n
- Greynoise<\/a>: shows whether your IP has been identified as a scanner or bot source.<\/li>\n
- MXToolbox Blacklist Check<\/a>: useful if you are also having email delivery issues.<\/li>\n<\/ul>
Once you have your abuse confidence score from AbuseIPDB, use the following guide:<\/p>
- \n
- 0–15%: Low risk. Start a chat with Kodee, our virtual assistant, and it can process the unblock automatically.<\/li>\n
- 16% and above: Our team is unable to unblock this IP. We recommend submitting a delisting request (Step 4), contacting your ISP for a new IP address (Step 5), or using a VPN as a temporary workaround to access your website or hPanel.
\n![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/04\/ip-confidence-score.png\")
<\/li>\n<\/ul>Step 3 – Request an unblock<\/h3>
If your score is 0–15%, start a chat with Kodee, our virtual assistant. Kodee can process the unblock automatically without needing to escalate to our support team.<\/p>
- \n
- Your current IP address (from whatismyip.com)<\/li>\n
- The domain or website you are trying to access<\/li>\n
- The error message you are seeing (for example: ERR_CONNECTION_TIMED_OUT or ERR_CONNECTION_REFUSED)<\/li>\n<\/ul>
Our team will review your case against the firewall and security tools. Please note that there is a chance the block may not be removed depending on our findings.<\/p>
NOTE<\/strong><\/p>
- \n
- If the same activity that triggered the block continues — for example, repeated failed login attempts — your IP may be automatically blocked again.<\/li>\n<\/ul>
Step 4 – Submit a delisting request<\/h3>
If your IP has a high abuse score but you believe the reports are inaccurate or outdated, you can dispute them directly with AbuseIPDB.<\/p>
- If the same activity that triggered the block continues — for example, repeated failed login attempts — your IP may be automatically blocked again.<\/li>\n<\/ul>
- Greynoise<\/a>: shows whether your IP has been identified as a scanner or bot source.<\/li>\n
- You share a network (office, school, or public wifi) with someone whose activity triggered the block<\/strong>.<\/li>\n
![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/04\/abuse-ipdb-contest.png\")
<\/li>\n<\/ol>