DMARC Report Inbox Parser

What It Does

Parse DMARC aggregate XML/ZIP reports into clean rows, source summaries, alignment failures, and executive deliverability posture briefs.

This local package is part of the Junipr Apify actors 171-200 premium build for ChatGPT review.

What It Does Not Do

• It does not call live Apify APIs.
• It does not publish, upload Store assets, create public tasks, or configure live PPE.
• It does not claim publish readiness.
• It does not make unbounded network calls in the local fixture path.

Input Fields

Seed shape: domains or URLs, maxDomains, timeoutMs, strictMode, includeSummary

The tiny fixture is available at examples/input.tiny.json and mirrored at fixtures/input.tiny.json for the local runner.

Output Fields

• reportId
• orgName
• domain
• sourceIp
• count
• dkimAligned
• spfAligned
• disposition
• reasonType
• dateRangeStart
• dateRangeEnd

Pricing / PPE Events

Pricing is local configuration only.

• Model: PPE
• Status: LOCAL_CONFIG_ONLY_NOT_LIVE
• Paid output event: report-parsed
• Pass-through usage: OFF by default. Browser, proxy, and high-volume external request modes are not enabled in this local build.

Public Task Examples

Parse DMARC aggregate XML from a mail inbox export

• Search intent: parse dmarc aggregate xml from a mail inbox export
• Specific input: Fixture input shaped for parse dmarc aggregate xml from a mail inbox export.
• Expected output: Dataset rows with reportId, orgName, domain, sourceIp plus local KVS report evidence.
• Why run it: MSPs, IT teams, SecOps, agencies would run this to get a bounded local proof before any live Apify review or production use.

Summarize DMARC failures by source IP

• Search intent: summarize dmarc failures by source ip
• Specific input: Fixture input shaped for summarize dmarc failures by source ip.
• Expected output: Dataset rows with reportId, orgName, domain, sourceIp plus local KVS report evidence.
• Why run it: MSPs, IT teams, SecOps, agencies would run this to get a bounded local proof before any live Apify review or production use.

Audit forwarded-mail DMARC dispositions

• Search intent: audit forwarded-mail dmarc dispositions
• Specific input: Fixture input shaped for audit forwarded-mail dmarc dispositions.
• Expected output: Dataset rows with reportId, orgName, domain, sourceIp plus local KVS report evidence.
• Why run it: MSPs, IT teams, SecOps, agencies would run this to get a bounded local proof before any live Apify review or production use.

Turn vendor DMARC XML into a CSV-ready table

• Search intent: turn vendor dmarc xml into a csv-ready table
• Specific input: Fixture input shaped for turn vendor dmarc xml into a csv-ready table.
• Expected output: Dataset rows with reportId, orgName, domain, sourceIp plus local KVS report evidence.
• Why run it: MSPs, IT teams, SecOps, agencies would run this to get a bounded local proof before any live Apify review or production use.

Check aggregate report coverage for a client domain

• Search intent: check aggregate report coverage for a client domain
• Specific input: Fixture input shaped for check aggregate report coverage for a client domain.
• Expected output: Dataset rows with reportId, orgName, domain, sourceIp plus local KVS report evidence.
• Why run it: MSPs, IT teams, SecOps, agencies would run this to get a bounded local proof before any live Apify review or production use.

Tests

• Actor-specific fixture tests live in test/dmarc-report-inbox-parser.test.ts.
• Node-based local suites validate dataset schema conformance, output samples, local smoke runs, and PPE guard behavior.

FAQ

Is this live on Apify?

No. This is a local package for ChatGPT review only.

Is it publish-ready?

No. It needs later live tiny-run validation and console configuration before any publication decision.