Skip to content
SpoofKiller
SPF monitoring

Your SPF record has a budget of ten. Do you know the balance?

SPF allows 10 DNS lookups per check. Your providers spend them on your behalf and do not send a statement. SpoofKiller recounts every 6 hours and tells you before the eleventh one bounces your mail.

Expands every include and counts lookups the way receivers do.

example.com / spf

DNS lookups

7 / 10

3 to spare
  • v=spf1
  • └ include:_spf.mail-host.example+1
  • └ include:_netblocks.mail-host.example+1
  • └ include:_netblocks2.mail-host.example+1
  • └ include:send.newsletter.example+1
  • └ include:pool.newsletter.example+1
  • └ a:mail.example.com+1
  • └ mx+1
  • └ ip4:192.0.2.0/24no lookup
  • └ ~all
Illustrative example: sample values, not customer data.
A stack of DNS records drawn as layered cards.TXT _dmarcv=DMARC1; p=rejectUNCHANGEDTXT @v=spf1 include:… -allUNCHANGEDTXT s1._domainkeyv=DKIM1; k=rsa; p=MIIB…UNCHANGEDMX @10 mx.example.netCHANGED$ scheduled check complete ▌
The problem

A record you wrote, made mostly of records you did not.

An SPF record is a single line of DNS that lists who may send mail for your domain. It looks simple. It is also a line that other companies can, in effect, rewrite after you publish it.

Here is how. You do not list your mail host's servers by address; you write include: and the name of a record they maintain. That record includes others. Each hop costs one DNS lookup, and SPF permits exactly 10 for the whole evaluation. Go over and the result is a permanent error. Receivers treat that as a failure for every message, including the genuine ones.

Nobody goes over on purpose. Somebody adds a help-desk tool. A provider splits one include into three. The record that passed in March fails in October, and the first notice is a customer asking why the invoice went to spam. The classic failures are all catalogued in Common SPF Errors; the common thread is that none of them announces itself.

v=spf1 include:_spf.mail-host.example include:send.newsletter.example a:mail.example.com mx ip4:192.0.2.0/24 ~all

An example record. Four of its terms cost lookups directly; the includes cost more once expanded. The ip4 term costs none.

What SpoofKiller checks

The same arithmetic a receiving server does, on a timer.

Each check below corresponds to a rule in RFC 7208, not to a house opinion.

  • Recursive lookup count

    include, a, mx, ptr, exists, and redirect each cost a lookup, at every depth. You get the total, a warning as you approach 10, and an error past it.

  • Multiple SPF records

    Two TXT records starting v=spf1 is a permanent error, however correct each one is alone. It is the most common result of two people each being helpful.

  • Include loops

    A includes B, B includes A. The walk detects the cycle and reports where it closes instead of running until the limit.

  • +all and other open doors

    +all authorizes the entire internet. A record with no all term, or with ?all, is flagged too, along with address ranges broad enough to be suspicious.

  • Deprecated ptr

    The ptr mechanism is slow, unreliable, and discouraged by the RFC itself. Some receivers ignore it. If it is in your record, you are told.

  • Void lookups

    Lookups that return no records at all are capped at two per evaluation. A stale include pointing at a service you left years ago is the usual cause.

Also flagged: syntax errors, malformed ip4 and ip6 values, includes that do not resolve, terms placed after all (which are ignored), a redirect that is ignored because all is present, and records long enough to cause trouble.

How it works

Fetch, walk, count, compare.

  1. 01

    Fetch the record

    Every 6 hours SpoofKiller queries the TXT records at your domain and picks out anything beginning v=spf1. Two such records is already an error.

  2. 02

    Walk every branch

    Each include and redirect is followed, and each of those is followed in turn, the way a receiving server would. Loops are caught instead of chased.

  3. 03

    Count what the receiver counts

    Every mechanism that costs a DNS query is tallied against the limit of 10. Lookups that return nothing are tallied separately as void lookups.

  4. 04

    Compare and report

    The result is compared with the last scan. New errors raise a finding, cleared errors resolve it, and an edited record is logged with its before and after.

A failed lookup is not a deleted record

If the DNS query itself fails, the scan records the result as unknown and raises nothing. You should not be woken because a resolver had a bad minute.
What you see

The whole tree, with a price on every branch.

The SPF view shows the record as receivers resolve it: each include indented under its parent, each lookup marked where it is spent. The expensive branch is obvious at a glance, which is most of the diagnosis.

Findings come with a fix in plain words. When the record changes, the before and after are kept, so the question “who edited SPF, and when?” has an answer. And because SPF alone does not satisfy DMARC unless it aligns with your From domain, the same dashboard shows SPF alignment from your actual reports, by sender, under DMARC monitoring.

A hand pressing a rubber stamp onto an envelope against an orange starburst.
Ten stamps per letter. The clerk does not make exceptions.
Honest limits

What SPF monitoring will not do.

  • It checks on a schedule

    Scans run every 6 hours. A record broken at noon may not be flagged until the next scan. This is monitoring on a timer, not a live wire.

  • It never edits your DNS

    You make every change, at your DNS provider. The SPF record generator will write the record; publishing it is yours to do.

  • SPF cannot protect the From address by itself

    SPF checks the envelope sender, which the reader never sees. Only DMARC ties it to the visible From. See SPF vs DKIM vs DMARC.

  • SPF breaks on forwarding, and always will

    A forwarded message arrives from the forwarder's server, which is not in your record. No monitor fixes that. It is the reason DKIM exists.

Try it before you buy it

Count your lookups now. It takes one field.

The free SPF checker runs the same recursive walk as the monitor, once, against live DNS. If the number comes back as 9 or 10, you have found a reason to want it run again without being asked.

Free. No account. The lookup runs against live DNS.

Free, no obligation

Record over the limit? Send it to us.

Tell us the domain. We will expand the SPF record, find the expensive branch, and write back with a version that fits.

  • A person reads every message
  • No sales sequence, no list rental
  • Reply within one business day

We use your details to reply. Nothing else.

FAQ

Questions about SPF monitoring

Straight answers. If yours is not here, ask us and a person will reply.

Ask a question

Stop finding out from the bounce message.

Add a domain and SpoofKiller recounts its SPF lookups every 6 hours. The first domain is free.