Threat profile

Interception (man-in-the-middle)

An attacker sits between you and a service and reads or alters what passes, typically on an untrusted network.

How it works

On a shared or hostile network, an attacker can try to redirect traffic or present a fake access point. Properly configured HTTPS makes this far harder, because the browser checks the server's certificate and encrypts the traffic. The risk grows when users click through certificate warnings or when a service still allows plain HTTP.

What to look for

  • A browser warning about an invalid or mismatched certificate.
  • A familiar network name that asks you to sign in on an unusual page.
  • A site that suddenly loads over http instead of https.

What reduces the risk

  1. Never accept a certificate warning for a sign-in or payment page.
  2. Prefer mobile data or a trusted VPN on public networks for sensitive work.
  3. Site owners: serve everything over HTTPS and send the Strict-Transport-Security header.
  4. Keep device and browser updated so certificate checks stay current.

Related tool

HTTP security header audit →

Sources

This section is for defence and learning. Do not test systems you do not own or have written permission to test: unlawful access to an information system is an offence (Turkish Penal Code, Article 243).