- Shipped
- September 4, 2026 at 5:56 PM UTC
- Author
- kamo
- Commit
- 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.