Skip to main content
This guide connects a domain to JetEmail DMARC Monitoring without changing how its existing DMARC policy handles mail.

​
Before you begin

You need:
  • Access to DMARC in the JetEmail dashboard
  • Permission to edit the domain’s DNS
  • The domain you want to monitor, without a protocol or path
  • The current DMARC record, if one already exists
Publish only one DMARC TXT record at _dmarc.your-domain. Multiple DMARC records make the policy invalid. If a record already exists, edit it instead of creating another one.

​
1. Add the domain

  1. In the dashboard, go to DMARC → Domains
  2. Click Add domain
  3. Enter the parent domain, such as example.com
  4. Click Add domain
Enter only the domain. Do not include https://, an email address, a port, a path, or _dmarc.. JetEmail creates a unique address similar to:
Add the parent domain when possible. Its registration accepts reports for that domain and its subdomains when they use the same reporting address.

​
2. Open the setup instructions

Find the new domain in the table and click Setup. The modal shows:
  • The TXT record host
  • A complete starter DMARC value
  • The domain’s unique mailto: RUA destination
The next step depends on whether the domain already has a DMARC record.

​
3. Update DNS

​
The domain has no DMARC record

Publish the complete record shown by JetEmail. It will look like this: Some DNS providers automatically append the domain name. If yours does, enter only _dmarc in the host field so it does not create _dmarc.example.com.example.com.

​
The domain already has a DMARC record

Keep the existing policy and all of its tags. Add the JetEmail destination to its rua= tag. For example, change:
to:
If the record does not have a rua tag, add one:
Do not replace an existing p=quarantine or p=reject policy with the generated p=none starter value. Adding JetEmail to rua does not require changing the policy.
JetEmail handles the external-report authorization required for addresses at rua.jetsmtp.net; you do not need to add another authorization record under the JetEmail domain.

​
4. Verify the reporting address

After publishing the record:
  1. Return to DMARC → Domains
  2. Click Check DNS for the pending domain
  3. Wait for the status to change from Pending DNS to Verified
The check looks up _dmarc.example.com and confirms that the domain’s assigned JetEmail address appears in the rua tag. It does not require the policy to be p=none. DNS changes can take time to propagate. If verification fails immediately after an update, wait for the record’s TTL and try again.

​
5. Wait for the first report

Reports are generated by participating receivers after they process mail using your domain. They normally arrive once per day, but the first data can take 24–48 hours after the DNS change and qualifying mail traffic. Go to DMARC → Reports to see authentication volume, sending sources, dispositions, and individual receiver reports.

Domains and DNS

Learn about subdomains, multiple report destinations, and policy rollout.

No reports yet?

Check DNS, report timing, and common configuration mistakes.