Case study · Notion
Notion publicly documented its shift to multi-region DKIM with SendGrid and Google Workspace. They rotated selectors gradually and published a short postmortem detailing lessons learned.
Read the post →Coordinate selectors, rotations, and alignment policies across hybrid email stacks without losing deliverability visibility.
Use this blueprint when onboarding new regions or providers. Add it to your runbooks so every team member follows a consistent approach.
Quick reference across the platforms most teams deploy. Each row links to the official guide.
Supports up to 5 active selectors per domain. Use Google Admin API to rotate programmatically.
Each custom domain gets two CNAME selectors (`selector1`, `selector2`). Rotate by switching endpoints.
Assign a dedicated IP pool per region and map selectors via the branded link interface.
Generate per-stream DKIM keys; align bounce domains to maintain DMARC compliance.
Notion publicly documented its shift to multi-region DKIM with SendGrid and Google Workspace. They rotated selectors gradually and published a short postmortem detailing lessons learned.
Read the post →Add your transactional subdomains to SendCheck's watchlist. If the selector drifts or alignment breaks, we alert owners via Slack so they can rotate keys before customers notice.
Automate selector rotations with SendCheck APIs
Trigger DKIM rotations via CI/CD when new keys are generated and automatically verify alignment before deployment.