Tripline

Is your email landing in spam, or could someone fake it?

We read your domain's public records and explain any problem in plain English.

Free, with no sign-up. Takes a few seconds.

What we look at

SPFv=spf1 include:mail.example +all

SPF

Which servers may send your mail. We flag a missing record, more than one record, a record that allows anyone, and one needing more than the 10 lookups receivers allow.

DMARCv=DMARC1; p=none

DMARC

What receivers should do with fake mail. We flag a missing record, and a policy that only watches.

DKIMselector1._domainkey

DKIM

Whether a signing key appears under common names. Keys can use any name, so not finding one doesn't prove it's missing.

MX10 mx1.mail.example

Mail servers

Whether your domain can receive mail and, if you ask us to watch, whether its mail servers change.

Common questions

What does "too many DNS lookups" mean for SPF?

Receivers follow at most 10 lookups when reading your record. Over that, SPF fails even for your real mail. Each include can use several, so adding one tool can tip you over.

Is p=none enough for DMARC?

It's the right place to start, because it changes nothing and lets you collect reports. It doesn't stop fake mail, so move to quarantine and then reject once your real mail passes.

Why would my SPF break if I changed nothing?

Your record usually includes your providers' records, and they can change theirs at any time. That can push you past the limit without any change on your side.

Does this tell me whether my email will arrive?

Not on its own. These records show how your domain is set up, while your sender reputation and the content of your mail also affect delivery.