identify Lucky scan traffic
A Lucky worker may connect to your server, request its public status, read the reply, and disconnect. Other scanners send the same request, so a connection alone cannot identify us.
[a status scan]
A worker sends the same status request used by Minecraft's multiplayer server list. It does not join the world. Targets are chosen by network address, not by the server's owner, players, or builds.
[where it comes from]
Members run workers from their own computers and hosted machines, so Lucky does not have a stable set of scanning addresses. A source-address list would quickly become incomplete.
A connection from an unfamiliar address is not enough to prove it came from Lucky. If you need help identifying traffic, email contact@lucky.systems.
[warning visits]
A status scan never joins the server. Outreach is separate. When an unfamiliar account can get in, our bot may join as LuckySystems, post a warning, and disconnect.
The secure-server guide explains what the bot does, how to verify a warning, and how to protect the server.
[stop the traffic]
A confirmed opt-out stops status scans and outreach to that address and port for one year. You prove control by placing a short code in the server's MOTD; no Lucky account is needed.
If you operate an address range or host servers for customers, email contact@lucky.systems to request a range exclusion.