BinaryEdge IP ranges
Current IP ranges (CIDRs) used by the BinaryEdge scanner, updated daily.
| category | Security Scanners |
|---|---|
| website | https://www.binaryedge.io |
| ranges | 38 (38 IPv4, 0 IPv6) |
| last change | |
| downloads | 1,775 |
| download | txt csv json — permalinks, always the latest data |
curl -O https://cloud-ip-ranges.com/download/binaryedge.txt
Ranges
Sample of 25 of 38 ranges. Download the full list above, or check a specific IP.
| CIDR | Type | Tag |
|---|---|---|
| 24.199.120.244/32 | ipv4 | binaryedge |
| 24.199.126.120/32 | ipv4 | binaryedge |
| 24.199.127.63/32 | ipv4 | binaryedge |
| 45.56.83.110/32 | ipv4 | binaryedge |
| 45.56.104.83/32 | ipv4 | binaryedge |
| 45.79.125.187/32 | ipv4 | binaryedge |
| 45.79.149.61/32 | ipv4 | binaryedge |
| 64.227.97.166/32 | ipv4 | binaryedge |
| 66.228.41.25/32 | ipv4 | binaryedge |
| 67.205.189.103/32 | ipv4 | binaryedge |
| 96.126.98.168/32 | ipv4 | binaryedge |
| 134.209.177.224/32 | ipv4 | binaryedge |
| 137.184.70.237/32 | ipv4 | binaryedge |
| 137.184.88.0/32 | ipv4 | binaryedge |
| 137.184.105.192/32 | ipv4 | binaryedge |
| 137.184.186.161/32 | ipv4 | binaryedge |
| 138.68.248.169/32 | ipv4 | binaryedge |
| 138.197.132.119/32 | ipv4 | binaryedge |
| 142.93.55.18/32 | ipv4 | binaryedge |
| 142.93.153.233/32 | ipv4 | binaryedge |
| 143.198.231.199/32 | ipv4 | binaryedge |
| 146.190.244.132/32 | ipv4 | binaryedge |
| 147.182.150.100/32 | ipv4 | binaryedge |
| 157.245.69.67/32 | ipv4 | binaryedge |
| 157.245.86.131/32 | ipv4 | binaryedge |
Blocking BinaryEdge
iptables
curl -sO https://cloud-ip-ranges.com/download/binaryedge.txt
while read ip; do
iptables -A INPUT -s $ip -j DROP
iptables -A OUTPUT -d $ip -j DROP
done < binaryedge.txt
ufw
curl -sO https://cloud-ip-ranges.com/download/binaryedge.txt
while read ip; do
ufw deny from $ip
ufw deny to $ip
done < binaryedge.txt
fail2ban
sudo tee /etc/fail2ban/filter.d/binaryedge-block.conf << EOF
[Definition]
failregex = ^.*$
ignoreregex =
EOF
sudo tee /etc/fail2ban/jail.d/binaryedge-block.conf << EOF
[binaryedge-block]
enabled = true
filter = binaryedge-block
action = iptables-allports[name=binaryedge]
logpath = /tmp/binaryedge.txt
findtime = 1
bantime = -1
maxretry = 1
EOF
curl -so /tmp/binaryedge.txt https://cloud-ip-ranges.com/download/binaryedge.txt
sudo systemctl restart fail2ban
pfSense / OPNsense
curl -sO https://cloud-ip-ranges.com/download/binaryedge.txt
# Firewall > Aliases: new alias BINARYEDGE_BLOCK, type Network(s), import the file
# Firewall > Rules > WAN: Action=Block, Source=BINARYEDGE_BLOCK
About
These are the addresses BinaryEdge scans the internet from, updated regularly. Use them to tag background scanning in your firewall and IDS logs so it does not read as a targeted attack, or to block the scanner outright if you would rather not be indexed. Last update was about 24 hours ago.
Other providers
AirVPN, Akamai, Alibaba, Alpha Strike Labs, Amazonbot, Amzn-SearchBot, Amzn-User, Anthropic, AppleBot, Atlassian, AWS, Azure, Backblaze, Baidu, BingBot, Bunny, CacheFly, CCBot, Censys, ChatGPT-User, ClaudeBot, Cloudflare, Datadog, DigitalOcean, DuckDuckBot, Fastly, Gabia, G-Core, GitHub, Googlebot, Google Cloud, Google Public DNS, Google Services, GPTBot, Hetzner, Hostway, Huawei Cloud, IBM Cloud, iCloud Private Relay, Internet Archive, IVPN, Leaseweb, Linode, Meta, Microsoft 365, Mistral, Mullvad, NHN Cloud, NordVPN, OpenAI ChatGPT, OpenAI SearchBot, Oracle Cloud, OVHcloud, OVPN.com, PerplexityBot, Perplexity-User, Pingdom, Private Internet Access, QUIC.cloud, Rackspace, Rapid7 Sonar, Salesforce, Scaleway, Shodan, StatusCake, StormWall, Stretchoid, Sucuri, Telegram, Tencent, TOR, UpCloud, UptimeRobot, Vultr, Wasabi, Windscribe, Yandex, Zoho, Zoom, Zscaler