Compromised packages in npm, PyPI, and other open-source ecosystems cause real damage – from backdoors to ransomware. CVE monitoring arrives too late, and whether you were affected is often impossible to say. A look at the problem, and how to at least trace the blast radius.
TXT Verify Records are the standard mechanism for proving domain ownership to third-party services. This article explains how verification works technically, where it's used, and what risks arise when tokens accumulate uncontrolled in your DNS.
Most teams don't know exactly which domains they own, where they're registered, and what points where. That's not a security problem – it's an organization problem. Until it isn't.
You're starting a new project, registering a domain, and want to do it right from the beginning. Here's a pragmatic checklist for a clean DNS configuration – no paranoia, just common sense.
SPF, DKIM, and DMARC protect your domain from mail spoofing. But they're only as strong as the DNS records they're defined in. Change a record, break the chain of trust.
TLS certificates expire. Automatic renewal can fail. And an unnoticed certificate issuance can mean someone else controls your domain.
The CAA record defines which certificate authorities may issue TLS certificates for your domain. Without it, anyone can. If it's manipulated, you lose control over your encryption.
The MX record determines which server receives your emails. If it's manipulated, password resets, contracts, and 2FA codes end up with the attacker.
The NS record determines which nameservers are authoritative for your domain. If it's manipulated, an attacker can freely define every other record – without you noticing.
We invest in firewalls, MFA, and encryption. But DNS and TLS – the foundation everything stands on – we often only monitor by accident.