lattice.com
BMostly OK

1 issue hurting your inbox placement. Details below.

SPF
Fail

Who is allowed to send mail as you

v=spf1 a mx include:_u.lattice.com._spf.smart.ondmarc.com include:mailgun.org ~all

Your SPF record doesn't authorize Google to send mail. Even though FrostSender connects via Gmail, your SPF check will fail — recipients will treat your mail as suspicious.

DKIM
Pass

Cryptographic signature on every send

v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEApqjXkDJ4ViJmOs8H8MS4lbtTqUIIm144pvR8aPlkvMyXZ7HAQq7t0Ka0466ajrl9osOwBI8PiizCuy+FXppNK+2juF+mxq6fW9g96vYCHahDxatuplDO2rhwFFHoMYkfgRiSGjwNtoJbxtgOxZIQ1LKzlGJquMvFMecjbXfntQ7QO9dsJWTLCsXPMr41jBfrI37HY32M/+YjqFQjYLTaBoOoak47DO+BeEoHys7ldHI9XR0/5g1DV2BhLLcTwYkRB15KGYE5PPp8KoDbDayEi80KRCJBklFtTgpVWa8miErbTXTmrqQfJeeXHZBLHtfGIi43MwTKGYYr7vuRX2wQYwIDAQAB

DMARC
Pass

What receivers do when SPF or DKIM fail

v=DMARC1; p=reject; pct=100; fo=1; ri=3600; rua=mailto:31a91356@inbox.ondmarc.com; ruf=mailto:31a91356@inbox.ondmarc.com;

MX
Pass

Where your inbound mail is delivered

aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.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.

beta v1.0