Back to blog
Threat Intel
Phishing Forensics

Reconnaissance and the DMARC RUA Pipeline: When Telemetry Becomes Target

DMARC aggregate reports provide critical visibility into email authentication, but left unprotected, this exact telemetry becomes a comprehensive map for supply chain attacks.

MailSleuth Research
Email Security Team
October 28, 20268 min read
Illustration of a glowing structural blueprint being extracted through a data pipeline.

Security teams deploy visibility tools under the assumption that more data always leads to better defensive posture. We instrument our endpoints, aggregate our logs, and instruct the internet at large to send us daily digests of our domain activity. But telemetry is inherently neutral. A map of your infrastructure does not care who is reading it. When dealing with email authentication protocols, this reality often goes unacknowledged until a sophisticated adversary exploits it.

The DMARC protocol relies heavily on its reporting mechanism to give domain owners insight into their mail streams. By publishing a TXT record with an RUA tag, an organization asks major receivers like Google, Microsoft, and Yahoo to send them XML files detailing every IP address that attempted to send mail on their behalf. This data is mandatory for safely shifting a domain to a strict reject policy. You need to know which legitimate systems are failing SPF or DKIM checks before you tell the internet to drop their messages.

But consider the nature of that data from an offensive perspective. An aggregate report is a continuously updated, highly accurate inventory of an organization's entire external communication footprint. It reveals sanctioned marketing tools, forgotten legacy servers, and unauthorized shadow IT. We must examine how attackers conceptualize this information, the theoretical mechanics of intercepting it, and the architecture required to treat this telemetry with the operational security it demands.

The Objective: Moving Beyond Perimeter Enumeration

Active reconnaissance is a noisy endeavor. When an attacker scans external subnets or attempts to enumerate active directory infrastructure, they generate localized anomalies. Modern detection engineering is built around catching exactly these types of behavioral spikes. Firewalls drop the packets, EDR agents flag the anomalous queries, and the security operations center is alerted to the probing activity long before initial access is achieved.

Email protocol telemetry flips this dynamic entirely. The reconnaissance is performed passively on the attacker's behalf by the largest technology companies in the world. The target organization never sees a single malicious packet hit their perimeter during the discovery phase. Instead, the attacker focuses on acquiring the diagnostic outputs generated by legitimate mail transfer agents.

The Anatomy of the Aggregate Report

To understand the value of this data, we have to look at the structure of the RUA XML schema defined in RFC 7489. These reports do not contain message bodies or subject lines, which often leads to a false sense of security regarding their sensitivity. However, they contain exact source IP addresses, the domains found in the Header From, the specific DKIM domains that signed the message, and the domains evaluated during the SPF check.

This provides a complete vendor risk profile. If an organization uses an external invoicing platform, a customer relationship management tool, and a bulk mailing service, the IP spaces and authentication alignment status for all of those platforms are detailed in the daily digest. The attacker no longer has to guess which supply chain partners the target relies on. The target's own infrastructure has thoughtfully compiled a list.

The Redirection Mirage and Protocol Verification

A common theoretical attack vector discussed in red team circles involves attempting to trigger RUA reports directly to an attacker-controlled mailbox. The hypothesis suggests that by spoofing the target domain and sending thousands of messages to large receivers, an attacker can force those receivers to generate aggregate reports. The critical flaw in this specific attack path is a misunderstanding of how report routing actually functions.

When a receiving mail transfer agent evaluates a message claiming to be from a specific domain, it fetches the DMARC TXT record for that domain. If an attacker sends a spoofed message pretending to be the target, the receiver pulls the target's policy. The RUA tag within that legitimate policy dictates exactly where the report will be sent. The attacker cannot dynamically inject their own email address into the transaction. The report goes to the target's configured ingestion point, not the attacker's inbox.

The External Destination Safeguard

What if the attacker attempts a more complex maneuver, such as identifying a misconfigured third-party reporting service used by the target, and attempting to hijack that destination? The architects of the DMARC protocol anticipated the risk of weaponized reporting and implemented a strict security control known as External Destination Verification.

If the domain portion of the URI address does not match the domain of the DMARC record, the Report Receiver MUST perform a DNS query to verify that the destination domain authorizes the receipt of reports. — RFC 7489, Section 7.1

This mechanism explicitly prevents a domain from arbitrary report routing. If the target domain asks for reports to be sent to a completely different domain, the receiving MTA will pause. It performs a specific DNS lookup on the destination domain looking for an authorization record. If the destination domain has not explicitly authorized the target domain to send it reports, the report is dropped. Therefore, turning the reporting mechanism into a direct reconnaissance tool requires the attacker to compromise the target's DNS infrastructure or breach the mailbox where the reports are legitimately delivered.

Parsing the XML Goldmine for Infrastructure Mapping

Because the protocol itself defends against arbitrary redirection, attackers shift their focus to the ingestion pipeline. Many organizations make the critical error of routing their RUA telemetry to an unmonitored shared IT mailbox. If an attacker gains initial access through a low-level credential compromise or a session token theft, discovering an inbox overflowing with unparsed XML attachments is a massive windfall.

Extracting Vendor Alignments

Once the raw data is acquired, the extraction process is trivial to script. The attacker parses the XML tree, iterating through each record block to map the row data against the authentication results. They are looking for specific patterns in the telemetry that indicate systemic configuration choices.

The first pattern is fully aligned third-party senders. An attacker will filter the data for source IPs belonging to major cloud providers that consistently pass both SPF and DKIM alignment. This immediately identifies the organization's core operational vendors. If the reports show high volume from a specific human resources SaaS platform passing alignment, the attacker knows exactly which external service the employees trust for internal communications.

The second pattern is shadow IT and configuration drift. Attackers look for internal IP ranges or obscure marketing vendors that consistently fail DMARC alignment but are still permitted to deliver mail because the domain policy is set to none. These softfail scenarios are highly valuable. Employees are already conditioned to seeing slightly anomalous headers or delayed delivery from these systems, making them perfect candidates for impersonation.

Pivot Plays: From Telemetry to Business Email Compromise

The intelligence gathered from the reporting pipeline rarely results in a direct technical exploit against a mail server. Instead, it acts as the foundation for highly targeted, context-aware business email compromise. Generic phishing campaigns fail because they lack the specific operational context of the target's daily workflow. Telemetry extraction provides that exact context.

Weaponizing the Vendor Relationship

Armed with the knowledge of exactly which vendors the target relies on, the attacker moves to infrastructure procurement. They register a lookalike domain that visually mimics the legitimate vendor discovered in the XML data. Because the attacker controls this new infrastructure entirely, they can implement perfect email authentication. They publish a flawless SPF record, set up cryptographic signing for DKIM, and immediately publish a strict DMARC reject policy for the lookalike domain.

When the attacker eventually sends the phishing payload, usually disguised as an urgent billing update or a mandatory platform migration, the message easily bypasses the target's secure email gateway. The gateway evaluates the lookalike domain, sees perfect cryptographic alignment, and scores the message favorably. The human recipient, who legitimately interacts with that specific vendor every week, is highly likely to engage with the payload. The success of the attack was entirely predicated on knowing exactly which vendor to impersonate.

Defensive Architecture for Telemetry Pipelines

The solution to this exposure is not to disable aggregate reporting. Visibility is an absolute requirement for modern email security administration. Without the continuous feedback loop provided by the receivers, maintaining a strict reject policy across a complex enterprise environment is impossible. Legitimate mail will inevitably break due to forwarders altering body hashes or misconfigured SPF macros, and security teams need the data to remediate those failures.

Instead, organizations must fundamentally change how they handle this data. DMARC telemetry must be classified and treated as sensitive security logging, subject to the exact same access controls and retention policies as firewall logs or identity provider audit trails.

The primary defensive control is decoupling ingestion from standard user infrastructure. Aggregate reports should never be routed to a standard Exchange or Google Workspace mailbox accessible by tier-one support staff. The risk of lateral movement exposing the entire vendor map is too high. Ingestion endpoints must be segregated and hardened.

Furthermore, security teams must actively monitor their external DNS configurations for unauthorized modifications. A silent, unauthorized alteration to the TXT record housing the reporting URI is a critical severity event. It indicates that an adversary has bypassed DNS provider access controls and is attempting to redirect the telemetry stream to an external endpoint they control.

The takeaway

Security architecture requires us to anticipate how our own operational requirements might be weaponized against us. We build pipelines to gather data so we can defend our perimeters, but the pipelines themselves expand our attack surface. Protecting an organization means recognizing that the maps of our infrastructure are just as valuable to an adversary as the infrastructure itself.

This is why purpose-built platforms are necessary for handling protocol telemetry. Using a dedicated platform like MailSleuth.AI ensures that aggregate reports are ingested securely, parsed in isolated environments, and presented through dashboards protected by strict role-based access controls. By securing the pipeline, security engineers can maintain the visibility required to enforce strict authentication policies without accidentally handing their adversaries the keys to the supply chain.

#email-forensics#dmarc#reconnaissance#defensive-architecture#threat-intel
MailSleuth Research
Email Security Team

We dissect phishing campaigns and email infrastructure so you don't have to.