Website DDoS Protection and Traffic Filtering

It is a deliberate overload of a website or server with a large volume of traffic or requests. Legitimate users cannot open pages, place orders or sign in.

Attackers often use distributed botnets, so stopping the hit with a single server firewall is hard. You need a separate filtering network with enough capacity.

At L3–L4 the system stops network attacks: SYN flood, UDP flood, ICMP and similar packet floods. They should not use up your server bandwidth.

At L7 the system analyzes HTTP and HTTPS requests. Mass hits on pages and APIs are limited, while regular visitors pass without extra checks and without CAPTCHA.

Hosting keeps your site online for normal traffic. During a strong attack the server channel and resources run out quickly, and pages stop opening for visitors.

Anti-DDoS PRO filtering absorbs the hit on its network and forwards only checked traffic to you. Your site stays on its current host.

Attacks often start without warning. Connecting in advance takes minutes. Recovering after downtime takes hours and lost orders.

Automatic filtering watches the traffic profile all the time and applies rules as soon as abnormal load grows, without waiting for a manual admin response.

There is no CAPTCHA for visitors, so search bots keep indexing the site. Only the A record changes, and the site stays on your hosting.

That lowers the risk of downtime, which is what search engines use to demote pages that stay unavailable.

On the plan you choose, not on the size of the attack. Ready-made plans have a fixed price, from $55 a month. The Individual plan is quoted separately.

A ready-made plan includes legitimate traffic at the 95th percentile: 5, 20 or 50 Mbps. Attacks are not counted in that volume. The Individual plan is requested with the “Discuss” form on this page.

You do not need to move your site. You change your domain's A record to a protected IP address, which we give you after your request.

We send instructions right away. Setup takes about 5 minutes. Your hosting and site files stay yours. How soon the new A record appears depends on the TTL at your registrar: often the same few minutes, sometimes longer.

Plans include your main domain and a set number of subdomains (5, 10 or 20, depending on the plan).

If several subdomains point to the same IP address, only the ones you name when you activate the service, and whose A records you change to the protected IP, will be protected.

Important: When you activate protection, tell us every subdomain you want protected. We add them to our system. The number of protected subdomains is limited by your plan.

No. The service is issued for the main domain named when you connect. It cannot be replaced with another domain, whether once a month or on any other schedule.

A different domain needs its own new service. Subdomains within the plan limit can still be added to the domain that is already connected.

If an attack targets your protected main domain, our system filters out all the malicious traffic. Unprotected subdomains keep working as usual, because the attack traffic never reaches your server.

If an attack targets an unprotected subdomain, and that subdomain is on the same server, the whole server can be affected, including your protected main domain.

Recommendation: Protect every critical subdomain, especially those on the same server as your main domain.

Yes. If you find that an attack is hitting an unprotected subdomain, add it to protection.

You will need to:

1. Tell our technical support which subdomain to add
2. Change that subdomain's A record to the protected IP address
3. Move to a plan with more subdomains, if needed

If attackers hit your server's IP address directly and skip your domain, changing DNS records will not help. That traffic does not pass through our filtering system.

Solution: Change your server's IP address and do not share the new one publicly. All traffic must come only through our protected IP address.

Prevention: Do not use your server's direct IP address in public settings. Always send traffic through DNS that points to the protected IP.

Move up when the bandwidth is no longer enough: 5 Mbps on WebStart, 20 Mbps on WebMiddle, 50 Mbps on WebBusiness. Subdomains, WebSocket, caching, the SLA and support response time increase with it.

Changing plans does not move the site: service limits update, and the list of protected names if needed. If 50 Mbps is still not enough, the Individual plan is requested with the “Discuss” form on this page.