Understand the signals.
Make better decisions.
The canonical home for MailMaid’s guides on email marketing automation, technical analysis, and deliverability. Original notes on verification, authentication and sending infrastructure — plus analysers that read your own records the way a receiving server reads them.
Read your records the way a receiver reads them.
All analysersPaste a record or a set of raw headers and get the same verdict a receiving mail server reaches — the lookup count that breaks SPF, the alignment gap that makes DMARC fail while DKIM passes, the hop that held your message for nine minutes. Every check runs in your browser; there is no backend to send it to.
SPF record analyser
Parse an SPF record, count its DNS lookups, and find what will break it.
Open analyser Technical analysisDMARC record analyser
Grade a DMARC record on enforcement, not just syntax.
Open analyser Technical analysisDKIM key analyser
Check a DKIM public key's strength, revocation state, and tags.
Open analyser Technical analysisEmail header analyser
Read authentication, DMARC alignment, and hop-by-hop delays from raw headers.
Open analyser Technical analysisWarm-up schedule planner
Build a day-by-day ramp that respects per-mailbox ceilings.
Open analyserLatest from the Academy
All 24 guidesA practical preflight before a large send
Review the audience, sending path and stop conditions together.
A repeatable list hygiene workflow for agencies
Keep client identity, decisions and report ownership clear.
A suppression list should survive every cleaning pass
A new verification result must not erase a recipient’s choice.
After a DNS change, verify what receivers can see
There is no single propagation timer for every sender and resolver.
Audit SPF without guessing at DNS
Build an inventory before editing the record.
BIMI, MTA-STS and TLS reporting: different layers
A logo record, transport policy and delivery report solve different problems.
The tools behind the guides.
Which tool answers your question?MailMaid’s product suite covers the work these guides describe — verifying an address, cleaning a list, reading the evidence in a delivered message, and watching a domain over time. Availability is stated per product, never implied.
MailMaid Verify™
“Is this address worth sending to?”
Know what an address check really tells you.
Local checks available · live verification needs a configured providerExplore product
MailMaid ListCare™
“What is actually in this list before I send to it?”
A cleaner list. A clearer next send.
Local CSV and XLSX cleaning availableExplore product
MailMaid InboxLens™
“What did the receiver actually conclude about my message?”
Find the evidence behind delivery.
Header analysis available · seed placement testing pendingExplore product
MailMaid DomainGuard™
“What is my domain actually publishing?”
Understand your sending domain.
Account service required for live DNS inspectionExplore product
MailMaid Connect™
“How does this fit the stack I already run?”
Keep email work close to your CRM.
Existing adapters · verification writeback on the roadmapExplore product
MailMaid Academy™
“I just need to understand what is going on.”
Better email decisions start here.
Free · no accountExplore productEvery topic, in depth
All topicsEmail Authentication
SPF, DKIM, DMARC, ARC, and MTA-STS: proving your mail is really from you.
BIMI and VMC Certification
Getting your verified logo into inboxes with BIMI, VMC, and CMC.
Email Deliverability
Sender reputation, warm-up, list hygiene, and inbox placement.
Email Marketing
Strategy, segmentation, copy, and measurement for campaigns that get read.
AI-Powered Automated Outreach
Cold email, personalization at scale, and reply handling with AI agents.
Inbox Management
Triage, labeling, scheduling, and getting to inbox zero without losing anything.
How this blog is written
The answer comes first
Every guide opens with a direct answer in a marked-up box, so search engines and answer engines can quote it and you can stop reading once you have what you came for.
Claims cite the spec
Authentication behaviour is defined in RFCs, not in opinion. Findings in the analysers carry the section that governs them, so you can check the tool rather than trust it.
Nothing you paste is uploaded
Records and headers carry internal hostnames and recipient addresses. The analysers are client-side code on a static site, so that data physically cannot reach a server.
Uncertainty is kept, not smoothed
Where evidence is incomplete the guides say so. A format check is not a mailbox verdict, a published record is not a passing one, and we would rather name the gap than imply a guarantee.