Network & transport layers
Layer 3 and Layer 4 attacks can exhaust bandwidth or connection resources. For server workloads, confirm the protected IPs, protocols, ports and mitigation limits.
Systron Micronix · Security
DDoS Protection for Websites, Servers & APIs
Reduce the risk of traffic-driven outages. Discuss DDoS mitigation, bot controls and application protection suited to your hosting environment.
Match protection to the service you run
A distributed denial-of-service (DDoS) attack attempts to make a service unavailable by overwhelming its capacity with traffic or requests from multiple sources. Protection needs differ between a public website, a server IP and an application API.
Web applications
Layer 7 attacks target application requests, including HTTP floods. Website protection needs to account for login, search, checkout and other resource-intensive pages.
Coverage that fits
Share your hosting location, normal traffic and business-critical services. Ask Systron to confirm available protection, activation requirements, support scope and pricing for your deployment.
Coverage depends on the selected service and infrastructure. Confirm whether network protection, application-layer mitigation and bot controls are included or require separate configuration.
Bot mitigation & API protection
Control unwanted automation
Distinguish abusive scraping and repeated login attempts from legitimate visitors, search crawlers and integrations. Discuss which traffic should be allowed, challenged or limited, and how to review false positives.
Bot management is a separate requirement from basic network DDoS protection.
Protect application resources
API protection should consider request rates, payload sizes, execution limits and resource usage. Browser challenges may not suit mobile apps or machine-to-machine clients.
Rate limiting complements authentication and authorization; it does not replace them.
Plan your protection with Systron
What to share with our team
- Your website domains, hosting plan and server location.
- Required protocols, ports and application dependencies.
- Normal traffic levels and details of any recent disruption.
- Your availability requirements and preferred support contact.
Send relevant timestamps and sanitized logs through your support ticket. Do not include passwords or private keys.
Assessment & readiness
Discuss a review of exposed services, traffic patterns, origin access and incident escalation. Any proposed resilience testing needs an agreed scope, provider authorization, limits and a maintenance window.
Confirm the deliverables and schedule before commissioning an assessment or test.
FAQsYour DDoS Protection Questions
Is DDoS protection included with my hosting plan?
Check the coverage for your specific plan and location with Systron. Network mitigation, website protection and bot management can have different inclusions and limits.
Does website protection cover every server port?
Do not assume it does. Protection for HTTP and HTTPS websites may have a different scope from protection for other TCP or UDP services. Confirm the protocols and ports your workload needs.
Can I discuss protection for a game server or API?
Yes. Share the application, hosting location, protocols and latency requirements so the team can assess suitable options. Availability must be confirmed for your deployment.
Will protection guarantee uninterrupted availability?
No protection should be treated as a guarantee against every outage. Review the agreed service limits, activation method, exclusions and any applicable service-level agreement.
Will I need to change DNS or server settings?
The setup depends on the selected solution. Ask whether DNS, routing, firewall rules or origin-access settings need changing, and arrange a controlled change window where needed.
What should I do if my service is under attack?
Existing customers should open a support ticket with the affected service, start time, symptoms and any available monitoring data. Ask the team to confirm the current coverage and next steps.