← Back to Home

How to Find Which KMS Server Windows Is Using

Last updated: July 31, 2026

Windows records its KMS host in three places - the licensing service, DNS and the registry. This guide shows how to read all three, how to tell a safe local host from a random third-party server, and what to do if you don't like what you find.

Verified Download - KMSPico Official
KMSPico_Official_v10.2.0.rar
Archive password: 123456  ·  8.3 MB  ·  v10.2.0
Download KMSPico
Extract with WinRAR using the password above, then run as administrator. Works on Windows 10, 11, Server & Office.

The Three Places Windows Stores Its KMS Host

Run all three checks - they answer different questions:

> slmgr /dlv
> nslookup -type=srv _vlmcs._tcp
> reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform" /v KeyManagementServiceName

slmgr /dlv shows the host actually registered with the licensing service. nslookup shows what DNS auto-discovery would hand out. The registry value shows a host that was pinned manually with slmgr /skms.

Reading slmgr /dlv output

In the /dlv dialog, scroll to the bottom section. Registered KMS machine name is the live answer - the host your activation renews against every 180 days. You will also see the KMS port (default TCP 1688) and the activation interval. If the line says the machine is using a KMS host at all, your edition is a volume (GVLK-based) edition; retail and OEM activations show no KMS section at all, which is normal for Home licenses activated with a product key.

Reading the DNS SRV record

When no host is pinned manually, Windows asks DNS for _vlmcs._tcp service records and activates against whatever answers. That makes the SRV check important on any network you don't fully control: if a coffee-shop, campus or ISP DNS server publishes a _vlmcs record, your PC may silently activate against a stranger's server. On a healthy home or corporate network the query either returns your organization's host or nothing at all.

Local host vs third-party host: why it matters

A KMS host can see every client that checks in - machine name, product, activation timestamps. If your registered host is an unknown public server, an outside party is not only logging that metadata, they also control whether your renewals succeed; if their server disappears, your activation starts counting down 180 days and eventually lapses. The fix is simple: point Windows at a host you control. A local KMS host - the kind KMSPico sets up on your own machine - removes the dependency entirely: nothing to reach over the network, no third party in the loop, renewals that cannot be blocked by firewalls or DNS changes.

Let a tool do the checking for you

If reading registry values and SRV records feels like more archaeology than you signed up for, the one-click route is easier: KMSPico detects the current licensing state, clears any third-party host configuration and activates Windows (and Office, in the same run) against its own local KMS emulator. Antivirus engines flag KMS utilities generically - an expected false positive for the category - and the build on this site is verified clean before release.

Don't trust a stranger's KMS server?

KMSPico clears third-party host settings and activates Windows + Office against a local KMS host on your own PC - one click, automatic 180-day renewals.

Download KMSPico Free
Open an elevated Command Prompt and run slmgr /dlv. The Registered KMS machine name line shows the host. You can cross-check with nslookup -type=srv _vlmcs._tcp and the KeyManagementServiceName registry value under SoftwareProtectionPlatform.
It is the DNS SRV record name that KMS clients query for auto-discovery. When no host is set manually, Windows asks DNS for _vlmcs._tcp and activates against the host the record points to, on TCP port 1688 by default.
It is a real privacy and reliability risk: the host operator sees your machine name and check-in times, and your activation lapses if their server goes offline. A local KMS host on your own PC avoids both problems.
Use slmgr /skms newhost in an elevated prompt, then slmgr /ato - or clear the pinned host with slmgr /ckms. KMSPico does the whole reconfiguration automatically in one click.

More ways to confirm your KMS setup

Event Viewer keeps a paper trail. Under Applications and Services Logs, look for Key Management Service events: activation requests, renewals and failures are all logged with the host they talked to, which is invaluable when slmgr /dlv and reality seem to disagree.

Office keeps its own KMS configuration, separate from Windows. The equivalent check is cscript ospp.vbs /dstatus from the Office16 folder - the KMS machine name line there can legitimately differ from the Windows host, so check both before drawing conclusions.

On domain networks, Group Policy can pin a KMS host that overrides whatever was set locally. If your manual /skms change keeps reverting, gpresult /h report.html will show whether a policy is reapplying it - a common surprise on ex-corporate laptops.

A quick connectivity test completes the picture: Test-NetConnection your-kms-host -Port 1688 in PowerShell tells you whether the host you found is actually reachable. An unreachable registered host explains most pending-expiration surprises.

None of these checks change anything on the system - they are pure inspection. You can run all of them, screenshots included, before deciding whether to keep the current host, switch to another, or hand the whole configuration to a one-click tool.

Get the KMSPico Official Bundle

Download the verified release and start activating Windows or Office in seconds.

Archive password: 123456

Download KMSPico RAR