Infraova, continuously improving.

Approved remediations now execute through connected DNS providers.

Connecting a DNS provider used to mean importing domains. Now it means giving Infraova the access required to act. When a proposed DNS change is approved, Infraova executes it directly through the connected provider — Cloudflare, Vercel, GoDaddy, Namecheap, Porkbun, DigitalOcean, Route 53, or Squarespace — without the operator having to open a separate tool, find the record, and make the change manually.

Post-remediation verification — every approved change is checked against live infrastructure.

Executing a change and confirming the change are two different things. After an approved remediation runs, Infraova queries the live DNS record and checks whether the expected state was actually reached. If verification passes, the operation is recorded as complete. If not, it's flagged for attention. Execution no longer marks the end of the workflow.

The approval boundary — no infrastructure change executes without a human decision.

Infraova can prepare a remediation: identify the issue, determine what changed, understand the impact, and propose the correct action. But Infraova waits. The operator reviews the proposal and explicitly approves or rejects it before anything is executed. The boundary between preparation and execution is deliberate and enforced — not a setting that can be switched off.

Infrastructure events now reach your team through email and Slack.

When Infraova detects something important or a proposal is waiting for review, the right people need to know — without having to watch a dashboard. Email and Slack notifications carry the operational event: what happened, how serious it is, which client and domain are affected, and a direct link back into Infraova where the decision is waiting. The notification is a bridge, not the interface. The review and approval still happen inside Infraova.

Email infrastructure integrations — sending context added to domain health.

A domain's DNS records tell one part of the story. The sending platforms actually generating email from that domain tell another. Infraova now connects to 14 email infrastructure platforms — including Klaviyo, HubSpot, Customer.io, Omnisend, Braze, Marketo, Instantly, Smartlead, SendGrid, Mailgun, Postmark, Amazon SES, SparkPost, and Google Postmaster — so the authentication, reputation, and delivery signals from the sending layer can be understood alongside the infrastructure underneath.

Client portal — clients can now see the infrastructure being managed for them.

The agency's operational workflow stays inside Infraova. But clients can now access a shared portal that shows them the health of the infrastructure being managed on their behalf — domain status, important issues, and operational history — without taking over the underlying workflow. The agency operates. The client has visibility.

White-label PDF reports — agency branding, client-ready delivery.

Infraova generates PDF reports that agencies can deliver directly to clients under their own branding. The report covers 8 sections: executive summary, issues and actions, infrastructure analysis, check details, advanced intelligence, security intelligence, a client-facing summary, and a month-over-month score comparison. Agency logo replaces Infraova branding when configured.

Audit log — important operational activity is now traceable.

Every important operation leaves a record: what was detected, what was proposed, who approved it, when it executed, what was verified, and what the result was. Provider connections, team changes, and billing events are also captured. The audit log exists so agencies can understand what happened and demonstrate it to clients when needed.

Public API — domain health accessible to your own systems.

Infraova doesn't have to be the only place where infrastructure health is visible. The API gives your own systems — internal dashboards, client portals, reporting workflows, automations — programmatic access to the health state Infraova maintains. Authenticated with an API key. Queries domain portfolio, health scores, check results, and client relationships.

DNS remediation proposals — dynamic recommendations from live check results.

Infraova began generating specific remediation proposals from live DNS check data. Each proposal reflects the actual current state of the record and the recommended corrected state — not a generic template. The operator sees what is wrong, what should replace it, what the impact is, and what action Infraova is recommending before deciding whether to approve.

Prioritization — issues organized by severity and client impact, not chronology.

A list of infrastructure warnings is only useful if the operator knows which one matters most. Infraova started organizing detected issues by severity and operational impact so the team's attention lands on the infrastructure that actually needs it — not just the most recent alert or the longest list.

Continuous domain monitoring — 30 checks per domain, running automatically.

Infraova started as a monitoring product. The job was to watch client domains continuously and surface problems before they became visible to clients or started affecting deliverability. That meant checking SPF, DKIM, DMARC, MX records, blacklist status, SSL certificates, DNS configuration, domain expiry, and other email and domain infrastructure signals — automatically, across every domain in the portfolio, without requiring someone to audit each one manually.

The check coverage has grown from the original set to 30 monitors per domain (25 infrastructure checks plus spoofing detection, Gmail reputation, domain expiry, DNS change history, and sending platform metrics), now including DNSSEC, CAA, DANE, MTA-STS, TLS-RPT, BIMI, and others alongside the original email infrastructure signals.

DNS provider connections — import domains from 8 providers including Cloudflare, Vercel, and Route 53.

Connect the DNS providers your clients already use and Infraova imports the domains automatically. Cloudflare, GoDaddy, Namecheap, Porkbun, DigitalOcean, Vercel, Amazon Route 53, and Squarespace are all supported. Cold email tools Instantly and Smartlead can also be connected to import sending domains. CSV import is available for any domains not managed through a connected provider.

Infrastructure context — domain health, sending signals, and reputation in one place.

A domain's health isn't just its DNS records. Infraova expanded from raw check results into a fuller picture of each domain: what infrastructure is involved, what sending platforms are connected, what the reputation signals look like, and how everything fits together. The goal was to help operators understand not just that something was wrong, but what was actually affected and how serious it was.