Who is allowed to send mail as you
v=spf1 a mx ip4:67.225.137.176 include:sendgrid.net include:support.zendesk.com include:spf.mail.intercom.io include:stspg-customer.com include:_spf.google.com ?all
Your SPF record doesn't end with an enforcement mechanism. Unauthorized senders won't be challenged.
Cryptographic signature on every send
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnJfGzGBtb+IWnp4qLPMdD75nJ37yQaVF6SltbAIqSlUbpfrJROi4O0GMmVVmJ4Zm1TlqGzn0cKDyqbeKzJ7B973Sc3GMpdCRouFD3jr258a6xmg6SpyTrrGcZFQ5WoSuLtVwuO/VNk68sQLKvKse61Qntb6eLak08QeZMk4qYqRvjMHABTe0Ln7oPACWBhDLvxdl3Czegp7AWS9IkB4zg/eNrc0utjA2LfBUl8g1OKP1DnxPak+G/XaT9tqnWUH7baL8pOQwJSMzUd4dxClbOeTSXjf0Eg4l/P11mHyDhKVZTlSBbyIY2tk3Y0oyBqEHJDtfyueTStYcZiBGAStXkQIDAQAB
What receivers do when SPF or DKIM fail
v=DMARC1; p=none; pct=100; rua=mailto:re+qv9rjnupoda@dmarc.postmarkapp.com; sp=none; aspf=r;
Your DMARC policy is "p=none" — monitor-only mode. Inbox providers still respect your SPF/DKIM passes, but failed mail isn't quarantined or rejected. This is fine for the first 2 weeks of a new domain, but you should tighten it once your real sends are clean.
Where your inbound mail is delivered
aspmx.l.google.com, aspmx2.googlemail.com, aspmx3.googlemail.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com
Want this fixed at the source?
FrostSender ships with deliverability monitoring built in. Get on the list and we’ll let you know the moment we open access.