EasyDMARC
Configure the EasyDMARC integration with RAD Security to ingest DMARC domain posture, aggregate (RUA) reports, and failure (RUF) reports.
This guide walks you through integrating EasyDMARC with RAD Security to ingest your DMARC posture and email-authentication telemetry for external attack-surface and email-security analysis.
EasyDMARC is an email-authentication (DMARC/SPF/DKIM) platform. RAD Security connects to the EasyDMARC API and pulls your monitored domains and DMARC reports on a scheduled basis. It complements the registration/DNS providers in Domain Security (CSC Global, DNS Made Easy) by adding deep DMARC reporting on top of domain posture.
Read-only integration: RAD Security only reads data from EasyDMARC. It never creates, modifies, or deletes domains, DNS records, or reports in your account.
Prerequisites
Before you begin, ensure you have:
- An EasyDMARC account with API access enabled (the Public API is plan-gated and may require enabling by EasyDMARC)
- Ability to generate a Client ID and Secret Key for API access
- Your EasyDMARC Organization ID (format
org_...), from the EasyDMARC admin console / organization URL - Access to a RAD Security workspace with integration permissions
API access is plan-gated: EasyDMARC's API is available on paid tiers and may need to be enabled for your account. If API access is not enabled, the integration cannot connect — enable Public API / API access in EasyDMARC first.
Understanding Integration Components
Step 1: Generate API Credentials in EasyDMARC
Sign in to EasyDMARC
Log in to your EasyDMARC account with an administrator.
Enable and open API access
Navigate to the API access section of your account settings. If API access is not available, follow the prompt to enable it (this may require a plan with API access or contacting EasyDMARC).
Generate Client ID and Secret Key
Generate your Client ID and Secret Key.
Copy the Secret Key immediately and store it securely in a password manager or secrets vault. You will need both values to configure the integration.
Note your Organization ID
Find your Organization ID (format org_...) in the EasyDMARC admin console or your organization URL. Every domain and report query is scoped to it, so the integration cannot connect without it.
Exact account navigation and labels may vary. See the EasyDMARC developer documentation for the current steps to enable API access and generate credentials.
Configure in RAD Security
Navigate to your RAD Security workspace and configure the EasyDMARC integration with the following parameters:
Required Parameters
| Parameter | Description |
|---|---|
| Client ID | EasyDMARC API Client ID |
| Secret Key | EasyDMARC API Secret Key, used to mint short-lived API tokens |
| Organization ID | EasyDMARC Organization ID (format org_...). All domain and report queries are scoped to it. |
Optional Parameters
| Parameter | Description |
|---|---|
| Ingest failure reports (RUF) | Also ingest forensic failure reports. These carry message-level PII (sender, recipient, subject); RAD hashes addresses and redacts subjects before storage. Boolean; default off. |
RAD Security handles token exchange and refresh automatically — you provide the Client ID, Secret Key, and Organization ID.
Verify Integration
Check Connection Status
- Navigate to Data Sources > Integrations > Domain Security in RAD Security
- Locate your EasyDMARC integration
- Verify the connection status shows as Connected
Your EasyDMARC integration is now configured! RAD Security will ingest your DMARC domain posture and aggregate reports on a scheduled basis (and failure reports if you enabled them).
What Data is Synced
On first connection RAD backfills recent DMARC reports, then syncs incrementally (only new reports each cycle), bounded by your EasyDMARC plan's report retention. Domain posture is refreshed each cycle.
Use Cases
Email Authentication Posture Track DMARC/SPF/DKIM coverage and enforcement policy across your domains.
Spoofing & Abuse Detection Surface unauthenticated senders and spoofing attempts from aggregate reports.
Enforcement Rollout Monitor progress toward p=quarantine/reject without breaking legitimate mail.
Attack Surface Analysis Combine DMARC posture with domain and DNS data for a fuller external view.
EasyDMARC focuses on email authentication. Pair it with CSC Global and DNS Made Easy for registration, TLS, and operational DNS coverage.
Troubleshooting
Security Best Practices
Use a Service Account Generate API credentials under a dedicated account rather than a personal login.
Rotate Credentials Regenerate the Client ID and Secret Key periodically according to your security policy.
Secure Storage Store the Secret Key in a secrets vault. Never commit it to version control.
Treat RUF as Sensitive Enable failure-report (RUF) ingestion only when needed; RAD hashes addresses and redacts subjects, but RUF is inherently more sensitive than RUA.
Additional Resources
EasyDMARC Developer Docs
Official EasyDMARC API documentation
Domain Security Overview
Learn about RAD's domain security integrations