Audit SPF DKIM DMARC DNS for Domains (Google DNS) + Telegram Alerts

Monitor SPF, DKIM, and DMARC DNS health—with Telegram alerts when something changes

This n8n workflow audits your domains’ SPF, DKIM, DMARC, and MX DNS records using Google Public DNS over HTTPS, compares results to the previous run, and sends you a Telegram alert only when problems appear or records change.

What this workflow does

• Runs daily at 8:00 or you can trigger it on-demand with a manual test.
• Reads a comma-separated domain list (optionally including DKIM selectors after a colon), for example: example.com, mycompany.com:google|selector1.
• Builds DNS queries for:
  • MX
  • SPF (TXT records)
  • DMARC (TXT record)
  • DKIM selectors (TXT records per selector)
• Resolves each record via Google DNS over HTTPS (dns.google/resolve), retries failed requests, and treats unresolved lookups as unknown rather than “missing.”
• Flags issues like missing/unsafe SPF, missing or weak DMARC, missing/revoked DKIM selectors, and missing MX.
• Compares current results with the last scheduled run to produce a change-only report (new issues, fixed issues, and edited record values). Manual runs produce a full report.
• Sends the compiled alert message to Telegram.

Use cases

• SaaS operators ensuring email authentication (SPF/DKIM/DMARC) stays compliant and prevents deliverability regressions.
• Automation engineers quickly detecting DNS misconfigurations after deployments or domain/DNS provider changes.
• Teams monitoring DKIM selector changes to confirm keys are present for all expected senders.

Technical details

• n8n nodes/tools used: if, set, code, telegram, sticky note, http request
• DNS resolution: Google Public DNS over HTTPS (dns.google/resolve)
• Alerting: Telegram bot (Telegram credential + target chat ID)