TeamSpeak 3 Server Status live online check

Check in seconds whether a TeamSpeak 3 server is online. We read slots, version, platform and uptime via ServerQuery and test the key ports (Voice, File Transfer, ServerQuery, WebQuery). Free, no signup, with anti-SSRF protection.

Enter server address

How does the TS3 status check work?

The tool's server first resolves the entered hostname via DNS and verifies that the returned IP is publicly routable. Private ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16, 127.0.0.0/8, link-local, loopback) are categorically rejected. Only then does it open a TCP connection to the ServerQuery port 10011, read the TS3 banner and query the protocol with the commands version, use port=<voice> and serverinfo.

Then the tool runs a short TCP connect against the typical ports (Voice 9987 as UDP is not actively tested because UDP isn't reliably verifiable via connect probe; we test 10011, 30033 and 10080). All sockets have hard timeouts (2 seconds for ServerQuery, 0.8 seconds per port check) so response time stays low.

ServerQuery, slots and port visibility explained

TeamSpeak 3 separates the voice protocol (UDP, default port 9987) from the management interface ServerQuery (TCP, port 10011). Tools like this one read metadata via ServerQuery: slots, version, platform, uptime. For anonymous (unprivileged) access to return data, the default server group needs the b_virtualserver_info_view right. Many admins remove it deliberately, so competitors or bots can't collect slot statistics. In that case we see "Hidden".

Voice: UDP 9987 (default, often custom)
ServerQuery (raw): TCP 10011
ServerQuery (SSH): TCP 10022 (if enabled)
File Transfer: TCP 30033
WebQuery (HTTP): TCP 10080
WebQuery (HTTPS): TCP 10443 (if enabled)

Why some servers only respond partially

There are three common reasons for an incomplete answer. First: the firewall blocks port 10011 from outside, so we mistakenly see the server as "Offline". Second: ServerQuery is reachable, but the unprivileged group isn't allowed to call serverinfo . Third: the voice port you entered doesn't exist on this instance (multiple virtual servers share a daemon). In the last case the tool reports "Partially reachable".

Anti-DDoS providers, NAT firewalls and IPv4 CGNAT can also cause the ServerQuery port to not respond from outside while the voice port is forwarded. In those cases only a voice client test will tell.

Privacy and limits

We don't store inputs long-term. For rate limiting (20 requests per minute per IP) a hash of the client IP is briefly held in the tool container and overwritten after 60 seconds. There is no tracking, no cookies and no third-party scripts other than hCaptcha (to protect against automated mass queries).

Tool limits: TeamSpeak 5 servers (new protocol) are not supported. TeaSpeak is largely compatible, though some fields may be missing. UDP voice ports are not actively tested because TCP connect probes against UDP aren't meaningful. For internal servers (private IP ranges) this tool is intentionally not usable; use a local client instead.

Frequently Asked Questions

How does the TeamSpeak 3 status check work?

We try to open a TCP connection to the ServerQuery interface (port 10011) of your TS3 server, read the banner and query version, platform, slots and uptime over the official ServerQuery protocol. Then we check via TCP connect whether the standard ports (Voice, File Transfer, ServerQuery, WebQuery) are open.

Why does uptime or slot count sometimes show as "Hidden"?

TeamSpeak lets server admins restrict the serverinfo command to authenticated ServerQuery logins only. If anonymous (unprivileged) access is restricted, the server replies with error id=2568 (insufficient client permissions). We then show "Restricted (Hidden)". This is not a bug; it's deliberate configuration.

What do ports 9987, 10011, 30033 and 10080 mean?

Port 9987 (UDP) is the default voice port that clients use to talk. Port 10011 (TCP) is the ServerQuery interface for admins and tools like this one. Port 30033 (TCP) is used for file transfers (avatars, icons, channel files). Port 10080 (TCP) is WebQuery, an HTTP variant of the ServerQuery API.

How do I allow public ServerQuery queries?

In ts3server.ini check or empty out query_ip_allowlist.txt. Port 10011 also needs to be open in the firewall. For full status queries without login, you have to give the serveradmin group or a dedicated ServerQuery group the b_virtualserver_info_view right. Be aware: an open ServerQuery port is a popular brute-force target; secure it with query_ip_denylist.txt or a firewall whitelist.

Why does the tool sometimes show "Version: Unknown"?

The version command is restricted on some servers for anonymous ServerQuery connections. Older TS3 versions also respond differently to the banner. In this case we can see that the server is online (TS3 banner present), but we don't get version details.

Which server versions are supported?

All official TeamSpeak 3 server versions since 3.0.x. The ServerQuery banner and protocol have been stable across all 3.x versions. We test regularly against the current 3.13.x line.

Does the tool work with TeamSpeak 5 or TeaSpeak?

TeamSpeak 5 (server) uses a completely new protocol and is not backwards-compatible with TS3 ServerQuery. TeaSpeak is largely ServerQuery-compatible and should work, though some fields (e.g. virtualserver_uptime) can differ. Coverage is most complete for pure TS3 servers.

Are my inputs stored?

No. The address you enter is used only for the direct query and is not logged. We only log anonymized IP and timestamp for rate limiting (20 requests per minute). The tool is anti-SSRF hardened: only publicly reachable IPs are contacted at all; private and reserved networks (RFC 1918, loopback, link-local) are blocked before any connection.

All KernelHost Products

Need more than just tools? Take a look at our commercial hosting lineup.

KVM-Rootserver from 4,99 €/mo Dedicated-Server from 69,99 €/mo Minecraft-Server from 4,00 €/mo Webhosting from 3,99 €/mo Private VPN-Server Dedicated IP DDoS Protection 3.2 Tbps Arbor