For your provider
SPF, DKIM, and DMARC DNS values Mailchimp, HubSpot, Klaviyo, Shopify, Resend, SparkPost, Google, Microsoft, SES, and other ESPs publish in vendor docs.
Vendor-published DNS values only. Examples: Google `include:_spf.google.com`, Microsoft `include:spf.protection.outlook.com`, SES `include:amazonses.com`, Mailgun `include:mailgun.org`, SendGrid `include:sendgrid.net`. Postmark uses a Return-Path CNAME to `pm.mtasv.net`; HubSpot adds `include:shared.hubspot.com` to one SPF TXT.
Marketing ESPs (Mailchimp, Klaviyo, Shopify, and others) usually lead with DKIM CNAMEs and DMARC; transactional APIs (Resend, SparkPost) show per-domain tables in their docs. RFC 7208 allows one `v=spf1` record per name — merge includes, do not add a second TXT.
Google WorkspaceGoogle's SPF example for mail that Google sends is v=spf1 include:_spf.google.com ~all. Any other sender has to be added to that same record. Microsoft 365Microsoft's SPF example for a custom domain is v=spf1 include:spf.protection.outlook.com -all. DKIM keys are CNAMEs from the Defender portal. Amazon SESAmazon SES uses a subdomain of amazonses.com as the default MAIL FROM. A custom MAIL FROM needs v=spf1 include:amazonses.com ~all and exactly one MX. MailgunMailgun's domain-verification table publishes v=spf1 include:mailgun.org ~all. The same table lists MX mxa.mailgun.org and mxb.mailgun.org for receiving. Twilio SendGridTwilio SendGrid's typical SPF example is v=spf1 include:sendgrid.net -all. Two v=spf1 records on one name are a permerror under RFC 7208, April 2014. PostmarkPostmark says you no longer have to include Postmark in your own SPF record. Mail through Postmark passes SPF on Postmark's Return-Path by default.