Genesys Cloud – DMARC monitoring for custom email domains in Genesys Cloud
| Announced on (YYYY-MM-DD) | Effective date (YYYY-MM-DD) | Aha! idea |
|---|---|---|
| 2026-01-05 | - | Aha! idea |
In a future release, Genesys Cloud will introduce domain-based message authentication, reporting, and conformance (DMARC) monitoring for all custom domains that use the Genesys Cloud email delivery service. Email providers such as Microsoft, Google, and Yahoo continue to strengthen authentication requirements, and this Genesys Cloud capability allows administrators to assess whether their domains are configured with DMARC and whether the detected DMARC record is valid.
DMARC monitoring identifies missing or invalid DMARC records before these gaps result in delivery issues or impact sender reputation. This release provides visibility only and does not change outbound email handling.
- Customers must implement and manage their own DMARC, SPF, and DKIM records within their DNS environment.
- SPF and DKIM are required for DMARC.
- DMARC statuses for Custom SMTP and Microsoft Graph domains appear for awareness only. Authentication enforcement for these domains occurs within the customer’s mail environment.
- DMARC will be mandatory when Genesys Cloud introduces DMARC enforcement for all outbound email.
Monitoring focus
Monitoring applies to these interactions:
- ACD email
- Transactional messages
- Campaign-based and agentless outbound email
Feature updates
The DMARC monitoring for custom email domains in Genesys Cloud introduces the following enhancements:
DMARC status detection
Genesys Cloud checks DNS for each custom domain and displays whether a DMARC record is:
- Valid (green) – record detected
- Invalid (red) – invalid DMARC record
- Not present (gray) – no DMARC record found
Centralized monitoring location
Administrators can view DMARC status in Admin > Email > Domains > [domain] for ACD and transactional messages.
Global availability
DMARC monitoring is available in all Genesys Cloud regions and applies to outbound email sent through the Genesys Cloud email delivery service.
Why this matters
- Email authentication visibility – administrators can see whether outbound email domains meet baseline authentication expectations.
- Deliverability awareness – monitoring highlights potential risks before messages are routed to spam or rejected.
- Preparation for future requirements – visibility into current DMARC posture supports readiness for future authentication alignment.
Customer action
Customers should confirm that a DMARC record exists for each outbound email domain. If no DMARC record is present, customers can publish the following policy: v=DMARC1; p=none
Setup guides and DNS examples will be available in the Genesys Cloud Resource Center and linked from within the product interface.
[NEXT] Was this article helpful?
Get user feedback about articles.