Skip to main content
Each monitored domain has its own JetEmail aggregate reporting address. JetEmail accepts reports for the registered domain and covered subdomains, then associates them with the account and regional log location captured when the domain was added.

​
Domain status

Verification confirms the RUA destination is present. It does not test whether every sender passes DMARC or whether every mailbox provider will send reports.

​
Parent domains and subdomains

Registering example.com covers:
  • example.com
  • mail.example.com
  • news.example.com
  • Deeper names such as transactional.mail.example.com
It does not cover a lookalike such as notexample.com, and registering mail.example.com does not cover its parent or sibling domains. Subdomains normally inherit the parent DMARC record. The parent’s sp tag controls the subdomain policy when present; otherwise the p policy applies.
If a subdomain publishes its own DMARC record, it stops inheriting the parent’s RUA destination. Add the same generated JetEmail address to the subdomain record if you still want its reports included under the parent registration.
You do not need to register every subdomain separately when they report to the parent domain’s assigned address.

​
Use more than one report destination

The rua tag can contain multiple comma-separated mailto: destinations. This lets you keep an existing mailbox or another DMARC service while evaluating JetEmail.
Receivers may apply their own limits to the number of destinations, report size, and reporting frequency.

​
Important DMARC tags

​
Move safely towards enforcement

1

Start with visibility

Use p=none for a new policy while reports identify legitimate and unexpected sources. This policy monitors failures but does not ask receivers to block them.
2

Fix legitimate sources

Configure aligned DKIM wherever possible and correct the SPF return path for every authorized sender. Confirm forwarding and mailing-list behavior before making policy changes.
3

Introduce quarantine

Move to p=quarantine, optionally with a lower pct during rollout, and watch the failing volume and receiver dispositions.
4

Enforce rejection

Use p=reject; pct=100 only after all legitimate high-volume sources have reliable aligned authentication.
Changing a DMARC policy affects how receiving mail systems handle messages using your domain. JetEmail reports what receivers observed; it does not automatically change your DNS or enforcement policy.

​
Remove a domain

Click the remove action beside a domain and confirm the dialog. The generated address stops accepting new reports for that registration. Previously ingested data remains subject to the normal retention policy. Remove the JetEmail destination from every DMARC record that uses it after deleting the registration.