A good fit when
- You have one custom business-email domain.
- You can name the mailbox, website form, CRM, invoicing and newsletter services that send as it.
- You or your administrator will make the DNS changes from the written plan.
Public DNS check — no login or email required
See what receiving mail systems can verify about your domain.
Check public MX, SPF and DMARC records for one domain. DKIM cannot be reliably checked without knowing your provider's selector, so this tool does not guess.
Need a safe change plan, not another dashboard?
For a one-time $49, we map one domain's public records, review your confirmed sending systems, provide the relevant provider DKIM checklist, draft a staged DMARC record only after sender confirmation, give exact DNS change instructions, and perform one public post-change recheck. One revision is included.
What the finished plan contains
- A sender inventory showing which mail provider, website form, CRM, invoicing tool, or newsletter service must be confirmed before records change.
- A source-cited snapshot of the public MX, SPF and DMARC records we actually found.
- A provider-specific DKIM checklist and a safe order of operations, with copy-ready DNS instructions where the evidence supports them.
- A staged DMARC draft only after the real senders are confirmed, plus a post-change public recheck.
Delivered as an editable plan within two business days after complete intake. This is a one-time purchase, not a subscription.
Preview a fictional plan extract
We do not request DNS credentials, change records, receive DMARC reports, monitor mail, guarantee delivery, certify security, or promise compliance. We will not recommend moving directly to quarantine or reject without evidence from your real senders.
Not the right fit when
- You need us to log in to DNS, change records, or troubleshoot a mail server live.
- You need multiple domains, emergency blocklist work, ongoing monitoring, or inbox-placement guarantees.
- You do not yet know which systems send as the domain.
Who reviews the plan
The free DNS lookup is automated. The paid plan is reviewed and delivered by Good AiDeas LLC using your confirmed sender list and the public evidence cited in the plan.
We confirm the published one-domain scope before work begins, contact you instead of guessing when intake is unclear, and never ask for DNS credentials or mailbox access.
Ask a scope question before checkout
Secure checkout asks only for your receipt email. After payment, the intake asks for the one business domain covered by the plan. No login or DNS access is requested.
Fictional deliverable preview — not a live domain audit
See the structure before you buy.
This abbreviated example uses sample-business.test and invented provider states only to show the plan format. A paid plan uses the buyer's confirmed senders and current public DNS evidence; it never copies these example findings.
1. Sender inventory gate
| System | Status | Before DNS change |
|---|---|---|
| Primary mailbox | Confirmed | Verify provider DKIM selector |
| Website forms | Needs confirmation | Identify sending service |
| CRM / invoicing | Needs confirmation | Confirm whether it sends as this domain |
2. Evidence-to-action map
- MX: record the observed provider and confirm it matches the buyer's mailbox service.
- SPF: map every authorized sender before consolidating or replacing anything.
- DKIM: use the confirmed provider's selector and setup instructions; do not guess.
- DMARC: draft a staged record only after SPF and/or DKIM alignment is understood.
3. Staged change order
- Confirm every real sending system and the person responsible for each one.
- Enable and verify provider-specific DKIM where supported.
- Repair SPF only when the source map shows a concrete issue; keep one valid SPF record.
- Prepare a monitoring-first DMARC draft after alignment is understood.
- Have the buyer publish changes in its own DNS account, then perform the included public recheck.
The real plan includes source links, copy-ready instructions where evidence supports them, open questions, rollback notes, and one revision. Good AiDeas does not log in to DNS and does not promise inbox placement.
Ask a scope question before checkout
Secure checkout asks only for the receipt email. The covered domain is collected after verified payment.
What the current official guidance actually says
Google says SPF and/or DKIM should be established before DMARC. Yahoo urges all senders to publish DMARC, while its stricter combined requirements apply to bulk senders. Microsoft requires SPF, DKIM and DMARC for domains sending more than 5,000 messages per day and describes authentication as beneficial for lower-volume senders too.
Sources: Google Workspace, Yahoo Sender Best Practices, and Microsoft.