- Shipped
- September 28, 2026 at 6:11 PM UTC
- Author
- Kamo
- Commit
- aadfc46
SPF: kamouniverse.com publishes the same record as spf.kamocrm.com (v=spf1 ip4:47.181.8.84 mx -all), so a customer who wrote include:kamouniverse.com has already authorized the relay. The equivalents list only knew kamocrm.com, so the DNS page told that customer to add a mechanism they already had, and the spf_verified sweep scored them unauthorized (sending them from the platform address). The default is now kamocrm.com,kamouniverse.com: add-only, the legacy include still counts. The recommended include stays spf.kamocrm.com, which is the one that exists. Aliases: kamocrm, kamocrm-com and kamouniverse-com join kamouniverse in OrgAliasPolicy.RESERVED. public/kamocrm-com/ still holds the platform's original branding, so an org aliased that would have written its logo over it. No organization holds any of the four today. The logout cookie test gains kamouniverse.com hosts (no code change: the Domain is the host's own last two labels, so each apex clears itself).