Infrastructure
Email Infrastructure
The email systems behind a client domain — why connecting them gives Infraova operational context for monitoring and health scoring.
What email infrastructure means
Every domain that sends email has infrastructure behind it — an email service provider, a marketing platform, a transactional sending service, or a cold outreach tool. These platforms are where the sending actually happens. They hold the authentication configuration, the sending history, the deliverability metrics, and the reputation signals that explain why a domain is healthy or unhealthy.
Why connecting email infrastructure matters
DNS monitoring tells you what the records say. Email infrastructure connections tell you what is actually happening with the sending. A domain can have a valid DMARC record in DNS but still have deliverability problems caused by the sending platform. By connecting the email infrastructure behind a domain, Infraova can correlate DNS health with sending health — giving you a more complete picture of what is actually affecting the domain.
What Infraova gets from email connections
The specific data Infraova receives depends on the platform. For email service providers like Klaviyo, HubSpot, or Customer.io, Infraova reads authentication configuration, sending domain status, and deliverability signals. For cold email and sending platforms like Instantly or Smartlead, Infraova also reads sending volume, bounce rates, and reply rates. For Google Postmaster, Infraova reads domain reputation signals directly from Gmail.
Where this data appears
Email infrastructure data appears in the domain health view alongside DNS data. When Infraova detects a problem that is driven by the sending platform — not just the DNS records — it surfaces that context in the issue diagnosis. This means proposals can be more precise: instead of flagging a generic authentication problem, Infraova can identify that the issue is specific to a particular sending platform's configuration.
Email infrastructure vs DNS providers
Email infrastructure connections are primarily for monitoring context, not for remediation. Infraova does not write records or make changes through email platform APIs. The remediation path for email-related problems goes through the DNS provider — fixing the SPF, DKIM, or DMARC record in DNS — informed by the context from the email platform connection.
Note
Email infrastructure connections give Infraova context. DNS provider connections give Infraova the ability to act. Both together give you the most complete operational picture.
Supported platforms
Infraova supports connections to email service providers, marketing platforms, transactional sending services, and cold email tools. Each platform has its own connection method and data set. See the individual platform documentation for connection instructions and what Infraova receives from each.