— completely unreadable without the server's private key.
The attacker places themselves between your device and the server. On a local network this is done via ARP spoofing, a rogue Wi-Fi hotspot, or a compromised router.
Because HTTP has no encryption, all traffic flows through the attacker's machine in plain readable text. Tools like Wireshark or mitmproxy can capture it automatically.
The attacker can read credentials silently — or even modify the page content in transit, injecting malicious scripts before the page reaches you.
TLS encrypts the entire connection. Even if traffic is intercepted, the attacker sees only encrypted bytes. Look for https:// and a padlock icon.
Sites hosted by raw IP address (like this demo) cannot obtain a TLS certificate from a public CA. This forces HTTP — another reason to use a proper domain with HTTPS.
Coffee shops, hotels, and airports are prime MITM hunting grounds. Anyone on the same network can run this attack against HTTP traffic. Always verify HTTPS before logging in.