EncryptCodecencryptcodec
Simulations/DNS Poisoning

DNS Poisoning

Intermediate

Poison a DNS cache to redirect victims to a malicious server, capture their credentials, then learn how DNSSEC prevents this attack.

Progress:
1
Intercept DNS Query
2
Harvest Credentials
3
Defend with DNSSEC
DNS Resolver — Cache
google.com142.250.80.46SIGNED
bank.example.com93.184.216.34SIGNED
api.stripe.com52.4.141.29SIGNED
DNS query for bank.example.com is pending...
Legitimate response: 93.184.216.34
DNS Query in Progress
$ dig bank.example.com
;; QUESTION SECTION:
;bank.example.com.    IN  A

;; ANSWER SECTION (pending...):
bank.example.com.  86400  IN  A  93.184.216.34

Race the legitimate response with your forged answer...

Challenges

1
Intercept DNS Query
Spoof the DNS response for bank.example.com to point to your malicious IP.
hints
2
Harvest Credentials
Capture the victim's login credentials on your spoofed banking site.
hints
3
Defend with DNSSEC
Enable DNSSEC validation to block the forged DNS record.
hints
How to fix DNS poisoning
DNSSEC, DoH, and certificate pinning stop cache poisoning

Frequently Asked Questions