evansvillechamber.org
Everything on this page was computed while you loaded it — at 2026-09-05 08:04:09 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.
No SPF record is published
Nothing beginning v=spf1 is published at evansvillechamber.org, so there is no evaluation budget to count. A receiver applying SPF to this domain gets the result "none".
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.
| Level | Name | Cloudflare | Agree | |
|---|---|---|---|---|
| 0 | evansvillechamber.org | — none published — | — none published — | yes |
| — | _dmarc.evansvillechamber.org | — none published — | — none published — | yes |
DNS queries made to produce this page: 4.
What your DMARC record asks receivers to do
Nothing beginning v=DMARC1 is published at _dmarc.evansvillechamber.org. With no DMARC record, a receiver has no published instruction from you about mail that fails authentication, and no reports are sent to you.
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