What is a DDoS attack?
A DDoS attack (distributed denial of service) deliberately overloads servers, networks or websites with a flood of requests from many sources at once. As a result, services become slow or unavailable to genuine users. The requests usually come from a botnet of remote-controlled devices.

DDoS: definition and goal
“Distributed denial of service” means a distributed refusal of service. The goal is not data theft but availability: the service is to be overloaded so much that it no longer works for legitimate users. This hits online stores, booking systems, customer portals and interfaces. During the disruption, revenue is lost, and support and reputation suffer.
The attacks come from a botnet: thousands of hijacked PCs, routers, cameras or servers that a perpetrator controls remotely. Because the requests originate from many addresses, the attack cannot simply be stopped by blocking a single IP address. Motives range from extortion through revenge and competition to distracting from other attacks.
Types of DDoS attacks
Attacks target different layers. Volumetric attacks fill the bandwidth with masses of data, often through amplification effects, for example with DNS queries. Protocol attacks such as the SYN flood exhaust the connection tables of firewalls and servers. Application-layer attacks send seemingly normal requests that make the server compute heavily and are hard to tell apart from genuine traffic. Often several methods are used at the same time to overwhelm the defenses.
- Volumetric: the bandwidth is saturated with masses of data
- Protocol: connection tables and network devices are exhausted, for example by SYN floods
- Application layer: seemingly normal HTTP requests overload the database or search
- Multi-vector: several methods are combined at the same time
Real-world example: an online store before the holiday season
A toy retailer receives an email in early December: pay, or the website goes offline. Shortly afterward, the store collapses—in the highest-revenue month of the year. The retailer’s own server with limited bandwidth is no match for the onslaught, and even the hosting provider throttles the connection to protect other customers.
Had the retailer prepared, the store would run behind a provider with DDoS protection that filters out the flood in its network before it reaches the server. An emergency plan with contacts, a status page and customer communication helps in addition. You do not give in to the demand; you file a report.
Protection, limits and implementation
DDoS attacks cannot be prevented completely, but they can be mitigated. Effective measures are an upstream content delivery network or a specialized anti-DDoS service with large capacity, a WAF with rate limiting, scalable infrastructure, caching and a server whose real address is not publicly known. Just as important are monitoring and an emergency plan agreed with the hosting provider.
Nano Concepts plans the protection of shops and web applications against overload, sets up protection and monitoring and, together with you, drafts a procedure for emergencies: who informs whom, what is communicated to customers and when to switch to which protective measure. That way, your company stays able to act even under pressure.
Frequently asked questions about DDoS attack
In a DoS attack, the overload comes from a single source; in a DDoS attack, from very many at once, usually a botnet. The latter is much harder to defend against because the requests cannot simply be blocked via a single address.
Typical signs are suddenly sharply rising traffic from unusual regions or at unusual times, extremely slow or unreachable pages, high server load without matching orders and many requests to the same address. Monitoring and logs help distinguish an attack from a genuine rush.
Deliberately paralyzing other people’s IT systems can be punishable in Germany as computer sabotage under Section 303b of the German Criminal Code (StGB). Victims should document the attack and file a report. Legal advice should assess the classification in the individual case.
Many hosting providers offer basic network-level protection that partly absorbs large attacks. The protection has limits in scale and against application-layer attacks. Ask about capacity, response time and costs during an attack, and supplement it with a specialized provider for critical services.
Matching services

Web Security
Find and fix vulnerabilities – for websites, online stores, customer portals and custom web applications.
Learn more
Databases & Cloud
Data architecture, migration and cloud hosting – high-performing, secure and, on request, in German data centers.
Learn more
Maintenance & Support
Updates, monitoring, backups and further development – so websites, apps and software run reliably.
Learn moreRelated terms
Relevant for these industries
Related magazine articles

Web Security: OWASP Top 10 and a Pragmatic Checklist for Teams
Most security vulnerabilities follow familiar patterns. With the OWASP Top 10 as a guardrail and a prioritized checklist, you close typical gaps before they become a problem.
Read moreGDPR-Compliant Tracking: Consent, Data Flows and Trust
Tracking and data protection aren’t mutually exclusive: which services need consent, how to document data flows and how to implement the technology so it does what your privacy policy promises.
Read more
DevOps and GitOps: CI/CD Pipeline, Quality and Reproducible Releases
Releases without the nerves: how a CI/CD pipeline, infrastructure as code and a rehearsed rollback plan make software delivery reproducible and measurable.
Read more