August 12, 2026

Ten domains, one ASN, and SpaceX locks down its cert issuers

Out of the 26,518 changes we clocked in the last 24 hours, one pattern stood out immediately: a cluster of unrelated-looking domains all landing on the same autonomous system within minutes of each other.

The AS16276 pile-up

At least ten domains — www.ladea.co.uk, abr-nc.com, www.desirabledating.com, www.hole11.com, www.fernsbyholdings.com, adabola.net, picknbuildbrazil.com, www.magic360.xyz, www.lexuality.ca, and rest24turkiye.org — all shifted their network to AS16276 within about a 45-minute window. Most came from AS30058, though rest24turkiye.org arrived from AS22612 instead. That last one also had a bigger cleanup: it dropped its registrar-servers.com email-forwarding MX/NS/SPF trio and picked up ns1.lander.d.parity.domains / ns2.lander.d.parity.domains — the fingerprint of a domain being repointed to a landing-page platform. When that many unrelated domains converge on one ASN this fast, it's usually a bulk portfolio move by whoever manages the underlying hosting, not a coincidence.

spacex.ai tightens who can issue its certs

spacex.ai added a fresh set of CAA records: 0 iodef mailto:caa-reports@x.ai, plus explicit issuer authorization for digicert.com, letsencrypt.org, and pki.goog. That's a textbook CAA hardening move — the domain is now telling every CA "don't issue a cert for me unless you're on this list, and email us if someone tries anyway."

azur.se leaves the parking lot

azur.se (and its www twin) swapped ns1.afternic.com / ns2.afternic.com — GoDaddy's aftermarket parking nameservers — for ns1.nameshift.com, ns2.nameshift.com, and 3wtxrx.ns3.nameshift.com. Alongside that it picked up new CAA records (including HTTP-01 validation constraints for Let's Encrypt and Google Trust Services), dropped a v=spf1 -all record, and moved network from AS16509 to AS20473. That combination — new DNS host, new CAA policy, dead SPF — reads like a domain that just changed hands and is being reconfigured by its new owner.

Teleonline's split personality

teleonline.org and www.teleonline.org present an odd mix: they gained Cloudflare's email-routing MX records (route1.mx.cloudflare.net, route2.mx.cloudflare.net, route3.mx.cloudflare.net) and Cloudflare nameservers (chip.ns.cloudflare.com, sharon.ns.cloudflare.com), plus a matching SPF include for _spf.mx.cloudflare.net. Yet the network record moved away from Cloudflare's AS13335 to AS23352, and hosting flipped from Cloudflare (cdn) to unknown. In other words: the site's proxying/CDN left Cloudflare, but its mail just signed up for Cloudflare's email routing — two separate decisions that happened to land in the same DNS diff.

Also worth a glance

rojo.ar quietly stripped its letsencrypt.org CAA authorization and its Google site-verification TXT — the kind of cleanup you'd expect right before a domain goes dark or gets re-platformed.