SPF & DMARC Record Lint
Runs the same checker as our npm package on a Node.js runtime that pip installs for you (
nodejs-wheel-binaries) - no system Node.js needed. Your files are checked locally.
19 offline checks on the SPF, DMARC and DKIM records in your branch — including the DMARC rewrite of May 2026
Install
spf-dmarc-record-lint file
Node 18+. The same 19 rules as the VS Code extension, from a terminal or CI.
Free
- Checks the file you have open — every v=spf1, v=DMARC1 and v=DKIM1 string in it, against all 19 rules, with the RFC section and the fix on the exact line. Nothing limited, timed or watermarked.
--ruleslists every rule
With a licence ($29 once)
- Sweeps every *.zone, *.tf, *.yaml and *.txt in the whole workspace in one pass and writes one dated Markdown audit report you keep — the file you attach to the change ticket as evidence that the policy was enforced on that date.
spf-dmarc-record-lint --dir ./templates --report html --out report.html
A freelance email-deliverability specialist bills $50-$150 an hour, and the first hour goes on reading the records you already have.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "spf-dmarc-record-lint": { "command": "spf-dmarc-record-lint", "args": ["--mcp"] } } }
Tools: check_text and check_file (free) · check_dir (licence). The agent gets every finding with the line number.
Use in CI
- name: SPF & DMARC Record Lint
run: pip install rulestamp-spf-dmarc-record-lint && spf-dmarc-record-lint --dir . --ci
The folder sweep, reports and CI mode need one licence — one payment, no subscription. Set READYSTACK_LICENSE=<key> or run --license <key> once.
Install (PyPI)
pip install rulestamp-spf-dmarc-record-lint
spf-dmarc-record-lint --help
Metadata
Release files for rulestamp-spf-dmarc-record-lint 1.1.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rulestamp_spf_dmarc_record_lint-1.1.7.tar.gz | 17.5 kB | Without provenance | Details for rulestamp_spf_dmarc_record_lint-1.1.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rulestamp_spf_dmarc_record_lint-1.1.7-py3-none-any.whl | Python 3 | none | any | Details for rulestamp_spf_dmarc_record_lint-1.1.7-py3-none-any.whl |
Total release size: 37.1 kB
Release files / rulestamp_spf_dmarc_record_lint-1.1.7.tar.gz
| Download URL | rulestamp_spf_dmarc_record_lint-1.1.7.tar.gz |
|---|---|
| Size | 17.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
be24d90b310e590ff51b500f0d4b885c1575df36434d9ee6a03d228d0fd7c2c3
|
|
BLAKE2b-256 checksum How to use checksums |
192fa18afaa6c2b2e989c753f333e035a9d4847fb576d4a02154ce313ff94c6f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / rulestamp_spf_dmarc_record_lint-1.1.7-py3-none-any.whl
| Download URL | rulestamp_spf_dmarc_record_lint-1.1.7-py3-none-any.whl |
|---|---|
| Size | 19.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a83dce1773ae5b251e25035fb54f4a39e78fcf0c8374cd96a61540e25d32cc27
|
|
BLAKE2b-256 checksum How to use checksums |
616f91a4a22681c5ced0e45606e32dc95e3a74796f3665726b4819ac481df4d2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for rulestamp-spf-dmarc-record-lint 1.1.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.