Skip to main content
Starmine, Minecraft server hosting

Protection anti-DDoS

Included with every plan, always on, with nothing to configure on your side. A public Minecraft server always ends up attracting an attack: the question is not whether, but when.

HOSTILE TRAFFIC · REJECTED PLAYERS · ROUTED THROUGH FILTERED UPSTREAM OF THE NETWORK ALWAYS-ON MITIGATION

Filtering happens
before your machine

Incoming traffic first goes through the operator's filtering infrastructure. Hostile packets are discarded at that level; only legitimate traffic is carried to your server. Your machine never sees the attack, so it never suffers it.

  • Permanent mitigation, with no activation and no intervention
  • Included with every plan, with no extra cost and no option
  • Your players stay connected during the attack
  • Public service status, available at any time

How it works

1

Detection at the datacenter

Traffic is analyzed continuously at the edge of the network. An abnormal change in volume or signature automatically triggers scrubbing.

2

Scrubbing the flow

Suspicious traffic is routed to the filtering equipment. Malicious packets are dropped, valid packets continue on their way.

3

Clean delivery

Your server receives only the cleaned traffic. No cut, no pause, nothing to do on your side.

Chart of a denial-of-service attack absorbed by the Starmine filtering

Types of attacks absorbed

Volumetric attacks

UDP flood, DNS or NTP amplification: the volume is absorbed upstream, long before it reaches the capacity of your link.

Protocol attacks

SYN flood, fragmentation, malformed packets: filtered at the network level, without consuming your machine's resources.

Application-level saturation

Mass Minecraft connections, scanning bots: combine the network filtering with the panel's whitelist and bans.

Network protection does not replace good hygiene on the server side: whitelist, anti-bot plugins and strong passwords remain your first line of defense.

A server protected
from the very first minute

Protection is active as soon as the server goes live, with no configuration.