November 3, 2026

CAA Records: Tightened Here, Vanished There

Out of roughly 43 million tracked domains, we logged 62,936 changes in the last 24 hours and about 300,000 brand-new domains. Most of it is routine — nameserver swaps, SPF tweaks — but a few CAA-record stories stood out.

CAA: good hygiene vs. a blind spot

CAA records tell certificate authorities who's allowed to issue TLS certs for a domain, and today showed both ends of the spectrum:

  • clochard.be tightened things up, updating its Let's Encrypt and Google Trust Services CAA entries to require dns-01 validation in addition to http-01 — a small but meaningful hardening move.
  • bitpost.pl landed on Cloudflare and picked up a sprawling CAA policy covering Certum, Comodo, DigiCert, Let's Encrypt, Google, and SSL.com, including cansignhttpexchanges flags — the kind of config you see from someone deliberately locking down issuance.
  • On the flip side, gasbuidltech.com left GitHub Pages for a plain host on AS16509 and, in the process, dropped a full set of DigiCert/Let's Encrypt/Sectigo CAA records (including wildcard entries) — meaning the domain is now, at least for the moment, back to "any CA can issue."
  • Similarly, ahmeddieselservices.tech moved off Vercel's nameservers onto Orderbox DNS and picked up Titan Email, but shed its CAA restrictions on Let's Encrypt, Google, and Sectigo along the way.

CAA isn't the most-watched record type, but losing it during a migration is an easy way to accidentally widen your attack surface.

Cloudflare keeps collecting migrations

Several domains pointed their nameservers at Cloudflare today: arppec.fr (dropping Openprovider NS), justhang.fr (off AS16276), bitpost.pl (away from nazwa.pl), and kunshan0512.com, which went from an untracked network straight to Cloudflare's AS13335. Meanwhile africaimpactinvest.org made a bigger leap — it ditched its old hwshost.com nameservers and Google Workspace MX/SPF setup, briefly stripped mail config, then re-added Google mail via smtp.google.com, all while flipping onto Cloudflare's network (AS22612 → AS13335). Looks like a full infrastructure refresh, not just a CDN front-end swap.

A CDN-to-CDN handoff

replaace.com is a neat edge case: the AS numbers in its routing (AS60068, AS200325, AS212238) stayed identical, but the provider label flipped from BunnyCDN to CDN77 — both services apparently sharing the same underlying network footprint. A reminder that "same ASN" doesn't always mean "same operator" once you're dealing with shared-infrastructure CDNs.

Elsewhere, the usual churn continued: fitribe.app widened its SPF to include Amazon SES while moving off AS47583 to AS16509, and mayfieldcustomhomes.com and tbredcorp.com both jumped from AS31898 to AS46606 within minutes of each other — worth watching if that pattern continues tomorrow.