Skip to main content

Valimail Monitor

Enable Valimail Monitor in DigiCert®​​ DNS to identify email services sending email on behalf of your organization and monitor DMARC compliance. Enable the integration at the account level, then enable it for the primary zones you want to monitor.

Before you begin, confirm that you have permission to manage integrations in DigiCert®​​ DNS. The primary zones you want to monitor must already exist. Review their existing DMARC configuration, including regional overrides, exclusions, and delegations, before enabling the integration.

Valimail Monitor integration controls

Use the account-level and zone-level controls to manage where Valimail Monitor is enabled.

Control

Purpose

Integrate Valimail Monitor on the Integrations page

Enable or disable the integration for the account

Enable Valimail Monitor on a primary zone’s Settings tab

Enable or disable monitoring for that zone

Enabling the account-level integration makes it available for individual zones. Disabling it stops monitoring through the integration for associated zones and removes the reporting addresses added by the integration. Unmodified records created by Valimail Monitor are deleted; customer-added settings and reporting addresses are preserved.

Disabling Valimail Monitor for an individual zone leaves the account-level integration enabled.

Enable Valimail Monitor

To enable the account-level integration:

  1. Open Integrations.

  2. Turn on Integrate Valimail Monitor.

  3. Confirm that the Valimail Monitor enabled message appears.

  4. Enable Valimail Monitor for each primary zone you want to monitor.

Disable Valimail Monitor

Disabling the account-level integration stops monitoring through the integration for associated zones. Before proceeding, review how those zones’ DMARC configurations will be managed afterward.

  1. Open Integrations.

  2. Turn off Integrate Valimail Monitor.

  3. Review the Disable Valimail Monitor dialog.

  4. Select Disable.

  5. Confirm that the Valimail Monitor disabled message appears.

  6. Review the affected zones’ Records tabs, including regional overrides, to verify the resulting DMARC configuration.

For each affected zone, the integration removes the Valimail reporting addresses it added. A Valimail-created record that has never been changed is deleted entirely. Customer-added content, including reporting addresses added manually, is retained.

Enable Valimail Monitor for a zone

After the account-level integration is enabled:

  1. Go to DNS > Zones and select Primary zones.

  2. Open the zone.

  3. Review its existing _dmarc records. If regional views are enabled, also review regional overrides, exclusions, and NS or CNAME delegations.

  4. Select Settings.

  5. Turn on Enable Valimail Monitor.

  6. Open the Records tab and review the DMARC policy and reporting destination in the global record and any regional overrides.

  7. Finalize your setup in Valimail.

If no global _dmarc record exists, the integration creates a TXT record with the standard Valimail value. If a global DMARC TXT record already exists, the integration adds the Valimail aggregate-reporting address to its rua setting and preserves your other settings.

For zones with regional views, the additional rules below apply.

Valimail Monitor and regional views

Enabling Valimail Monitor updates DMARC reporting across the zone’s global and regional records.

Existing configuration

Result when enabling Valimail Monitor

No global _dmarc record

Creates a global DMARC TXT record with the standard Valimail value

Existing global DMARC TXT record

Adds the Valimail reporting address and preserves other settings

Regional _dmarc TXT override

Adds the Valimail reporting address to each override and preserves other settings

Global _dmarc record excluded from a region

Preserves the exclusion; that region does not report through the excluded global record

Regional NS or CNAME delegation at _dmarc, without a global exclusion for that region

Rejects enablement and identifies the conflicting region

Delegation at _dmarc pointing to Valimail in any region, including an excluded region

Rejects enablement

A regional exclusion does not prevent the integration from being enabled for the zone. However, a region with no applicable DMARC TXT record does not report to Valimail.

If enablement fails, review the region named in the error and resolve the conflicting _dmarc configuration before trying again. For a regional delegation to another provider, the global _dmarc record must be excluded from that region. A delegation pointing to Valimail prevents enablement even when the region is excluded.

For configuration instructions, see Regional views.

Disable Valimail Monitor for a zone

Disabling Valimail Monitor removes the reporting addresses added by the integration from the zone’s global and regional DMARC records. Before proceeding, determine how the zone’s DMARC configuration will be managed afterward.

  1. Go to DNS > Zones and select Primary zones.

  2. Open the zone.

  3. Select Settings.

  4. Turn off Enable Valimail Monitor.

  5. Review the Disable Valimail Monitor dialog and confirm that it identifies the intended zone.

  6. Select Disable.

  7. Confirm that the Valimail Monitor disabled message appears.

  8. Open the Records tab and review the global DMARC record and any regional overrides.

When disabled:

  • Valimail reporting addresses are removed, including those added manually

  • Valimail-created records that have never been changed are deleted entirely

  • Customer-added DMARC records and their other settings are preserved

  • The same preservation rules apply to regional overrides

Because manually added reporting addresses remain, review the resulting records rather than assuming that every Valimail reporting destination has been removed.

Disabling Valimail Monitor for an individual zone leaves the account-level integration enabled. To disable it for the account, turn off Integrate Valimail Monitor on the Integrations page.

Review and manage DMARC records

Valimail Monitor uses the rua setting in a DMARC TXT record to receive aggregate email authentication reports.

To review the record:

  1. Open the zone’s Records tab.

  2. In Grouped view, expand TXT (Text).

  3. Locate the _dmarc record. For a zone named example.com, the complete record name is _dmarc.example.com.

  4. Review Contains to see the DMARC policy and reporting destinations.

  5. If regional views are enabled, review the corresponding regional records and exclusions.

The regional _dmarc view displays the Valimail banner. When editing a record, the message explains that the Valimail reporting address is required and that you must disable Valimail Monitor to remove or change it.

While Valimail Monitor is enabled, you can:

  • Change the DMARC policy or TTL while retaining the required Valimail reporting address

  • Add a regional DMARC TXT override with a different policy and the required Valimail reporting address

  • Delete a regional override to return to the global record, provided the region is not excluded

  • Exclude the global _dmarc record from a region

The following changes are rejected:

  • Creating or editing a global or regional DMARC TXT record without the required Valimail reporting address

  • Adding more than one value to a DMARC TXT record set

  • Deleting the global DMARC record

To remove or change the required Valimail reporting address, disable Valimail Monitor for the zone first.

For DMARC syntax and TXT record management, see TXT records.

DMARC conflicts and validation

Each region can have only one applicable _dmarc record type: TXT, NS, or CNAME. Validation includes the global record unless it is excluded from that region.

These rules apply to changes made through the UI and API, as well as zone restores and zone file uploads.

Zone file uploads add records to the global configuration. An upload is rejected if it:

  • Conflicts with an _dmarc delegation in any region

  • Contains duplicate _dmarc records

  • Removes the required Valimail reporting address

Bulk enablement, zone copying, zone restoration, and conversion from secondary to primary follow the same applicable rules. If bulk enablement fails because of a regional conflict, the report identifies the region that caused the failure.

See Import DNS records and DNS snapshots for the related procedures.