
Every server on Sigilhosting is protected by our DDoS scrubbing infrastructure at the network edge. Volumetric attacks are detected and filtered inline — no rerouting, no manual activation, no additional cost. Protection is automatic from the moment your server comes online.
All inbound traffic passes through our scrubbing infrastructure before reaching your server. This happens inline — there's no rerouting step and no latency penalty on legitimate traffic during normal operation.
When volumetric attack traffic is detected (SYN floods, UDP amplification, DNS reflection, NTP amplification, memcached reflection), it's filtered at line rate at the network edge. Our scrubbing capacity is distributed across all points of presence, so attack traffic is absorbed close to its source rather than concentrated at your server's data center.
Detection uses a combination of flow analysis, packet inspection, and behavioral heuristics. The system adapts to your server's normal traffic patterns and can distinguish between a legitimate traffic spike and an attack. False positive rates are monitored continuously.

For HTTP and HTTPS workloads, we offer an optional application-layer WAF that sits in front of your load balancer or directly in front of your server. It inspects HTTP requests and filters malicious traffic based on configurable rules.
Rate limiting per IP address, geographic blocking by country code, bot detection using behavioral analysis, and custom rules based on request headers, paths, or query parameters. Rules are configured via API and take effect within seconds.
The WAF logs all blocked requests with full details (source IP, country, matched rule, request summary). Logs are available via API for integration with your SIEM or monitoring system.

What happens when your server is targeted.
When an attack is detected, the scrubbing infrastructure tightens its filtering rules automatically. The severity and type of attack determines which mitigation techniques are applied — a SYN flood triggers SYN cookie enforcement, while a DNS amplification attack triggers source validation and rate limiting on UDP/53.
During and after an attack, full telemetry is available via your dashboard and API: attack type, peak bandwidth, duration, source distribution (by country and ASN), and the mitigation techniques that were applied. Post-attack reports are generated automatically.
No configuration. No additional cost.