Keep your firewall from banning AttackerView.
Every scan, Warden monitoring check and AI pentest connects from the same two IP addresses. A server firewall such as fail2ban, Imunify360, a WAF, Cloudflare security rules or your host's abuse protection can mistake a security scan for an attack and ban those addresses for hours.
You need this if your site opens fine for you but AttackerView says "We can't reach" your domain, or if results look incomplete. Allowlisting the addresses below fixes it.
2.28.113.111 2a01:4f8:1c1a:405a::1
The first is IPv4, the second IPv6. Allow both: we connect over IPv6 when your domain has an AAAA record.
Go to Security > WAF > Tools > IP Access Rules. Add each address with the action Allow, applied to this website or all websites in the account.
Add the addresses to ignoreip in the [DEFAULT] section of /etc/fail2ban/jail.local, then restart fail2ban:
ignoreip = 127.0.0.1/8 ::1 2.28.113.111 2a01:4f8:1c1a:405a::1
Imunify360: open the Imunify360 plugin, go to White List and add each address. CSF: add each address to /etc/csf/csf.allow (or use Quick Allow in the CSF screen), then restart CSF.
Allow inbound ports 443 and 80 from both addresses in your cloud firewall or security group. If you filter in the web server itself, add an allow rule for them, for example in nginx:
allow 2.28.113.111; allow 2a01:4f8:1c1a:405a::1;
If you cannot change the firewall yourself, ask your host's support to allowlist both addresses so they are never banned or rate limited.
Open the domain in AttackerView and run a scan. Warden monitoring picks it up on its next check and emails you when the domain answers again.