burlingtonchamber.com

Everything on this page was computed while you loaded it — at 2026-09-05 08:02:25 UTC — by reading public DNS through two independent resolvers, Cloudflare and Google, and requiring their answers to agree. No answer above was taken from a previous reading and no mailbox was touched. Reload it and the work is done again. We do keep one line saying this page was loaded and which domain was asked about — a count, so we can tell whether anyone reads what we send. It holds no address, no identifier, no cookie and nothing that could single you out.

Inside the limit, with little room

8 of the 10 permitted terms are used. This passes today and has 2 to spare.

The count

8 of 10

2 are terms written in your own record. 6 are performed inside records published and edited by other companies, reached through your includes. That second number is the one you cannot fix by editing your own DNS.

The derivation, one line per term, in the order a receiver performs them

Terms counted are the ones the specification counts: include, a, mx, ptr, exists and the redirect modifier. all, ip4, ip6 and exp cause no DNS query at evaluation time and are not counted.

What this number is, exactly. It is the whole tree, which is the worst case. A receiver evaluates left to right and stops at the first term that matches, so a record above ten does not fail for every sender — it fails for every sender whose evaluation has to walk past the tenth term. A record at or under ten cannot fail this way at all.

Both resolvers, verbatim, name by name

The left column is what Cloudflare’s resolver returned; the right is Google’s. Only SPF records are shown — the other TXT records a domain publishes are none of our business and are filtered out before the two answers are compared.

DNS queries made to produce this page: 20.

What your DMARC record asks receivers to do

v=DMARC1; p=quarantine; rua=mailto:dmarc@joeapps.ca; ruf=mailto:dmarc@joeapps.ca; fo=1; pct=1

Your p tag asks receivers to treat failing mail as suspicious.

The clauses this page counted under, word for word

RFC 7208 section 4.6.4: “SPF implementations MUST limit the total number of those terms to 10 during SPF evaluation, to avoid unreasonable load on the DNS. If this limit is exceeded, the implementation MUST return ‘permerror’.”

RFC 7208 section 4.5: “If the resultant record set includes more than one record, check_host() produces the ‘permerror’ result.”

RFC 7208 section 7: macros are expanded per message from the client IP address, the sender and the HELO identity — which is why a term containing %{ is counted here and not followed.

What this page did not measure

It did not read your mail and could not. It says nothing about whether your mail is being delivered, whether anyone has forged your domain, or whether the addresses inside your record are the right ones. It reads what your domain publishes, counts the terms the published specification counts, and quotes the clause it counted them under.

What we sell, plainly

Two things, both fixed price, both delivered by email, both produced by the same reader that wrote this page.

$29 — a full written audit of one domain: every check, the standards clause each one evaluates, the exact strings read, and the change we would make. Order the $29 audit

$99 — the same read across up to 25 domains, one row each, for a firm that carries other organisations’ domains as well as its own. Order the $99 roster read

Either is emailed within one business day or refunded in full without you asking. You owe us nothing for this page: the reading, the records and the clauses are yours to keep and to check whether or not you ever buy anything.

Read another domain · The free lookup counter · The free record check · What else we do