Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Responder?

Responder answers broadcast name resolution requests on a local network and impersonates the service the victim was looking for, capturing authentication material in the process.

Illustration for the cybersecurity term Responder
Home / Blog / Cybersecurity Terms / What Is Responder?
17 November 2026

What Is Responder?

What Is Responder?

Responder is a small Python tool that exploits an old convenience in Windows networking. When a client cannot resolve a name through DNS, it shouts the question to the whole local subnet using LLMNR, NBT-NS, or mDNS, and accepts an answer from whoever replies first. Responder always replies first, claims to be the host the victim wanted, and then presents a fake SMB, HTTP, LDAP, or SQL service to collect the authentication the client offers.

What comes back is a NetNTLM challenge-response. It is not a password, but it can be cracked offline or, more dangerously, relayed in real time to a service that will accept it. On an internal penetration test, Responder is typically the first thing started and frequently produces domain credentials within minutes.

Why the Victim Cooperates

Nothing needs to be exploited. The failed lookups that trigger this happen constantly on real networks, for mundane reasons: a mistyped share name, a mapped drive pointing at a decommissioned server, a printer reference in a logon script, a browser looking for a proxy configuration. Windows resolves the name, fails in DNS, falls back to broadcast, and sends credentials to whatever answers.

The web proxy case is the most productive. If a machine is configured to detect proxy settings automatically and no wpad record exists in DNS, the client broadcasts for it. Responder supplies a rogue proxy configuration, and from that point the browser authenticates to the attacker for ordinary web requests.

What an Operator Does Next

PathRequirementOutcome
Offline crackingA weak or reused passwordThe plaintext password, usable anywhere
SMB relaySMB signing not enforced on the targetCode execution or file access as the captured user
LDAP relayLDAP signing or channel binding not enforcedDirectory modification, including adding computer accounts

The relay path is the one that turns a captured hash into immediate compromise, and it is covered in more detail under NTLM relay attacks. Responder is usually paired with a relay tool for this, with its own SMB and HTTP servers disabled so they do not compete for the connection.

Captured NetNTLMv2 hashes are cracked with Hashcat in mode 5600. A fifteen-character passphrase will survive; a seasonal password with a number on the end will not survive the lunch break.

Shutting the Technique Down

This is one of the few internal findings with a clean, complete fix. The attack depends on fallback protocols that almost no modern environment needs.

Password strength is the backstop rather than the control. Long passphrases and multi-factor authentication limit what a cracked hash achieves, but they do not stop relaying, because a relayed authentication never needs the password at all.

Detecting It

Poisoning is noisy if anyone is listening. A host answering LLMNR or NBT-NS queries for names it has no relationship with is anomalous by definition, and network monitoring with Zeek or an IDS rule set will show one source responding to many different queries. Sudden SMB or HTTP authentication attempts from workstations to a machine that is not a server deserve the same scrutiny.

Honey credentials are the cheapest high-confidence detection available. Plant a non-existent hostname in a logon script or a mapped drive and alert whenever anything resolves it, because only a poisoner will ever answer. An account that exists solely to be captured, with alerting on any use, works the same way.

Where It Fits in Testing

Responder appears in almost every internal infrastructure assessment and assumed-breach exercise, because it tests network hygiene, password policy, and detection in one go. A clean result, meaning no responses captured over several hours on a busy subnet, is a genuine sign that the basics have been done. Our Infrastructure Security Testing Services include this assessment alongside wider Active Directory security review.

FAQ – Frequently Asked Questions

Does Responder Capture Actual Passwords?

Not directly. It captures NetNTLM challenge-response material, which is derived from the password but is not the password itself. That material can be cracked offline if the password is weak, or relayed to another service to authenticate as the user without ever recovering the plaintext. Strong passphrases defeat cracking but do nothing against relaying.

How Do We Stop LLMNR Poisoning?

Disable LLMNR and NetBIOS name resolution through Group Policy and DHCP options, create a DNS entry for wpad so proxy detection never broadcasts, and enforce SMB signing and LDAP channel binding so captured authentication cannot be relayed. These changes rarely break anything in an environment with healthy DNS, but test them with a pilot group first.

Will Disabling LLMNR Break Our Network?

In most organisations, no. LLMNR and NBT-NS are fallback mechanisms for when DNS fails, and correctly configured networks do not depend on them. Problems appear where legacy applications or small workgroup devices resolve names by broadcast. Roll the change out in stages, monitor for failures, and fix the underlying DNS records that the fallback was hiding.

Is Running Responder Legal?

Only with authorisation. Responder intercepts other people’s authentication traffic on a network, which in the UK engages the Computer Misuse Act 1990 and interception provisions. Authorised testers operate under written rules of engagement that name the networks in scope, and they handle captured material as confidential evidence that is destroyed when the engagement ends.

Related Terms

You May Be Interested In These

What Happened in the Equifax Data Breach?

Cybersecurity Terms

17 November 2026

What Happened in the Equifax Data Breach?

Read More
What Is PwnKit?

Cybersecurity Terms

17 November 2026

What Is PwnKit?

Read More
What Is Proxychains?

Cybersecurity Terms

17 November 2026

What Is Proxychains?

Read More