September 11, 2026

BP's CAA flip-flop and a Capital One vanity CNAME

Out of roughly 24.7 million tracked domains, who.is logged 35,408 changes and 353,539 brand-new domains in the last 24 hours. Most of it is routine — SPF tweaks, nameserver swaps — but a few changes are worth a closer look.

Capital One quietly claims a card domain

afscmecard.com picked up a new CNAME pointing to vanity-url-redirects.9d37d877e8.capitalonegslbex.com, added a batch of Akamai nameservers (a1-219.akam.net, a18-66.akam.net, etc.) plus ns1.capitalone.com through ns6.capitalone.com, and dropped its old CAA record (which had listed domainmgr@capitalone.com as the iodef contact) along with its v=spf1 -all TXT. Reads like a card-partner site being folded onto Capital One's own GSLB/Akamai infrastructure rather than run separately.

BP's CAA policy, moving in opposite directions

Two BP-adjacent domains did completely different things with the same CAA block (the one with iodef mailto:certificateservices@bp.com and a long allow-list of CAs — comodoca.com, digicert.com, letsencrypt.org, pki.goog, ssl.com). bp-austria.com removed that exact CAA set while flipping its hosting classification from unknown to direct. bpamerica.org added it. Same policy, same company family, opposite move — a nice reminder that CAA hygiene often gets handled domain-by-domain rather than centrally.

A CNAME that says "blocked"

www.tcgfinder.com swapped its Vercel CNAME (1069b71fa80a7160.vercel-dns-017.com) for blocked.transip.nl, dropped its CAA records for globalsign.com, letsencrypt.org, pki.goog and sectigo.com, and moved networks from AS16509 to AS20857. That combination — losing your CDN CNAME to a registrar's "blocked" placeholder — is the classic fingerprint of a domain getting suspended at the registrar level.

Cloudflare's revolving door

baboonhosting.com moved onto Cloudflare (AS214970 → AS13335), picking up a full CAA suite (digicert.com, letsencrypt.org, pki.goog, ssl.com, comodoca.com) plus a Google site-verification TXT — looks like a fresh onboarding. Meanwhile miyaggd.com did the reverse: it left Cloudflare entirely (AS13335 → AS34619), dropping its ivan.ns.cloudflare.com/sasha.ns.cloudflare.com nameservers, its Hostinger MX records, and its SPF record. Between the two, it's the same infrastructure, opposite directions — one site standing up, one winding down.

Small oddity worth a mention

yutim.rs was today's chattiest domain, flipping through 3 separate changes in the window — nothing dramatic in the details, but a good example of a domain that just can't sit still.