Cloudflare announced that Certificate Transparency Monitoring, a feature that alerts domain owners when a TLS certificate is issued for their domain by someone other than themselves, is now generally available on every Cloudflare plan at no additional cost, including the free tier. Certificate Transparency is a public logging system that certificate authorities are required to write to whenever they issue a certificate, and it exists precisely so that domain owners and researchers can catch mis-issued or fraudulently obtained certificates, which are a common building block in phishing campaigns and man-in-the-middle attacks against a brand's users. The practical challenge with CT logs has always been noise: a domain behind Cloudflare can generate a large number of its own legitimate certificate events, from Universal SSL renewals to backup certificates to Advanced Certificate Manager issuances, all of which get logged the same way as anything else. Cloudflare's monitoring tool automatically filters out certificates it issued itself on a customer's behalf, so the alerts that reach a security team are much more likely to represent something that actually needs investigating rather than routine housekeeping. More than 650,000 customer domains already have the feature turned on since it began rolling out, and it's managed from a single settings view in the dashboard under SSL/TLS, regardless of which plan tier an account is on. For engineering teams without a dedicated security function, this closes a real gap: catching a rogue certificate quickly can be the difference between an attempted impersonation attack getting shut down before it's used and a customer stumbling into a convincing phishing site that presents a technically valid certificate. Making the capability free rather than gating it behind Enterprise plans, as competing CDN and DNS providers often do, also lowers the bar for smaller teams and side projects that wouldn't otherwise have budget for dedicated certificate monitoring tooling, and it fits a broader pattern of core security hygiene features drifting from paid add-ons toward table-stakes defaults across the industry.