EasyDMARC incident

DMARC Reporting Issue (EU Region)

Minor Resolved View vendor source →

EasyDMARC experienced a minor incident on June 30, 2026 affecting Reporting, lasting 28m. The incident has been resolved; the full update timeline is below.

Started
Jun 30, 2026, 08:13 AM UTC
Resolved
Jun 30, 2026, 08:42 AM UTC
Duration
28m
Detected by Pingoru
Jun 30, 2026, 08:13 AM UTC

Affected components

Reporting

Update timeline

  1. investigating Jun 30, 2026, 08:03 AM UTC

    We are currently investigating an issue affecting rua.easydmarc.eu and ruf.easydmarc.eu reporting addresses. As a result, these addresses may be flagged as invalid in some DMARC configurations. Our team is actively working on a fix and will provide updates as soon as they are available. We apologize for any inconvenience.

  2. identified Jun 30, 2026, 08:13 AM UTC

    We have identified the root cause of the issue affecting rua.easydmarc.eu and ruf.easydmarc.eu reporting addresses. The issue was caused by an unexpected domain expiration of easydmarc.eu due to a system glitch on our domain registrar's end, which prevented the domain from auto-renewing despite being correctly configured to do so. Our team is actively working with the registrar to restore the domain and resolve the issue. We will provide further updates as soon as a fix is deployed.

  3. monitoring Jun 30, 2026, 08:26 AM UTC

    A fix has been implemented for the issue. The domain has been restored and reporting addresses should now be functioning as expected. We are continuing to monitor the situation to ensure full stability.

  4. monitoring Jun 30, 2026, 08:26 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Jun 30, 2026, 08:42 AM UTC

    This incident has been fully resolved. The rua.easydmarc.eu and ruf.easydmarc.eu reporting addresses are now operational. The root cause was a system glitch on Namecheap's end that prevented the easydmarc.eu domain from auto-renewing, despite auto-renewal being correctly configured. The domain has since been restored and full functionality has been confirmed. We apologize for any inconvenience this may have caused.