Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
DDoS protection means being ready for the day when a flood of requests from many machines around the world makes your site or email unusable, so that it is less likely to happen and quicker to recover from. It concerns companies that depend on the web for bookings, orders or inquiries, and the agencies that look after those sites. Three jobs come first: put a CDN (a network of relay servers that carry part of your traffic) in front of the site, learn what your normal traffic looks like, and settle whom to call and how to announce an outage.
This page is a hub for owners and managers. DDoS aims to stop a service, not to steal information, so its priorities differ from the other hubs. For break-ins, see hacking prevention. If your site is down now, read the emergency guide first.
What does a DDoS attack do?
Imagine your shop's phone number is spread around town, and thousands of strangers ring at once and say nothing. Real customers hear only a busy tone. A DDoS attack (distributed denial of service) does the same thing on the internet.
The National Police Agency describes it as an attack that repeatedly sends a large volume of access from many computers to one target so that the service cannot be provided. The senders are a network of machines the attacker has taken over, a botnet. IPA mentions botnets built from IoT devices. NISC gives routers and IP cameras as examples of machines that get drawn in.
The goal is to stop a service, not to take data. While it is down, sales, bookings, inquiries and internal email stop. IPA lists two aims of attackers: showing off a cause, and demanding money in return for stopping.
There is a second position that is easy to miss. Your own equipment can be taken over and used to attack someone else. NISC lists measures against becoming such a stepping stone next to the measures that limit damage to you.
What types of attack are there, and where do you act?
The word DDoS covers attacks aimed at different places. If you know where the bottleneck forms, you can see where to absorb the load. The table rearranges the main types in IPA's guide and NISC's advisory from a site owner's point of view.
| Type of attack | What happens | Where to act | Read more |
|---|---|---|---|
| Flooding the line (flood attack) | A huge volume of traffic clogs the line or the server's processing, and the site will not open | In front of your line: a CDN, or DDoS protection from the network or cloud provider | This page |
| Reflection attack | The sender address is faked and many servers are asked questions, so their replies pile onto the target | Settings that stop your own DNS server from being used as a stepping stone | DNS misconfiguration |
| Mass requests for web pages (HTTP flood) | Machines keep opening pages and the site cannot keep up | A WAF (blocks harmful traffic at the door), rate limiting, caching | Missing rate limiting |
| Attack on DNS (queries for random subdomains) | Your DNS server is overloaded and the site's name cannot be looked up | Redundant DNS, the DNS provider's protections | DNS misconfiguration |
| Mass login attempts | Attempts pile up on the login screen and the server slows | Limits on login attempts and on where logins can come from | Preventing unauthorized access |
| Hitting the origin server directly | Traffic skips the CDN and lands on the server behind it | Hide the origin server's IP address and block anything that does not come through the CDN | This page |
IPA writes that services which carry out DDoS attacks for a fee are offered on dedicated sites and social media. We do not publish attack steps, because all a defender needs to know is where the bottleneck forms and where to absorb the load.
What do public statistics show?
The figures below come from the original publications, which we opened ourselves.
National Police Agency: real-life impact, and attackers who change methods mid-way
In its Reiwa 7 situation report (published March 2026), the National Police Agency says that damage believed to come from DDoS attacks hit one organization after another from late December 2024 to early January 2025. The targets were operators of critical infrastructure, such as transport and financial institutions. Automatic baggage check-in machines at an airport became unusable, and logging in to internet banking became difficult. People's daily lives were affected.
Police confirmed several methods. In some cases, the attackers changed methods as conditions changed and kept going even after operators blocked traffic. In several cases, attackers specified IP addresses and hit the origin server, which holds the original web data, directly. That bypasses the load spreading a CDN provides.
In March and April 2025, the personal site of a senior government figure became hard to view. In June, several sites run by government bodies, local governments and private firms had viewing failures. Around then, accounts on social media that appeared to belong to hacktivists, who attack to make a political point, posted hints about the attacks.
The same document gives another view. In a survey the Agency ran among randomly selected private companies and public bodies, DDoS among the attacks received in the past year had halved compared with ten years earlier. A lower count does not make an attack any less damaging when it comes.
IPA: ninth among threats to organizations, selected for the seventh time
In IPA's Top 10 Information Security Threats 2026 (29 January 2026), "DDoS attacks" is ninth for organizations. It first appeared in the 2016 edition, and 2026 is its seventh selection (second year in a row). IPA states that a rank does not measure the degree of danger itself.
The explanatory guide describes two cases. In the first, in late June 2025, a research institute lost email reception and access to its homepage, and had trouble again in July. The cause was a DDoS attack, and IPA writes that no leak of information was confirmed. Network recovery was completed on 31 July.
In the second, KAGOYA JAPAN, a rental server operator, saw a large number of login attempts from multiple IP addresses against its webmail from about 16:30 on 30 July 2025. Mail and the control panel became hard to reach. At about 17:45 the company blocked traffic from some regions that the attacks came from, and it confirmed that logins worked normally afterwards (IPA, explanatory booklet for the Top 10 Information Security Threats 2026, organization edition).
NISC: three bundles of measures, limit, anticipate and do not take part
NISC issued its advisory on DDoS countermeasures on 4 February 2025. It explains that attacks on airlines, financial institutions and telecom operators followed one another around the year-end, using several types, including UDP flood and HTTP flood attacks run through IoT botnets.
The advisory divides measures into three bundles. The first limits damage: blocking traffic from IP addresses allocated abroad, dedicated devices or services such as a WAF, using a CDN, and redundancy. The second anticipates damage: ranking systems by priority, monitoring normal traffic, alerts, an apology page, and a contact list with a procedure sheet. The third keeps you from becoming a stepping stone.
NISC states in the same document that some DDoS measures need a lot of money and time, and that not every attack can be stopped in advance. It asks you to begin with close-at-hand work: reviewing settings, checking vulnerabilities and updating software.
Curious about your own site after reading this? The free URL check looks at public information only and costs JPY 0.
What should you do first, by company size?
DDoS protection ranges from costly items such as a CDN and dedicated services to work that is only a settings review. Match the order to your company.
A company of a few people up to about 20, with the site managed by a web agency
Begin by finding out what DDoS protection your server company has. Even if you cannot own defensive equipment, the provider's blocking features can sometimes limit the damage.
Then ask your agency: "Is a CDN in place?" and "Whom do we call when the site is down?" If no answer comes, nobody may know how to react to an outage. Decide in calm times where you will post notices for customers, such as social media or a separate notice page.
A company of a few dozen, whose bookings or orders run through the site
Here an outage hits revenue directly. Consider first a setup that combines a CDN and a WAF and keeps the origin server's IP address out of public view.
Also record normal traffic, and make an alert reach a person when it jumps. As NISC suggests, decide in advance which services you must protect and which could tolerate a stop of some length.
A company that runs its own servers, DNS or VPN devices
At this size you are both a defender and a possible stepping stone. Check that you do not run a DNS server that answers outsiders' questions without limit (an open resolver), and that you do not send out packets with forged sender addresses. Updating routers and IoT devices is part of this check.
Then find out whether you have a DDoS contract with your network provider, and write down who calls them and how. That written procedure is what makes a contract usable.
10 things to do today
These 10 steps follow the NISC advisory and our fix menu, arranged so that a site owner can start easily. Where an item matches a fix-menu number, it is noted.
- Learn your normal traffic. Use analytics or the server's graphs to see typical levels on weekdays and weekends. Without a baseline you cannot spot an anomaly.
- Ask your server company and network provider what DDoS protection they offer. Check the contract or the control panel for their blocking features, and make sure you can use them.
- Put a CDN in front and hide the origin server's IP address. This makes the bypass that the police confirmed harder. Review your DNS settings as well, so the address is less likely to be known outside.
- Set up a WAF. It drops harmful traffic before it reaches the site (fix menu number 9). NISC lists a WAF among its measures to limit damage.
- Apply rate limiting. Use a threshold to stop bursts of requests from one source (rate limiting).
- Limit login attempts and stop entrances you do not use. These are fix-menu numbers 5 and 7, and they make it easier to stop mass login attempts from becoming load.
- Keep the core, themes and plugins current and remove what you do not use. This is fix-menu number 1, and it shrinks the openings through which your site could be taken over as a stepping stone.
- Prepare a place for outage notices. Put an apology page somewhere separate, and be ready to post on social media too.
- Make a contact list and a one-page procedure. Record the server company, network provider, web agency and police contacts, and decide who does what.
- Update routers, cameras and other IoT devices in the office. Change default passwords and do not keep using devices that are out of support. That makes it harder for your own equipment to join an attack.
Start with items 1, 2 and 9. Items 3 and 4 can make the site unreachable if set wrongly, so take a backup first. Finishing all 10 does not mean you cannot go down. It cuts the odds and the length of an outage.
Not enough hands in-house? Tell us your situation and we will check with you which of the 10 are still open.
What should you hand to a specialist?
DDoS is hard to handle within one company. Absorbing a huge volume of traffic is the job of CDN, cloud and network providers' equipment.
First, to avoid any misunderstanding: our price list contains no line service that absorbs DDoS traffic itself. CDN and DDoS service fees depend on the provider you contract. We take care of checking settings, finding holes and ongoing watch.
We recommend a specialist for these:
- Checking CDN, WAF and rate-limit settings. Whether the origin server's IP address leaks, and whether an entrance that skips the CDN remains, has to be checked from outside. A server and network assessment is from JPY 49,800 (excl. tax, up to 5 IPs).
- Assessment of login screens and inquiry forms. We confirm that limits work on the screens most prone to heavy load. A web application assessment Lite is from JPY 98,000 (excl. tax, up to 10 screens). The number of screens and the screens behind login affect the price.
- Continuous watch. Updates, backups, tamper monitoring and first response to faults can sit in a maintenance plan. Maintenance Lite is JPY 9,800 per month (excl. tax), and Guard Lite, our AI monitoring for WordPress, is JPY 5,000 per month (excl. tax).
- Answers to partners and internal rules. For the question "What do you do about DDoS?", the security advisory plan at JPY 29,800 per month (excl. tax) can help you prepare an answer.
- Handling an attack in progress. Contacting providers, announcing the outage and consulting the police all at once is a heavy load for one company. Start from the emergency guide.
What an assessment returns is the issues found and how to fix them. Before delivery you receive a PDF of what we changed, and you check the real screens. After delivery, the first month of support is free. An assessment checks whether the weak points known now are absent, and it does not promise resistance to future attacks.
Which pages cover the individual holes?
Among our categories, one vulnerability page links directly to this hub, on missing rate limiting. The others share entrances or settings with DDoS.
Linked directly to DDoS
- Missing rate limiting (no limit on large numbers of requests in a short time)
Sharing entrances or settings
Related hubs: hacking prevention, unauthorized access and ransomware. A DDoS with a demand for money has the same shape as a ransomware threat, so reading both gives a fuller picture.
How can the free URL check help you decide?
Decide what to fix after you know your starting position. Type your site's address into the free URL check. It works from public information alone: the submitted page, public DNS and the TLS handshake. Certificate expiry, security headers, software versions shown on the page, and SPF and DMARC records are covered, and the JavaScript libraries the page loads are matched against known vulnerabilities. Screens behind login and the server's interior stay out of view.
It does not send a large volume of requests to test whether your site holds up. Not running anything that amounts to an attack is the basis of the check. How well you stand up to load is something we discuss separately, after we have your consent and have checked the environment.
A worrying result can lead to the free assessment, after an NDA and your signed consent form: tools plus a person run a quick check, and you receive an issue report. A formal quotation follows that report.
Frequently asked questions
Can a small company's website be hit by a DDoS attack?
Yes. It is not only a large-company problem. IPA's guide describes July 2025, when the webmail and control panel of a rental server operator became hard to use for a while. If the server company you rely on is targeted, firms that use the same service can feel it too.
What should we do first while a DDoS attack is under way?
First contact your server company or network provider and ask whether they can block or limit the traffic. At the same time, tell your customers what is happening on your site and social media, and consult the police. If a message demands money, consult the police before paying anything.
Will a CDN stop DDoS attacks?
It can reduce the damage a great deal, but it cannot be called a guarantee. The National Police Agency has confirmed attacks that bypass the CDN and hit the server behind it directly. Hide the real server's IP address and block traffic that does not come through the CDN.
How much does DDoS protection cost?
The free URL check, which looks only at what is visible from outside, costs JPY 0. A server and network assessment is from JPY 49,800 (excl. tax, up to 5 IPs), and the amount depends on the number of IP addresses. CDN and network-provider DDoS services are priced by their own contracts and are not in our price list.
Next step
Do two things today: start on items 1, 2 and 9 of the list, and run your site through the free URL check.
To settle priorities or decide what to outsource, write to us. If your site is already down, begin with the emergency guide.
Written by Mio Kanzaki (AI security analyst). Supervised by 千葉圭介. Updated 19 November 2026.
Frequently asked questions
Can a small company's website be hit by a DDoS attack?
Yes. It is not only a large-company problem. IPA's guide describes July 2025, when the webmail and control panel of a rental server operator became hard to use for a while. If the server company you rely on is targeted, firms that use the same service can feel it too.
What should we do first while a DDoS attack is under way?
First contact your server company or network provider and ask whether they can block or limit the traffic. At the same time, tell your customers what is happening on your site and social media, and consult the police. If a message demands money, consult the police before paying anything.
Will a CDN stop DDoS attacks?
It can reduce the damage a great deal, but it cannot be called a guarantee. The National Police Agency has confirmed attacks that bypass the CDN and hit the server behind it directly. Hide the real server's IP address and block traffic that does not come through the CDN.
How much does DDoS protection cost?
The free URL check, which looks only at what is visible from outside, costs JPY 0. A server and network assessment is from JPY 49,800 (excl. tax, up to 5 IPs), and the amount depends on the number of IP addresses. CDN and network-provider DDoS services are priced by their own contracts and are not in our price list.