Voting sites and NuVotifier

Vote-listing sites (TopMinecraft, MinecraftServers, …) deliver player votes to your server through Votifier or NuVotifier. By default, that means giving the voting site your backend IP — which then sits in their database forever.

The Infinity-Filter Votifier module proxies vote traffic so vote sites only learn a hostname pointing at the edge.

Quick setup

1. Install (Nu)Votifier on your backend (typically on the Velocity proxy).
2. In Network → Backends, add a Votifier module backend. Set its address to your backend ip:port (default 8192).
3. The panel shows a “How to install” hostname — give this hostname to the voting sites instead of your backend IP.
4. On each vote site, set the Votifier IP to the IF hostname and keep your public key unchanged.

See Votifier / NuVotifier integration for the full walkthrough.

Why the public key doesn’t need to change

(Nu)Votifier encrypts the vote payload with the public key the voting site holds. Only your backend can decrypt it (with the private key). Infinity-Filter just forwards the encrypted blob — it never sees the plaintext vote, so changing the IF endpoint doesn’t require rotating the key.

Recommended setup for multiple vote sites

You can register the same IF Votifier hostname on every vote site. There’s no per-site secret; the public key is shared the same way.

Vote delivery during attacks

Vote traffic is low-volume and goes through the same edge as Minecraft. During a sustained attack:

• Votes are not deprioritized vs. player traffic — both pass through mitigation.
• If a specific vote site’s source IP is caught by Anti-VPN or Country filtering, votes from that site fail. Whitelist the IP if needed.

Multiple networks

Each network has its own Votifier module backend. If you run separate networks for separate brands, each can have its own Votifier integration with its own keys.

What’s next