DDoS attack
A deliberate overload of a site or server with traffic or requests, so that ordinary visitors cannot open pages.
An explanation, in Russian as the official wording, of the special terms used on this site.
Edition of 30 October 2026.
The Russian text of this glossary is the official wording. This page is a translation to help you read it.
This document is prepared to meet the Law of the Russian Federation of 7 February 1992 No. 2300-1 “On the protection of consumer rights” (Articles 8 and 10.1), Federal Law of 24 June 2025 No. 168-FZ and Federal Law of 1 June 2005 No. 53-FZ “On the state language of the Russian Federation”, so that a consumer can receive information in the state language of the Russian Federation.
The main text of the site is in Russian. The English version carries the same meaning for clients in other countries. The official wording is the Russian one.
Foreign and special words used on the site are explained below in Russian. Names of payment systems, messengers and the service are kept as the names of those services, with a note of what they are.
A deliberate overload of a site or server with traffic or requests, so that ordinary visitors cannot open pages.
Requests from visitors and search engines. A ready-made plan’s bandwidth includes only this traffic. An attack is not counted in that bandwidth.
Checks of incoming requests on the Anti-DDoS PRO network, before the client’s server. The hosting server receives the requests that pass.
A model that splits network work into layers. On this site L3, L4 and L7 are layers of that model: network, transport and application.
Network layers where packet floods are dropped: SYN flood, UDP flood, ICMP and similar floods. They should not fill the server’s link.
The application layer. HTTP and HTTPS requests are examined here: mass requests to pages and APIs are limited, and ordinary visitors pass without a captcha.
The numeric address of a device on a network. Computers use it to find each other. Anti-DDoS PRO issues the protected IP. The origin IP is the hosting server’s address, which bypasses protection.
A protocol that opens a connection and checks that the data arrived.
A protocol that sends data without that connection check. Ordinary services use it, and so does a UDP flood.
A service protocol. It is used to check whether a host answers, and an ICMP flood uses it to fill a link.
A stream of requests to open a TCP connection that never finish. The aim is to occupy the server before any data is exchanged.
A stream of UDP packets that fills a link.
The protocol a browser uses to request pages.
The same page request over an encrypted channel. It needs an SSL certificate.
A mass of page requests meant to occupy the server. This is an L7 attack.
A program interface: a way for a program to talk to a site or a portal without an ordinary browser page.
0.1 seconds. Filtering rules turn on automatically, without the site administrator.
More than 2 Tbit/s without connection tracking and more than 800 Gbit/s with connection tracking. The main points are Tier IV data centers in Moscow and St. Petersburg.
A data-center grade with a high reserve of power and cooling. The main filtering points are data centers of this grade in Moscow and St. Petersburg.
The hosting address that bypasses protection. If the attack goes there, a DNS change does not help: traffic has to be sent only through the protected IP.
The DNS record that points a domain at an IP address. To turn protection on, it is changed to the protected IP. Site files, mail and the database stay on the current host.
The address issued after a request. The domain and the subdomains that should be protected are pointed at it.
A ready-made plan covers one main domain and a limited number of subdomains: 5 on WebStart, 10 on WebMiddle, 20 on WebBusiness. Protection covers the names named at setup whose A record was changed.
How long the registrar keeps the old DNS record. It decides when the new A record becomes visible. Often that is minutes, sometimes longer. The connection itself takes about 5 minutes.
Where the site files live. Connecting Anti-DDoS PRO does not change the host.
The certificate used for HTTPS. A free certificate is included in WebStart, WebMiddle and WebBusiness.
The domain name system. It turns a site name into an IP address. Protection is turned on by changing the A record in DNS.
DNS included in the ready-made plans together with SSL and L3–L7 filtering.
5 Mbps on WebStart, 20 Mbps on WebMiddle, 50 Mbps on WebBusiness. This is the site’s traffic without attacks. The price on the card does not rise with the size of an attack.
The way a ready-made plan’s bandwidth is counted. Attacks are not included in that volume.
Availability on the plan: 98% on WebStart and WebMiddle, 99% on WebBusiness.
The plan for landing pages and small sites: 5 Mbps, 1 domain and 5 subdomains, a 98% SLA, a support reply within 120 minutes. A rough visit figure is about 50,000 a month. The price is 5,000 rubles or 55 dollars a month.
The plan for stores and company sites: 20 Mbps, 10 subdomains, anti-parsing, WebSocket, caching and a reply within 60 minutes. A rough visit figure is about 200,000 a month. The price is 7,000 rubles or 75 dollars a month.
The plan for large projects: 50 Mbps, 20 subdomains, a 99% SLA, priority support 24/7, load balancing and a reply within 30 minutes. A rough visit figure is about 500,000 a month. The price is 12,000 rubles or 130 dollars a month.
Used when 50 Mbps is not enough. Bandwidth, the number of domains and the reply time are agreed separately, through the Discuss form on the home page.
Filtering rules that turn on automatically when unusual load grows. Included in the ready-made plans. The filter stays on all the time, not only after a support request.
Limits on automatic page collection and password attempts, based on how the request behaves, with no captcha for people. Included in WebMiddle and WebBusiness.
Support for a long-lived connection between the browser and the site. Available on WebMiddle and WebBusiness.
Faster pages by keeping responses. Included in WebMiddle and WebBusiness.
A WebBusiness option. WebStart and WebMiddle do not include it.
An “I am not a robot” check for a visitor. Protected sites do not use one: people and search robots pass without it.
Within 120 minutes on WebStart, 60 minutes on WebMiddle and 30 minutes on WebBusiness.
my.anti-ddos.pro. Services, invoices and tickets are there.
The payment document in the client portal. If a payment fails, the invoice stays: there is no need to place a new order.
A payment system. Mir cards are accepted through it. The card number and security code are entered on its side.
A payment system. SberPay, Mir cards and TPay are available through it.
The bank-card payment system that can pay an invoice through Unitpay or TBank.
Payment via Sberbank Online, on TBank’s side.
Tinkoff Pay, on TBank’s side.
A card number with only some digits visible. That is what the payment system may return to the operator, together with the transaction number, amount and date. The full card number is not passed to the operator.
An electronic mail address. On this site it is a way to get in touch, and the address info@anti-ddos.pro.
A small record the site stores in the browser so it can recognise that browser on the next visit. Records the site and the client portal need in order to work are used for that work. Yandex Metrica loads only after Accept.
The statistics service of Yandex LLC. The counter loads after Accept. Webvisor is part of that statistics: it does not record the characters a person types into request fields.
Names of messaging services. On the Russian site a reply can be requested by email, phone, Telegram or Max. On the English site the choices are email, Telegram, WhatsApp or LINE. The site does not send the request record to those services.
Copyright © 2015–2026 Anti-DDoS PRO. All rights reserved.
We use cookies
By continuing to use the site, you agree to essential cookies. More is in the personal data policy.
Leave a phone number and email. We will contact you to turn protection on.