Infobip announced on July 9, 2026 that it had acquired SocketLabs, a Pennsylvania-based email infrastructure company that processes more than 1.2 billion messages a month for over 2,000 businesses. On its face this is a routine piece of martech consolidation news. Underneath it is a reminder of a problem almost every growing company runs into without noticing: the more email service providers a business strings together, the more places its DMARC alignment can quietly break.
The Problem SocketLabs Was Built to Solve
SocketLabs spent nearly two decades building what it calls vendor-agnostic email observability: a layer that sits across SendGrid, Mailgun, SparkPost, and other providers at once, showing what actually lands in the inbox rather than just what left the sending server, and letting a company migrate between providers without a blind, all-at-once cutover. Infobip CEO Silvio Kutić described the acquired team as having “spent years in solving the problems that keep enterprises locked into vendors they’ve outgrown, giving visibility across email providers, showing what actually reaches inboxes, and enabling safe, low-risk migration.” SocketLabs CEO Tim Moore called joining Infobip “the natural next step in a journey we started nearly 20 years ago.”
Why Enterprises End Up With So Many Providers in the First Place
Nobody plans a five-vendor email stack. It accumulates. A marketing team picks one ESP for campaigns. A product team wires up a second for transactional receipts. A support tool ships its own notification emails through a third. A growth team spins up a fourth for a specific send-time or deliverability advantage, and nobody retires the first three. Each addition is a reasonable decision made in isolation, and each one adds a sending source that has to be authenticated correctly for the parent domain to stay protected, not just functional.
Where DMARC Alignment Actually Breaks
DMARC does not care how many providers send mail on a domain’s behalf. It cares that every one of them passes SPF or DKIM and that the result aligns with the domain in the visible From header. In practice, alignment breaks at the exact moments a multi-provider stack grows or changes: a new ESP goes live and nobody adds its include mechanism to the SPF record before it hits ten lookups and starts failing silently for everyone. A DKIM selector gets rotated on one provider and the DNS record update lags behind the cutover. A vendor gets deprecated but its SPF include is never removed, leaving a stale, unmonitored authorization sitting in the domain’s DNS indefinitely. None of this shows up as an outage. It shows up months later as a spike in DMARC failure reports, or worse, as a phishing email that passed authentication because an old, forgotten sending path was still technically authorized.
Consolidation Helps, But Only the Layer It Actually Touches
Folding SocketLabs’ cross-provider visibility into Infobip’s platform, including the company’s existing Email Deliverability Agent, should make it easier for a joint customer to see inbox placement and reputation across every provider from one dashboard. That is a real improvement for the deliverability half of the problem. It does not, by itself, guarantee that every sending source is correctly declared in SPF, correctly signing with DKIM, or aligned under the domain’s DMARC policy. Deliverability visibility answers “did it reach the inbox.” DMARC enforcement answers a different question: “was this domain’s identity actually protected while it got there.” A business can have excellent visibility into inbox placement across five providers and still be running p=none, watching spoofed mail sail through the same pipes its own legitimate traffic uses.
What to Do Regardless of Which Platforms You Use
Inventory every sending source before you consolidate anything. Marketing platforms, transactional mailers, support tools, billing systems, and any service that emails on the domain’s behalf all need to appear somewhere, ideally in one list your security team actually owns.
Read DMARC aggregate reports as a source of truth, not a compliance checkbox. They are the only reliable way to discover a sending source nobody remembers authorizing, because DMARC reports every source that claims the domain, authorized or not.
Treat vendor migrations, consolidations, and offboarding as DMARC events, not just billing events. Retiring a provider without pulling its SPF include and DKIM selector leaves an authenticated door open long after anyone is using it.
Move toward enforcement, not just monitoring. Visibility tools, whether built in-house or acquired, make it easier to see what is happening. They do not replace the step of actually setting policy to quarantine or reject once every legitimate source is confirmed.
The Takeaway
Email infrastructure consolidation is a genuinely good trend for enterprises tired of stitching together disconnected sending platforms. But visibility across providers and authentication of those providers are two different jobs, and a deal like this one only ever solves the first. The DMARC record still has to be built, checked, and enforced by the domain owner, one sending source at a time, no matter how many of those sources end up owned by the same parent company.
Excello Mail gives you one clear view of every sending source authorized on your domain and keeps your SPF, DKIM, and DMARC records aligned as your vendor stack grows or changes. Sign up for free to Excello Mail and get full visibility into who is really sending on your behalf.