DDoS protection
built for Minecraft.

DDoS protection built for Minecraft. A filtering shield forwards only real Minecraft clients to your server, both Java and Bedrock, while bots, scans, and floods are dropped at the edge. No mitigation mode to activate, ever.

Point your domain at us. Your players keep the same address.

A proxy that speaks
Minecraft.

The shield validates every connection at the protocol level. It knows what a real Minecraft client looks like on the wire, so protection doesn't depend on recognizing an attack first. It depends on recognizing your players, which happens on every legitimate connection.

Fake clients are dropped at the edge

Bot floods and fake-client attacks are filtered out before they ever reach your backend. Your players never notice.

Bot pings never reach you

Server-list pings are answered by the shield itself. Probing bots get a response without your server ever seeing the connection.

Protection that never turns off

There is no attack mode to activate. The shield filters traffic around the clock, attack or not.

Geyser and Bedrock,
first-class.

Bedrock protection uses NetherNet, the modern way Bedrock Edition connects. We relay the signaling and carry the game traffic, and Geyser receives real player IPs so bans and logs work exactly like Java.

One domain for both editions

Bedrock players join with the same domain your Java players use, on the standard Bedrock port. No separate address to publish.

Signaling relayed, traffic carried

We relay Geyser NetherNet signaling and carry the game traffic, so Bedrock works with no plugins and no client changes.

Real player IPs for Bedrock too

Player addresses reach Geyser so Bedrock bans and logging work exactly like Java.

A dashboard with
live telemetry.

The same proxy that protects your server records what happens on it: players online, joins, sessions, and bandwidth, updated live.

Players online right now

Live player counts for every network, updated continuously by the shield itself.

Joins and sessions

See who joined, how long they stayed, and how active your server has been over the last hour, day, week, or month.

Bandwidth per network

Inbound and outbound traffic per network, counted the same way your plan allowance is.

Three steps to
protected.

Setup is self-serve and takes minutes. Your players keep the same domain, and nothing is installed on your server.

  1. Create a network

    Sign in and add a network: name it, choose an edge region, and add your backend address.

  2. Point your domain

    Add a CNAME (or SRV) record pointing your domain at the protected hostname shown in your dashboard.

  3. Lock down the backend

    Firewall your server to accept traffic only from our published IP list, and enable proxy protocol so real player IPs arrive.

Two regions.
Built like fortresses.

We would rather run two big, heavily provisioned locations than scatter capacity across dozens of small ones. Our Ashburn and Amsterdam sites sit in the most popular hosting destinations, with generous headroom for attack traffic, so your server stays online even when an attack would flatten a smaller edge. Traffic leaves the network at the region closest to your hosting, with one setting per network.

Ashburn, VA (US East)

Next to the largest concentration of game hosting on the East Coast. The right pick for servers hosted in the Americas.

Amsterdam (EU West)

Europe's connectivity hub. The right pick for servers hosted in Europe, the Middle East, and Africa.

Protect your server
in minutes.

Plans start at $25 a month with a 7-day free trial on Essential. Free forever for Pufferfish Host customers, with unlimited networks, domains, and backends.

Create your first network today.