MX and mailbox path
Identify the active mailbox provider, forwarding behavior, inbound routing, and any stale services still receiving mail.
Business email and DNS
Untangle email delivery and domain records before another guess makes it worse.
Business email depends on several providers agreeing about routing, identity, and ownership. We document the current setup, identify conflicting or missing records, and plan changes around the services that must stay working.
Common signalMail bounces, goes to spam, or routes unpredictably
Business impactMissed conversations and fragile domain ownership
First useful stepInventory providers and authoritative DNS records
What may be happening
One domain can carry several services with different requirements.
Mailboxes, website hosting, newsletters, transactional messages, form notifications, and tracking systems may all publish records under the same domain. A copied setup guide can introduce a second SPF record, point MX records at the wrong provider, or replace a record another service still needs.
The diagnostic separates symptoms from configuration. A single rejected message, a forwarding loop, and a domain-wide authentication issue require different corrections.
Signals worth checking
- Messages bounce or arrive only for some recipients
- Valid mail regularly lands in spam
- SPF, DKIM, or DMARC reports show failures
- Several providers claim they need the same DNS record
- A migration left old MX, forwarding, or verification entries
- Registrar, DNS, and mailbox ownership are unclear
Diagnostic scope
Map identity, routing, and responsibility before editing records.
DNS is shared infrastructure. The review identifies dependencies and proposes the smallest responsible change rather than replacing records blindly.
SPF, DKIM, and DMARC
Review published records, alignment, sending sources, selector ownership, and obvious syntax or duplication problems.
Domain and DNS control
Document the registrar, authoritative DNS, active integrations, and a safer change sequence with rollback considerations.
A dependable outcome
Know which provider owns each part of the mail path.
The practical result is a coherent configuration, an understandable record of active services, and a safer way to make future changes.
- Current provider and DNS dependency map
- Conflicting or stale record findings
- Corrected records within approved scope
- Validation from authoritative public DNS
- Change notes and rollback context
Pricing
Start with the domain and one observable mail problem.
The $99 Tech Diagnostic reviews the current configuration and recommends a safe fix path. Direct DNS or mail corrections are scoped separately when provider access, dependencies, and risk are clear.
Frequently asked questions
Business email and DNS questions.
Can DNS changes interrupt working email?
Yes. Incorrect or conflicting changes can affect mail routing and other domain services. Current records, providers, and dependencies should be documented before any live change is approved.
Does SPF, DKIM, and DMARC guarantee inbox delivery?
No. Authentication supports trustworthy delivery, but recipient filtering also considers content, reputation, behavior, and mailbox-provider policies. The work focuses on correct configuration and observable issues, not inbox guarantees.
Can you help after a website or email provider change?
Yes. Provider changes often leave stale records, conflicting forwarding, or unclear ownership. A diagnostic can map the current setup and identify what belongs to each active service.
Should I send mailbox passwords in the intake form?
No. Do not submit passwords, recovery codes, API keys, or registrar credentials through the public form. Safe access can be arranged separately if approved work requires it.
Related problems
When email is only one part of the failure.
Lead notifications and account recovery often depend on the same domain configuration.
Make the records understandable
Bring order to business email and DNS.
Tell us which domain and providers are involved, what changed, and what senders or recipients are affected. Do not include credentials.