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 (changeable in your plugin config). Paste the RSA public key from your plugin’s key folder or config—usually a PEM block starting with -----BEGIN PUBLIC KEY-----. The host is the address listings use (your server IP or DNS name), which must be reachable from the public internet if sites send votes from outside your LAN.

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.

Minecraft Votifier Tester (NuVotifier, V1 RSA) — Free Online Tool

Q: Does this Votifier tester work with NuVotifier?

Yes, when NuVotifier is listening for classic Votifier protocol v1 (TCP + RSA vote block on your Votifier port, often 8192). This tool opens a TCP connection, reads the VOTIFIER greeting, and sends the same style of encrypted test vote NuVotifier expects from listing sites. It does not test NuVotifier protocol v2 (token-based) or vote forwarding that only uses HTTP without this TCP listener.

Q: Does this test Votifier protocol v2?

No. Protocol v2 uses a different handshake (keyed tokens / HMAC-style verification). This Minelist tool only sends classic v1 RSA blocks. If your host only enables v2 for listings, use your provider’s v2-specific test or temporarily allow v1 for debugging.

Test your Votifier Configuration for Free

Have you ever seen a Minecraft server offering rewards for voting, such as diamonds, crate keys, in-game currency, or exclusive perks? In that case, Votifier is powering the system behind the scenes.

We'll break down what Votifier is, how it works, and why it's essential for Minecraft server growth and player engagement.

🧠 What Is Votifier?

Votifier is a Minecraft plugin (and protocol) that listens for vote notifications from server listing websites like:

Minelist.com
MinecraftServers.org
and many others

When a player votes on a listing site, your server must accept that vote. The classic Votifier protocol v1 uses TCP (often port 8192) plus an RSA-encrypted vote block—the same flow this page’s tool exercises. Some setups add HTTP callbacks or NuVotifier protocol v2 (token-based); those are separate channels and are not validated by this RSA/TCP tester.

It is how voting becomes more than a leaderboard number: the packet reaches your network, your listener verifies it, and companion plugins turn it into keys, coins, or shoutouts.

🛠️ How Does Votifier Work?

Here's a simplified breakdown of how it operates:

Player votes for your server on a listing website.
The listing site sends a vote notification to your server.
Votifier receives the vote and logs the player who voted.
A reward system (via another plugin or script) gives the player in-game rewards.

Note: The player doesn't have to be online to receive rewards, most modern implementations support offline vote queuing.

Which Votifier-style plugins does this tester target?

The form above is built for the classic listener shared by most “Votifier” ecosystems:

NuVotifier — the common maintained fork on Paper/Spigot; use the public key and port from its config (often still called “Votifier” in hosting panels).
Legacy Votifier — the original plugin’s RSA/TCP v1 behavior; same wire format.
VotifierPlus and other forks — as long as they expose the same VOTIFIER handshake and accept the padded RSA vote block, the test is meaningful.
Velocity / BungeeCord forwarding — test the host/port the vote site reaches (backend or proxy), matching where NuVotifier actually binds.

Reward and queue plugins sit after the listener: VotingPlugin, SuperbVote, VoteParty, VotifierListener (or NuVotifier’s own listener API), LuckyVotes-style bridges, etc. They do not change how the RSA packet is delivered; they consume the vote event once NuVotifier decrypts it.

What this tool does not test

Protocol v2 only setups (no v1 listener).
Pure HTTP(S) postback vote receivers with no compatible TCP RSA port.
Whether your listing’s API key / callback URL on a third-party site is correct—only that your Minecraft host accepts this style of packet.

Quick setup checklist

Open your NuVotifier (or fork) folder and copy rsa/public.key (or the PEM shown in the config) into the form.
Use the public IPv4/hostname and open port your host expects—match what you entered on Minelist and other lists.
Ensure the port is forwarded on the router or allowed in the host’s firewall if the machine is not directly on a public IP.
Run the test, then watch the server console or vote plugin debug for a line mentioning the test service/user.

🚀 Final thoughts

Votifier is more than a single jar—it is the growth loop between server lists and your world. When the listener and keys are correct, reward plugins can thank voters automatically, even if they are offline (depending on your stack).

Grow discovery through honest voting on lists like Minelist
Improve retention with daily vote reminders and perks
Keep keys and ports documented so staff can debug quickly

Use the tester at the top of this page whenever you migrate hosts, rotate keys, or add a new backend behind a proxy.

Votifier tester — frequently asked questions

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

Does this Votifier tester work with NuVotifier? ▼

Yes, when NuVotifier exposes the classic protocol v1 TCP listener (RSA vote block, default port often 8192). NuVotifier is the de facto replacement for the original Votifier plugin on modern Paper servers. If you disabled v1 and only allow v2 tokens, this page cannot validate that path—use a v2-aware tool or temporarily enable v1 for debugging.

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? ▼

No. v2 uses a different token handshake; HTTP-only receivers never see this RSA block. Use your provider’s documentation for v2 or webhook testing, and keep v1 enabled if you still rely on classic TCP from older lists.

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