> ## Documentation Index
> Fetch the complete documentation index at: https://jetemail.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Domains and DNS

> Manage monitored domains, subdomain coverage, RUA destinations, and DMARC policy changes.

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

| Status          | Meaning                                                                                                                                                                                |
| --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Pending DNS** | The domain is registered, but JetEmail has not found its assigned address in the DMARC `rua` tag. Use **Setup** to view the expected destination and **Check DNS** after updating DNS. |
| **Verified**    | JetEmail found the assigned address in the domain's current DMARC record. The setup details remain available under **View**.                                                           |

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.

```text theme={null}
v=DMARC1; p=reject; sp=quarantine; rua=mailto:5e2f617ea64848ab9073@rua.jetsmtp.net
```

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.

<Note>
  You do not need to register every subdomain separately when they report to the parent domain's assigned address.
</Note>

## 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.

```text theme={null}
v=DMARC1; p=none; rua=mailto:dmarc@example.com,mailto:5e2f617ea64848ab9073@rua.jetsmtp.net
```

Receivers may apply their own limits to the number of destinations, report size, and reporting frequency.

## Important DMARC tags

| Tag     | Purpose                                                            |
| ------- | ------------------------------------------------------------------ |
| `p`     | Policy for the domain: `none`, `quarantine`, or `reject`           |
| `sp`    | Optional policy for subdomains                                     |
| `np`    | Optional policy for non-existent subdomains in newer DMARC reports |
| `rua`   | Aggregate report destinations                                      |
| `pct`   | Percentage of failing mail to which enforcement applies            |
| `adkim` | DKIM alignment: relaxed (`r`) or strict (`s`)                      |
| `aspf`  | SPF alignment: relaxed (`r`) or strict (`s`)                       |

## Move safely towards enforcement

<Steps>
  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Introduce quarantine">
    Move to `p=quarantine`, optionally with a lower `pct` during rollout, and watch the failing volume and receiver dispositions.
  </Step>

  <Step title="Enforce rejection">
    Use `p=reject; pct=100` only after all legitimate high-volume sources have reliable aligned authentication.
  </Step>
</Steps>

<Warning>
  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.
</Warning>

## 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.