CDNs Are a Single Point of Failure
CDN consolidation means a single outage takes down thousands of sites. We traded distributed resilience for centralized convenience.
Read moreOn protocols, security, and how the internet actually works.
CDN consolidation means a single outage takes down thousands of sites. We traded distributed resilience for centralized convenience.
Read moreDoH wraps DNS queries in HTTPS. Same questions, same answers, different transport. The technical change is simple. The political implications are enormous.
Read moreCDN cache poisoning tricks a CDN into caching a malicious response and serving it to all subsequent visitors. One weird request, a lot of collateral.
Read moreWhen a certificate is compromised, it needs to be revoked. Both mechanisms for checking revocation are fundamentally broken. Here's why.
Read moreQuantum computers will break RSA and elliptic curve crypto. The transition has already started — not because quantum computers are here, but because 'harvest now, decrypt later' is a real threat.
Read moreHTTPS encrypts everything — except which website you're visiting. The Server Name Indication field travels in plaintext before encryption starts.
Read moreTLS 1.0 and 1.1 are formally deprecated and rejected by every browser. And yet servers still offer them. How many, and why?
Read moreA VPN shifts who can see your traffic from your ISP to the VPN provider. You're trusting a different entity, not eliminating trust.
Read moreAbstraction made the internet usable. It also made it opaque. The cost shows up in bad security decisions, helplessness during outages, and cargo-cult configuration.
Read moreEvery messaging app claims E2EE. Most users think it means total privacy. The reality is more nuanced, and the marketing oversells it.
Read moreBGP routes the internet with no built-in authentication. Any autonomous system can announce any prefix. Route hijacking is trivially possible. Here's how it works and what RPKI is trying to fix.
Read moreEvery TLS certificate issued by a public CA is logged in a publicly searchable, append-only log. This happened because of DigiNotar. Here's how CT works and why it matters.
Read moreSOC 2, ISO 27001, PCI DSS — organizations treat compliance as proof of security. It isn't. Compliance is a floor. Security is the actual state of your defenses.
Read moreMost domains that 'have' DMARC set it to p=none, which means monitor but don't enforce. It's a smoke detector without a siren.
Read moreYou type a URL and the page loads. In between, your computer talked to at least four servers, traversed a hierarchy from 1983, and relied on caching so aggressive most queries never reach their destination.
Read moreDNSSEC is elegant cryptography with brutal operational reality. Two decades in, adoption is still under 20%. The protocol isn't the problem.
Read moreSPF, DKIM, DMARC, MTA-STS, BIMI — five standards, twenty years, and the percentage of domains that have all of them could fit in a margin of error.
Read moreNot all security headers are equal. Some prevent real attacks daily. Some are legacy relics browsers ignore. Here's an honest priority list.
Read moreThe gap between easy headers and hard headers is enormous. Most sites set X-Content-Type-Options and skip Content-Security-Policy. The data shows exactly how wide the gap is.
Read moreBefore 2015, HTTPS meant someone cared. After Let's Encrypt, HTTPS means the server exists. We got encryption everywhere and lost a trust signal nobody has replaced.
Read moreModel Context Protocol gives AI agents a standard way to call security tools. The recon workflow is about to change. The judgment part isn't.
Read moreThe browser padlock creates false trust in hundreds of millions of users. HTTPS means encrypted, not safe. The icon should go.
Read morePasskeys are technically superior in every way — phishing-resistant, no shared secrets, biometric-friendly. Apple, Google, and Microsoft all support them. Adoption is still negligible.
Read moreI build security scoring systems. I know better than anyone that they don't measure actual security. Here's why I keep building them anyway.
Read moreRFC 7208 limits SPF to 10 DNS lookups. Exceed it and your email authentication silently breaks. The limit made sense in 2003. It doesn't anymore.
Read moreEvery HTTPS connection starts with a negotiation most developers never think about. Here's exactly what happens in TLS 1.3, step by step.
Read more2FA stops credential stuffing. It barely slows down the real-time phishing proxies that are actually stealing sessions in 2026.
Read moreIn 2011, DigiNotar was hacked and 500+ fraudulent certificates were issued, including *.google.com. The aftermath reshaped the entire PKI ecosystem.
Read moreSPF, DKIM, DMARC, BIMI, MTA-STS — email keeps stacking protocols on a 50-year-old system instead of replacing it. Here's why.
Read moreZero Trust started as a legitimate security architecture principle. It has been co-opted by every vendor to mean 'buy our product.' The original idea deserves better.
Read more