Case F6271B · Network · L3 Applied

Our Mail Domain Moved Overnight

Practise as: Incident drillLevel: L3 Applied

Live alertYour Certificate Transparency monitor flags a new Let's Encrypt cert for mail.example-corp.com issued at 03:20 UTC. Public DNS now resolves mail to 198.51.100.23, and the registrar log shows an NS change from an unknown IP.

  1. 01 What happened?
  2. 02 What is the impact?
  3. 03 What do you do?
What a strong answer covers

Try it out loud first. Then check yourself:

  1. DNS infrastructure hijack: registrar or DNS provider account compromised, records repointed, valid cert issued via DV
  2. Impact: users and mail servers connect to an attacker proxy with a trusted cert, harvesting credentials and email
  3. Respond: regain the registrar account, revert NS and records, revoke rogue certs, reset creds used during the window
  4. Scope: lower TTLs do not undo caching; check which records changed, for how long, and logins from captured accounts
  5. Prevent: MFA and registry lock at the registrar, CAA records, CT and DNS change monitoring, as CISA ED 19-01 urged

If the interviewer pushes back

  • Would DNSSEC have prevented this attack? Explain why or why not.

Go deeper

More Network cards

All Network cards →

cardosec draws a security topic and gives you a clock: explain it out loud with no notes, then see what you covered and what you missed. Free during early access.

Reviewed 2026-10-09