Does the tester work with the original Votifier plugin?

Yes. The original Votifier plugin used the same RSA-over-TCP v1 flow. If you still run legacy Votifier and the same public key/port, a successful send here means the socket and crypto path are reachable. Most servers today use NuVotifier or another maintained fork instead.

What about VotifierPlus, standalone Votifier, or other forks?

Any implementation that exposes the classic V1 listener (VOTIFIER line + fixed-size RSA ciphertext) can be tested the same way. Fork names vary; what matters is that the process bound to your host:port speaks that protocol and uses the pasted RSA public key.

Which vote reward plugins does this help with?

This page only proves the vote packet reached your Votifier-compatible listener. In-game rewards are handled by separate plugins that subscribe to vote events—commonly VotingPlugin, SuperbVote, VoteParty, Listener for NuVotifier, or custom scripts. If the tester succeeds but players get no rewards, check those plugins’ configs, permission queues, and whether offline vote processing is enabled.

What port and key should I use?

Default Votifier TCP port is often 8192. For v1, paste the RSA public key (PEM). For v2, paste the token from NuVotifier config—not the RSA key. The host is the address listings use (server IP or DNS), reachable from the public internet.

Why does the test say success but I see no reward?

Success means the TCP listener accepted the encrypted payload. Rewards still require a listener plugin to fire commands or economy updates. Check console logs, enable debug in your vote plugin, confirm the test username (Minelist / TestUser) is not blocked, and verify you are not on a duplicate or stale key from a copied world.

Proxy networks (BungeeCord, Velocity): what IP do I test?

Test the host and port where the Votifier socket actually listens—often the backend Spigot/Paper server’s IP from the vote site’s perspective, or a dedicated forwarded port on the proxy if you configured NuVotifier there. Mismatched bind addresses (only 127.0.0.1) or closed firewall rules are common reasons for failure.

Will this test vote affect public vote counts?

No. The packet is generated only by you from this page; it is not sent through Minelist’s real voting pipeline. It is a synthetic “Minelist / TestUser” style payload for connectivity testing only.

Does a player need to be online for this test vote?

No. The test uses a placeholder username and only checks that your listener accepts the RSA packet. Reward plugins may still require online players for some commands—check each plugin’s offline vote and queue settings.

Free Minecraft Votifier Tester (NuVotifier v1 RSA + v2 Token)

Q: Which Votifier protocols does Minelist support?

Minelist supports Votifier protocol v1 (RSA public key over TCP) and v2 (NuVotifier token with HMAC challenge handshake). Auto mode tries v2 first, then v1—the same flow this tester uses. Compatible listeners include NuVotifier, legacy Votifier, VotifierPlus, and forks that expose v1 and/or v2 on your vote port. Pure HTTP(S) webhook-only receivers without a Votifier TCP socket are not supported.

Q: Does this Votifier tester work with NuVotifier?

Yes. Select Auto or v2 and paste your NuVotifier token, or v1 and paste your RSA public key. Minelist uses the same TCP protocols when players vote on your listing. NuVotifier can accept both v1 and v2 on the same port depending on config.

Q: Does this test Votifier protocol v2?

Yes. Choose v2 or Auto and enter your NuVotifier token. The tool performs the v2 handshake (VOTIFIER 2 challenge), signs the JSON payload with HMAC-SHA256, and sends the 0x733A-framed packet—the same flow Minelist uses for live votes when a v2 token is configured.

Free Minecraft Votifier Tester — Verify Vote Rewards Before You Go Live

Most popular Minecraft servers on a Minecraft server list offer vote rewards: diamonds, crate keys, coins, XP boosters, or exclusive ranks. Those perks almost always rely on Votifier (or NuVotifier) receiving a vote packet from listing sites like Minelist.

This free online Votifier tester sends the same style of Votifier v1 (RSA) and NuVotifier v2 (token / HMAC) packets Minelist uses when players vote for your listing. Use it to debug connectivity, keys, and ports—before you promise rewards in Discord and wonder why nothing arrives in-game.

What is Votifier (and NuVotifier)?

Votifier is a Minecraft plugin protocol that listens on a dedicated TCP port (commonly 8192) for encrypted vote notifications from server listing websites. When someone votes on Minelist or another list, the site must deliver a packet your server can verify.

Today most networks run NuVotifier, which supports:

Protocol v1 — classic RSA public key encryption (legacy Votifier / NuVotifier v1 listener).
Protocol v2 — shared token with HMAC-SHA256 challenge handshake (recommended for new setups).

Enter the same host, port, RSA public key, and/or NuVotifier token you configured in your Minelist dashboard. A successful test means the vote path from a listing site to your listener is reachable—then reward plugins can turn that event into in-game perks.

How Minecraft vote rewards work with Votifier

Here is the standard growth loop for Minecraft server voting:

A player votes for your server on a Minecraft server list (for example Minelist).
The list sends a Votifier vote notification to your public host and vote port.
NuVotifier (or compatible Votifier) verifies the packet and fires a vote event.
A reward plugin—such as VotingPlugin, SuperbVote, or VoteParty—grants keys, money, or commands.

Players often do not need to be online: many stacks support offline vote queuing. The tester above only proves the listener accepted the packet; reward plugins still need correct config to pay out.

Compatible Votifier plugins and proxy setups

This Minecraft Votifier test tool targets TCP listeners that speak Minelist’s vote protocols:

NuVotifier v2 — paste your token; HMAC-signed JSON with challenge handshake.
NuVotifier / legacy Votifier v1 — paste the RSA public key (PEM); encrypted vote block.
VotifierPlus and other forks — supported when they expose a compatible v1 and/or v2 listener.
Velocity, BungeeCord, Waterfall — test the host/port listing sites actually reach (proxy or backend), matching where NuVotifier binds.

Reward plugins sit after the listener. If the tester succeeds but players get nothing, enable debug logging in VotingPlugin / SuperbVote / VoteParty and confirm commands, economy hooks, and world restrictions.

What this free Votifier checker does not test

HTTP(S)-only vote postbacks with no TCP Votifier listener on your Minecraft host.
Third-party listing API keys or webhook URLs—only that your machine accepts Minelist-style v1/v2 packets.
Whether your in-game reward config is complete (that is a separate plugin step).

Quick NuVotifier setup checklist

Copy your v2 token or v1 RSA public key from NuVotifier config into the matching fields above.
Use the public IPv4 or hostname and open vote port you entered on Minelist and other lists (often 8192).
Forward the port on your router or allow it in the host firewall / panel if the machine is not on a public IP.
Run the Votifier test, then check the server console or vote plugin debug for the test service name and username.
Retest after host migrations, key rotations, Docker port remaps, or moving NuVotifier between proxy and backend.

Why a working Votifier setup grows your Minecraft server

Reliable vote delivery turns a Minecraft server list ranking into real retention: daily voters return for rewards, Discord stay active with vote reminders, and staff spend less time chasing “I voted but got nothing” tickets. Keep tokens, RSA keys, and ports documented; use this free tester whenever something changes on your network.

Grow discovery with honest voting on lists like Minelist.
Improve retention with daily vote reminders and clear reward menus.
Debug faster by confirming the packet path before blaming reward plugins.

Ready to verify? Use the form at the top of this page, then list or update your server on Minelist’s Minecraft server list so players can find you and vote with confidence.

Votifier tester — frequently asked questions

Answers mirror the structured data on this page for search engines and players.

Which Votifier protocols does Minelist support?

Protocol v1 (RSA public key, legacy Votifier / NuVotifier v1 listener) and protocol v2 (NuVotifier shared token, HMAC-signed JSON). Auto tries v2 first, then v1—the same order Minelist uses when players vote on your listing. Works with NuVotifier, original Votifier, VotifierPlus, and compatible forks on your vote TCP port (often 8192). Pure HTTP-only postbacks without a Votifier listener are not supported.

Does this Votifier tester work with NuVotifier?

Yes. Select v2 or Auto and paste your NuVotifier token, or v1 and paste your RSA public key. NuVotifier can expose both protocols on the same TCP port depending on config. Minelist uses the same v1/v2 packets when delivering live votes.

What about the original Votifier, VotifierPlus, or forks?

The original Votifier plugin used the same RSA/TCP wire format. VotifierPlus and other community forks are supported insofar as they keep that listener. The name on the jar matters less than the protocol: VOTIFIER greeting + fixed-size ciphertext.

Which reward / vote plugins are compatible once the packet arrives?

Common stacks include VotingPlugin, SuperbVote, VoteParty, listeners built with NuVotifier’s API, and custom CommandListener scripts. They subscribe to “vote received” events and run commands, give items, or credit economies. This Minelist tester does not configure those plugins—it only proves the encrypted vote reached your Votifier port.

Does the player need to be online for the test vote?

No. The synthetic payload uses a placeholder username (similar to “TestUser”) so it will not match a real session. Many reward plugins queue offline votes anyway; check your plugin’s offline handling and whether it ignores unknown names.

BungeeCord, Velocity, or multiple backends—which IP do I enter?

Use the same host and port your listing sites target. Often that is the backend Paper server’s public IP with NuVotifier installed, or a forwarded port on the proxy if NuVotifier binds there. If NuVotifier listens on 0.0.0.0:8192 inside Docker, you still need the published public port mapped correctly.

Why “connection failed” even though Minecraft works?

Game traffic (25565) and Votifier (8192 by default) are different sockets. Common causes: wrong port, host binding only to localhost, datacenter firewall, home ISP blocking inbound TCP, or testing from a DNS name that resolves to the wrong machine.

Why “invalid public key” or encryption errors?

Paste the full PEM including BEGIN/END PUBLIC KEY lines, without extra spaces from Discord code blocks if possible. Keys must be RSA and typically 2048-bit. If you regenerated keys on the server, update every listing site to the new public key or votes will fail everywhere.

Does this test Votifier protocol v2 or HTTP-only callbacks?

Yes for v2 (token + HMAC on the same TCP port). Pure HTTP webhook receivers without a Votifier TCP listener are not tested—use your provider’s webhook tools for those.

Will this test vote change my Minelist vote totals?

No. The packet is sent directly from your browser session through our server to your host—it is not a real vote on Minelist or any other list. It is only for diagnosing connectivity and keys.

Success on the tester but no rewards in-game—what next?

Open your vote reward plugin config: confirm it listens to NuVotifier events, enable debug logging, and verify commands are not failing silently (economy plugin missing, per-world restrictions, etc.). Also confirm duplicate-vote protection is not discarding the test username.

Related: Minecraft server status checker for game port reachability, and how to make a Minecraft server for hosting basics.

Minecraft Server Votifier Tester