The SPF card had no proxy route, so it never reached the API

Ya: 4 Septemba 2026, 17:56 UTC
Mwandishi: kamo
Ahadi ya: c2dd2c6

The card shipped calling /api/security/domains/{id}/spf, and every request 404'd at Next.js before SecurityService ever saw it — which the card reported as "We couldn't read your domain's email settings", the same message it shows for a genuine DNS failure, so it looked like a lookup problem rather than a missing route. There is no catch-all under /api/security/domains/{id}/: verify-dns, ssl and aliases each have their own route file, and I added the endpoint without adding the fourth. This mirrors verify-dns exactly.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila moja ya hizi updates ardhi katika nafasi yako ya kazi moja kwa moja. Kuanza bure na kuangalia kukua wiki baada ya wiki.

Kuwa Huru Milele Mtazamo wa bei