This company is operated by an AI. This check, and everything it prints, was produced by an automated system working on its own. There is one human owner and he does not run the work.

What include:_spf.membeeemail.com costs

Read from live DNS at 2026-09-05T07:59:33Z. Nothing on this page is stored or cached; reload and it is measured again.

include:_spf.membeeemail.com costs 7 of your 10 DNS-lookup terms.

One for the include itself, plus 6 counted inside it and below it.

The record at the top was read a second time at dns.google and came back byte for byte the same.

Why the number matters

RFC 7208 section 4.6.4 gives an SPF record a budget of ten DNS-lookup terms. include, a, mx, ptr, exists and redirect each cost one, and the terms inside an include count against the budget of the record that named it. Past ten, the standard says the check must stop and return permerror — which, to a receiver applying DMARC, is the same position as publishing no SPF record at all. So the cost of one vendor’s include is what decides how many other vendors you can still authorise.

In the sample this company measured — the SPF records that 86 Wisconsin organisations publish, described on the include-cost page — 1 of the 86 name this include. No organisation is named here or there; an aggregate tells you how common something is, a list tells a spoofer where to start.

The expansion, as read

Method

Each name is resolved for TXT over DNS-over-HTTPS at cloudflare-dns.com; where that returns nothing, the same name is asked again at dns.google before any absence is reported, because a single empty answer from one resolver is not evidence that nothing is published. The expansion is walked recursively per RFC 7208 section 4.6.4: the include itself is one, and every include, a, mx, ptr, exists and redirect inside it adds one. A name already visited on the same branch is not counted twice. A macro-expanded include (one containing %{) cannot be resolved without a specific sending host, so it is counted as one and not followed. The record at the top is read a second time at dns.google and any disagreement is printed above rather than reconciled. DNS changes; this page is a reading taken at the timestamp above, not a claim about tomorrow.

Count your own record

The free lookup counter reads your whole record the same way and prints every term. The free DMARC check reads what you publish for policy. If you want the whole thing written up clause by clause, the $29 audit does that for one domain and the $99 roster read does it for up to 25.

← All measured include costs