Skip to content

Commit 105aab1

Browse files
authored
Update simulate-ddos-attack.mdx
Related to SPM-2931
1 parent 79d4daf commit 105aab1

File tree

1 file changed

+1
-23
lines changed

1 file changed

+1
-23
lines changed

src/content/docs/ddos-protection/reference/simulate-ddos-attack.mdx

Lines changed: 1 addition & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -17,28 +17,6 @@ You can only launch DDoS attacks against your own Internet properties — your z
1717

1818
## Before you start
1919

20-
You do not have to obtain permission from Cloudflare to launch a DDoS attack simulation against your own Internet properties. However, before launching the simulated attack, you must [open a Support ticket](/support/contacting-cloudflare-support/) and provide the information below. All fields are mandatory.
20+
You do not have to obtain permission from Cloudflare to launch a DDoS attack simulation against your own Internet properties.
2121

2222
It is recommended that you choose the right service and enable the correct features to test against the corresponding DDoS attacks. For example, if you want to test Cloudflare against an HTTP DDoS attack and you are only using Magic Transit, the test is going to fail because you need to onboard your HTTP application to Cloudflare's reverse proxy service to test our HTTP DDoS Protection.
23-
24-
### **For WAF/CDN customers:**
25-
26-
* Attack origin region
27-
* Attack duration
28-
* Attack window (UTC)
29-
* Attack method
30-
* Traffic estimate in both requests per second (rps) and bandwidth (Gbps/Mbps/MBps)
31-
* Target IPs, ports, ranges, zones, hostnames, full URLs
32-
* Contact in case of emergency
33-
34-
### For Magic Transit and Spectrum customers:
35-
36-
* Attack origin region
37-
* Attack duration
38-
* Attack date & timeframe
39-
* Attack method
40-
* Target IPs, ports, ranges, zones, hostnames, full URLs
41-
* Protocol
42-
* Traffic estimate in both requests per second (rps) and bandwidth (Gbps/Mbps/MBps)
43-
* Max packet/bit rate
44-
* Contact in case of emergency

0 commit comments

Comments
 (0)