DDoS-Guard.net main network

BGP inherited
Cluster stats
Netblocks30
Registered in Russia (9) · AG (7) · KZ (1)
Cluster ID208802525
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
30 -1 netblocks since 2026-07-05
2026-07-05 peak 31 2026-07-19

IP Ranges (30)

⬇ export CSV
CIDR Org name Registry Status Confidence
91.240.225.178/32 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
109.239.136.200/32 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
109.239.137.21/32 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
109.239.137.194/32 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
178.18.224.217/32 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
178.18.224.246/32 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
178.18.226.76/32 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
178.18.227.57/32 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
185.0.13.173/32 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
185.1.153.130/32 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
185.232.60.199/32 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
193.27.37.102/32 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
193.27.38.3/32 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
193.232.140.52/32 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
194.226.100.215/32 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
194.226.102.215/32 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
195.2.230.253/32 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
195.208.210.96/32 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
2001:7f8:20:101::210:96/128 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
2001:7f8:20:201::100:215/128 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
2001:7f8:20:202::102:215/128 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
2001:7f8:20:501::140:52/128 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
2001:7f8:eb::e17c:1/128 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
2001:b28:3ff::137:21/128 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
2001:b28:3ff::e17c:0:1/128 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
2a03:5f80:4::224:217/128 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
2a03:5f80:4::224:246/128 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
2a03:5f80:4::226:76/128 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
2a03:5f80:4::227:57/128 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high
2a0d:e180::60:199/128 DDoS-Guard.net main network PEERINGDB ASSIGNED ● high

Network trust

what's this?
RPKI hygiene: C how networks compare →
56.7% of checked blocks have valid RPKI ROA coverage (17 of 30)
No discrepancies found among checked blocks.

NIC Handles

AS57724