PMKID vs Handshake: WiFi Security Explained Simply
If you've read about WiFi password recovery, you've probably encountered two cryptic terms: PMKID and handshake. What are they, how are they different, and why does it matter for your home network? This article explains both concepts in plain language — no cryptographic background required. Whether you're a curious homeowner, a student learning cybersecurity, or someone who just wants to understand what these terms mean, this guide breaks down the technical concepts into simple analogies and practical explanations.
The elevator pitch
A WPA handshake is like a conversation between your phone and your router when it connects to WiFi. An eavesdropper can record that conversation and later try to guess the password from it.
PMKID is not part of that public announcement. It is a receipt the router hands out during the connecting conversation: a tester within range can request it from the AP without waiting for any real device to connect.
Both can be used to recover a WiFi password — but they work differently. Think of it as two different locks on the same door: either one can be used to get in, but one (PMKID) is sometimes easier to reach.
What is a WPA handshake?
When your phone, laptop, or any WiFi device connects to a WiFi network, it goes through a 4-step authentication process called the '4-way handshake'. Both devices agree on encryption keys without ever sending the actual password over the air.
Step 1: The router sends your phone a random number (called an 'Anonce'). Step 2: Your phone sends back its own random number (called a 'Snonce') plus a calculated tag (called a MIC) that proves it knows the password. Step 3: The router sends its own MIC to prove it knows the password too. Step 4: Both devices now have everything they need to encrypt traffic.
Why it matters for password recovery: a bystander who captures these 4 messages can use the MIC to test password guesses offline. This is the basis of WPA2 password cracking with tools like hashcat.
The limitation: to capture a handshake, you need a client device to connect (or reconnect) while you're listening. If no one connects during your capture window, you get nothing.
Simple analogy — the secret handshake
Imagine two people agreeing on a secret handshake. The handshake itself doesn't reveal the secret — but an observer who records the moves could go home and try different secrets to see which one produces the same moves. That's the WPA handshake in a nutshell.
What is PMKID?
PMKID stands for Pairwise Master Key Identifier. It is a 16-byte value — PMKID = HMAC-SHA1-128(PMK, "PMK Name" || AP_MAC || STA_MAC) — that the access point can optionally place in the key-data field of EAPOL message 1 of the 4-way handshake. A client can also advertise it in the RSN IE of its (re)association request when it wants to reuse a cached PMK. Beacons carry only the SSID and AKM; they do not carry a PMKID.
The PMKID is therefore derived from the PMK — which itself comes from the passphrase and the SSID through PBKDF2 — plus the AP's and the station's MAC addresses. In a clientless test there is no real station: the station MAC is the tester's own adapter or a spoofed address, which is why the hash line carries MAC_AP and MAC_STA rather than a real client.
Why it's useful: to capture a PMKID, you need to be within WiFi range and request it from the router — the capture tool sends an association request and reads the EAPOL message 1 that comes back. You don't need to wait for any device to connect. That makes PMKID capture simpler than handshake capture in many scenarios.
Limitation: whether an AP hands out a PMKID is a firmware and implementation choice, not a setting you can rely on. Many access points simply do not populate it, or disable PMK caching, so the request returns an M1 with no PMKID. Note also that this has nothing to do with Protected Management Frames (802.11w): PMF's job is rejecting forged deauthentication and disassociation frames, which is what the deauth-based handshake path depends on.
PMKID vs Handshake — key differences
What's needed to capture: Handshake = a connecting device (you prompt a reconnect, or wait for one). PMKID = no client needed — you send an association request and read the AP's EAPOL message 1.
Time to capture: Handshake = seconds to minutes (waiting for client reconnection). PMKID = one association round trip when the AP cooperates, though retries are common and some APs never return a PMKID.
Success rate: Handshake = depends on having a client to prompt. If no clients are connected and none can be prompted, you cannot capture a handshake. PMKID = depends on the AP's firmware populating it — many do not.
Applicable networks: Handshake = all WPA/WPA2 networks, and the WPA2 leg of a transition-mode network. PMKID = WPA2 networks whose firmware exposes it; 802.11w is unrelated. Does NOT work on WPA3-SAE.
Cracking difficulty: Identical — both derive the same PMK from PBKDF2(password, SSID). Hashcat mode 22000 handles both formats at the same speed.
Tools required: Handshake = airodump-ng + aireplay-ng (or hcxdumptool). PMKID = hcxdumptool (simpler command, fewer dependencies).
Does PMKID work on WPA3?
No. PMKID capture does NOT yield a crackable result on WPA3-SAE networks — but not for the reason that management frames are encrypted. The RSN IE is not carried during the SAE exchange at all, and the RSNE or PMKID that appears in association frames and EAPOL message 1 is unencrypted, because no key exists yet at that point.
The real reason is where the PMK comes from. WPA3-SAE derives the PMK from the Dragonfly commit and confirm exchange rather than from PBKDF2(passphrase, SSID), so an SAE capture is not an offline password oracle: there is no static value to test a candidate against. hcxpcapngtool refuses to convert SAE material for exactly this reason ('PMK not recoverable' for AKM 00-0F-AC:8), and hashcat has no mode for it.
For WPA3 networks in Transition Mode: the risk is the WPA2-PSK leg. The same passphrase is used for both AKMs, so the WPA2 path stays capturable and crackable as ordinary WPA2 — a downgrade risk that is independent of the PMF setting (in transition mode PMF capability is set by the specification as optional on the WPA2 leg).
Which is better for password recovery?
For the average home user trying to recover their own forgotten password: neither. You should check a connected device first (Windows, Mac, iPhone, Android) or access your router admin panel. Handshake and PMKID recovery are last-resort methods.
For password recovery on your own network when no device is connected and admin access is lost: PMKID is preferred if the router exposes it — no client interaction required. If PMKID fails, handshake capture is the next option.
For security testing of your own network: the PMKID attack is a good test of whether your router populates a PMKID and whether your password is strong enough. If you can capture a PMKID from your own network, anyone else within range can request one too.
From a security perspective: WPA3-only mode (not transition mode) removes offline dictionary attacks against the handshake and PMKID on patched devices. Transition mode leaves the WPA2-PSK path capturable and crackable by downgrade, and a weak passphrase remains guessable online in any mode. If you must use WPA2, the only real defence against PMKID or handshake cracking is passphrase entropy — use a long random password; enabling PMF (802.11w) protects against forged deauthentication and downgrade attempts, but it does not change whether a captured WPA2 PMKID is crackable.
How to check if your router exposes PMKID
If you're curious whether your home router exposes the PMKID, here's a safe way to check on your own network: download and install hcxdumptool on a Linux machine with a compatible WiFi adapter (Alfa AWUS036ACHM recommended). With hcxdumptool 6.2.x, run: sudo hcxdumptool -i wlan0 -o capture.pcapng --enable_status=1. Version 6.3.0 changed several options: the capture file is now written with -w instead of -o (sudo hcxdumptool -i wlan0 -w capture.pcapng) and the status option was renamed, so --enable_status on a current build returns 'unrecognized option'. Let it run for 30 seconds. Check the output with: hcxpcapngtool -o hash.hc22000 capture.pcapng. If the hash file contains a line starting with 'WPA*01*', your router returned a PMKID.
If your router exposes PMKID: the practical fix is a long random passphrase (generated by a password manager, not based on dictionary words), and WPA3-only mode where all your devices support it.
If your router does NOT expose PMKID: the most likely explanation is that its firmware does not populate the PMKID (or has PMK caching disabled) — that is a firmware choice, not a setting you have misconfigured, and it is not evidence that PMF is off. Nothing about your router's PMF configuration changes whether a WPA2 PMKID or handshake is crackable; keep PMF enabled for its actual purpose, which is rejecting forged deauthentication and downgrade attempts.
Only test your own network
Attempting to capture a PMKID or handshake from a network you do not own is illegal in most jurisdictions, and transmitting association requests or deauthentication frames to a network you do not own is an active interference offence — the treatment of mere passive reception in range varies by country. Only perform these tests on your own router or one you have written permission to test.
PMKID vs Handshake decision guide
- 1
Try connected device first
Check Windows, Mac, iPhone, or Android for saved WiFi passwords. Fastest and simplest method.
- 2
Try router admin panel
Go to 192.168.1.1 and log in. Default password on router sticker.
- 3
Check if PMKID is available
Use hcxdumptool on your own network, or one you have written permission to test. If the AP returns a PMKID, cracking can proceed without client interaction.
- 4
If no PMKID, capture a handshake
On a network you own or have written permission to test: use aircrack-ng or hcxdumptool with a deauth to prompt a client reconnection. Deauth is an active injection that disrupts other people's devices — never run it anywhere you are not authorized.
- 5
Crack with hashcat mode 22000
Both PMKID and handshake use the same format. Convert to .hc22000 and crack the passphrase of your own network with a dictionary and rules.
Frequently Asked Questions
What does PMKID stand for?
Is PMKID easier to capture than a handshake?
Does PMKID work on WPA3?
Is PMKID faster to crack than a handshake?
Does every router support PMKID?
Should I disable PMF on my router to prevent PMKID exposure?
Can't find the WiFi password another way?
If every device-side method failed, use the authorized recovery form for a file-specific assessment. The result depends on capture quality, password clues, and the candidate set that can be justified.
Open Recovery Tool