DDoS-Guard.net main network
Cluster stats
Netblocks31
All fragments 78 blocks across 19 clusters
Cluster ID193383779
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (31)

⬇ 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
103.93.124.0 – 103.93.127.250 DDOS-HK APNIC ALLOCATED NON-PORTABLE ● low

Network trust

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

NIC Handles

AD933-AP AS57724 DCSL1-AP DCSL1-AP MAINT-DDOS-HK