Certificate Validation Failures
What you'll learn: How to detect SSL/TLS interception by spotting certificate pinning violations, mismatched chains, and unexpected issuers.
When you intercept SSL/TLS traffic (as in a MITM attack from earlier lessons), the attacker's system must present a replacement certificate to the victim—because the attacker doesn't have the legitimate server's private key. Modern browsers and apps check certificates carefully, and when something's off, you see certificate validation failures—telltale signs of interception.
Why Certificates Fail Validation
-
Unexpected Certificate Issuer
You expect Amazon's certificate to be signed by a trusted CA like DigiCert. If you suddenly see it signed by "BurpSuite CA" or an unknown issuer, that's a red flag. Someone (or some tool) is intercepting your traffic. -
Certificate Chain Mismatches
SSL certificates form a trust chain: server cert → intermediate CA → root CA. If the chain is broken, incomplete, or contains certificates that don't logically connect, validation fails. This often happens when MITM tools generate on-the-fly certificates. -
Certificate Pinning Violations
Some apps "pin" a specific certificate or public key—they'll only trust that exact cert, ignoring the OS certificate store. If the app detects a different certificate (even if signed by a trusted CA), it refuses the connection. This is a defense mechanism against interception.
What This Looks Like
Browser warnings like "Your connection is not private" or "Certificate error" often mean someone is tampering with the encrypted channel—or the server misconfigured its certificate. In corporate networks, you might see this if IT installs a TLS inspection proxy with a custom CA.
Key Takeaway:
Certificate validation failures—wrong issuers, broken chains, or pinning mismatches—are critical indicators that SSL/TLS traffic is being intercepted or manipulated.