Guides
Practical playbooks for keeping email infrastructure healthy.
Step-by-step guides for teams managing domains, DNS, authentication, deliverability, and infrastructure changes — whether you're managing your own business or infrastructure for clients.
Featured playbook
How to investigate a broken SPF record
SPF failures are one of the most common causes of deliverability problems. This guide walks through how to find the failure, understand its impact on sending, determine the right fix, and confirm the result in live infrastructure.
Audience
Getting Started
3 guidesHow to onboard your first domain
Add a domain to Infraova, run the initial health scan, and understand what the results mean.
How to connect a DNS provider
Connect Cloudflare, GoDaddy, Namecheap, or another supported provider to enable automated remediation.
How to start monitoring infrastructure
Set up continuous monitoring across a domain portfolio and configure alert thresholds.
Diagnose
6 guidesHow to investigate a broken SPF record
Identify the failure, understand its sending impact, determine the appropriate fix, and verify the result.
How to diagnose a DKIM failure
Trace a DKIM failure from the DNS record to the signing configuration and identify the root cause.
How to investigate DMARC problems
Understand DMARC alignment failures, policy issues, and their impact on email deliverability.
How to handle unexpected DNS changes
Identify what changed, when it changed, who may have changed it, and what the operational impact is.
How to investigate SSL problems
Diagnose SSL certificate issues, expiry warnings, and misconfigurations across a domain portfolio.
How to investigate reputation problems
Identify blacklist listings, reputation signals, and their impact on client email deliverability.
Remediation
5 guidesHow to review a proposed DNS change
Understand what Infraova has proposed, why it was proposed, and what to check before approving.
How to approve an infrastructure change
Walk through the approval workflow — what the proposal contains, how to authorize it, and what happens next.
How to understand approved remediation
Read an executed remediation — what changed, where it changed, and how to confirm it is correct.
How to verify a DNS change
Confirm that a DNS change is live in the infrastructure and matches the expected state.
How to handle failed remediation
Diagnose a remediation that did not produce the expected result and determine the appropriate next step.
Operations at Scale
4 guidesHow to manage many domains
Organize a large domain portfolio, prioritize monitoring coverage, and maintain consistency across clients.
How to prioritize infrastructure problems
Use severity tiers to decide which detected issues deserve immediate attention and which can wait.
How to build a proactive monitoring process
Move from reactive fire-fighting to a structured process where problems are caught before clients notice.
How to create a repeatable infrastructure workflow
Standardize the detect → propose → approve → remediate → verify loop across every client in the portfolio.
Email & Deliverability
5 guidesHow to audit email authentication
Review SPF, DKIM, and DMARC configuration across a domain and identify authentication gaps.
How to monitor sending domains
Keep sending domain infrastructure healthy — authentication, reputation, and DNS — continuously.
How to investigate bounce-rate changes
Connect a bounce rate increase to the underlying infrastructure change that caused it.
How to understand Google Postmaster signals
Read Gmail reputation and authentication signals and connect them to DNS infrastructure state.
How to connect sending platforms
Associate Klaviyo, SendGrid, Postmark, or another platform with monitored domains to add sending context.
Reporting & Communication
4 guidesHow to explain infrastructure problems to clients
Communicate what happened, what it means for the client's email operation, and what is being done about it.
How to report domain health
Generate a domain health report and communicate the current infrastructure state to a client or stakeholder.
How to create monthly infrastructure reports
Build a recurring reporting process covering detected issues, completed remediations, and health trends.
How to communicate remediation outcomes
Document what was proposed, approved, executed, and verified — and present it in a form clients can understand.
Turn the playbook into an operating system
Learn the process. Let Infraova run it.
The guides teach you how to solve infrastructure problems. Infraova continuously monitors, prioritizes, proposes, remediates approved changes, and verifies the result — so the process runs without someone manually driving it.