Aim of TCP SYN Flood is to exploit TCP three-way handshake process by sending very high volume of SYN flagged TCP packets to the targeted server. Targeted server tries to respond these packets with SYN/ACK packets but gets overwhelmed by huge number of incoming requests and becomes unresponsive.

In TCP SYN-ACK Flood very high volume of SYN/ACK flagged TCP packets are sent to the target. Out-of-state sent SYN/ACK packets violate three-way handshake process. Responding to these requests uses very significant processing power, since these ACK packets do not belong to any of the sessions in targeted server's transmission list. This results in targeted server becoming unresponsive.

In TCP ACK-FIN Flood very high volume of ACK-FIN flagged TCP packets are sent to the target. Out-of-state sent ACK-FIN packets violate TCP connection termination process. Responding to these requests uses very significant processing power, since these ACK-FIN packets do not belong to any of the sessions in targeted server's transmission list. This results in targeted server becoming unresponsive.

High volume of RST packets is sent to a TCP service serving on the target system to prevent the corresponding TCP service from serving.

In TCP RST Flood very high volume of RST flagged TCP packets are sent to the target server. Since these RST packets are not preceeded by a TCP handshake, targeted server goes through all of it's transmission list in order to response to incoming requests. This renders targeted server unresponsive as it requires very signification processing power.

Also known as Xmas Flood, in TCP All Flags Flood very high volume of TCP packets are sent with all TCP flags (SYN-ACK-FIN-RST-PSH-URG) present in it's body. Targeted servers may response to this request differently, as a TCP packet with all flags present in it's body is considered illegal by TCP RFC. Generally, similar to other out-of-state TCP attacks, targeted servers respond to these requests with a RST packet and waste it's resources which results in server becoming unresponsive.

Also known as TCP Null Flood, in TCP No Flags Flood very high volume of TCP packets with no TCP flags. Similar to the TCP All Flags Flood it's considered as illegal by TCP RFC, thus targeted server's may respond to this request differently. Generally, similar to other out-of-state TCP attacks, targeted servers respond to these requests with a RST packet and waste it's resources which results in server becoming unresponsive.

Aim of UDP Flood is to saturate bandwidth and waste resources of the targeted server by sending very high volume of UDP packets. If UDP packets are sent to a port which listens for UDP packets, listening service gets overwhelmed by incoming packets and becomes unavailabile. If no service is listening for UDP packets at the targeted port, server tries to respond it with an ICMP (ping) packet which generates even more traffic resulting in server becoming unresponsive.

Similar to the UDP Flood, UDP Fragmented Flood aims to waste resources of the targeted server by sending very high volume of fragmented UDP packets of the maximum size in order to saturate the channel with as few packets as possible. Sent UDP packets are made of fragments of packets fabricated to waste targeted server's resources, resulting in making server unresponsive.

Aim of ICMP Flood is to disrupt a server's ability to use ICMP(Ping, Echo Request), by saturating it's bandwidth with very high volume of ICMP packets. ICMP protocol is used by various network components to communicate about network connectivity issues and impact of an ICMP Flood is not only limited to denial of the attacked service, but it's effects can be seen by applications that use different/higher layer network protocols.

SSL Negotiaton Flood aims to render a SSL/TLS service unresponsive by establishing too many SSL handshake with targeted server, as a SSL/TLS handshake is a lot more CPU intensive on the server side than on the client side. SSL Negotiaton Flood makes service unable to establish any new SSL connections.

Aim of HTTP(S) GET attack is to simulate very high number of real users requesting the resources of a web application by sending high number of HTTP(S) GET requests to the application. PDFs, Images, etc. large sized files can be targeted to increase the impact of this attack even further. Each request can imitate as if it's send by a real user to make it harder to distinguish from a legitimate request from an actual user. Application gets overwhelmed by incoming requests and unable to respond legitimate requests, becoming unavailable.

Aim of HTTP(S) POST attack is to simulate very high number of real users sending data to the web application by sending high number of HTTP(S) POST requests with customizable payload to the application. Each request can imitate as if it's send by a real user to make it harder to distinguish from a legitimate request from an actual user. Application gets overwhelmed by incoming requests and unable to respond legitimate requests, becoming unavailable.

Unlike many other attack vectors, aim of the Slowloris attack is to fill maximum concurrent connection pool of an application with minimal bandwidth usage by opening many connections to the server and keeping them open as long as possible. When targeted application's connection pool is full, targeted application denies new additional connection attemps from actual clients, and targeted application becomes unavailable.

In DNS Query Flood, very high number of DNS queries are sent to a DNS Server in order to saturate the bandwidth and waste resources of the DNS server. Preventing it from responding to actual DNS queries coming from real users.

Similar to the DNS Query Flood, very hig number of DNS queries are sent to a DNS server in order to saturate the bandwidth and waste resources of the DNS server. Unlike DNS Query Flood, sent queries are random and requires additional processing by the DNS server, preventing the server from responding to actual DNS queries coming from real users.