September 22, 2026
CAA Records Vanish, a Shop Ditches Its Platform, and Crypto Meets Cloudflare
Out of roughly 29 million tracked domains, we logged 58,363 DNS changes in the last 24 hours, plus about 520,000 freshly seen domains. Most of it is routine housekeeping — but a few changes tell real stories.
A platform exit: jadelya.ma
jadelya.ma and www.jadelya.ma pulled every trace of the youcan.shop e-commerce platform in one shot: the NS records (ns1.youcan.shop, ns2.youcan.shop), the MX records (mta1/mta2.youcan.shop), the SOA, and a long CAA policy that had been locking certificate issuance down to a specific list of CAs (amazon.com, digicert.com, letsencrypt.org, sectigo.com, and friends). That's not a tweak — that's a full migration off the hosted-storefront platform, with nothing yet standing in its place at the time of capture.
Iran-to-Iran, but a different host: redikashop.com
redikashop.com moved off limoodns.com nameservers onto cape.parspack.net / cloud.parspack.net, with its ASN shifting from AS60976 to AS202269 and mail switching to mail.redikashop.com. Along the way it also shed a pile of old TXT verification records (Google, Pinterest, Yandex) — the kind of cleanup that usually happens when a site gets rebuilt from scratch rather than just re-pointed.
Also worth a mention: wirtualnemedia.pl (and its www) hopped from AS31080 to AS12827 — a straightforward hosting-network move for the Polish media outlet.
Onto Cloudflare, awkwardly
thorncryptotrade.com swapped its anitahost.com nameservers for Cloudflare's (aaden.ns.cloudflare.com, alexa.ns.cloudflare.com), moving from AS29802 to Cloudflare's AS13335 and flipping its hosting classification to Cloudflare CDN. The SPF record came along for the ride too — except all the spaces got stripped out in transit, turning v=spf1 ip4:... ~all into one unbroken string. Functionally that record may no longer parse as valid SPF, which is a good reminder to double-check TXT records after a DNS cutover.
CAA records quietly disappearing
Two separate domains, xenia188.com and sentris.com, each dropped a CAA record that had restricted certificate issuance to letsencrypt.org. Removing a CAA record doesn't tighten security — it loosens it, since no CAA means any CA can now issue for that name. sentris.com also shifted networks (AS19194 → AS3491/AS31713) at the same time, suggesting a host change knocked the CAA config loose.
Contrast that with theo-psy.fr, which kept its CAA protections for digicert.com and pki.goog but stripped the cansignhttpexchanges=yes flag — a smaller, more deliberate tightening. And www.azhoboe.org went the other direction entirely, standing up a brand-new CAA record plus MX and NS pointed at r4l.com, the signature of a site coming online for the first time.