Skip to main content
In DMARCeye, billing is based on domain slots — not on whether a domain is actively sending email or correctly configured. This article explains exactly which domains count toward your slot limit and which do not.

​
Billable domains

A domain occupies a slot — and is therefore billable — as soon as it is added to your account and placed in either Active or Pending status. Active domains are fully set up and receiving DMARC reports. These are the straightforward case: the domain is monitored, it counts toward your limit, and it appears in your billing. Pending domains have been added to your account but are not yet fully configured — DNS records may be missing or incorrect, and no reports are arriving yet. Despite this, a Pending domain already occupies a slot. The slot is reserved the moment a domain is added, regardless of its setup state. This applies equally to misconfigured domains and domains that are not yet sending any email. If the domain is in your account and not Parked, it counts.

​
Non-billable domains

Parked domains do not occupy a slot and are not billable. Parking is designed exactly for this purpose — it lets you keep a domain in your account without committing a slot to it. You can park a domain at any time and reactivate it later when a free slot is available.

​
Subdomains

Whether a subdomain is billable depends on its DNS configuration, not on whether it was added manually or detected automatically. A subdomain with its own DMARC record in DNS is treated as an independent domain. If you activate it, it occupies its own slot and is billed accordingly. A subdomain that inherits its DMARC policy from the parent domain does not have an independent DNS entry to bill against — however, if you choose to activate it in DMARCeye, it still occupies a slot and counts toward your limit. The billing is tied to the slot being used, not to the presence of a dedicated DMARC record. Subdomains detected automatically from reports are placed in Parked status and are not billable until you explicitly activate them. For a full explanation of how subdomains are detected and managed, see Subdomains in DMARCeye. For slot usage specifics, see Subdomains and domain slots.

​
Summary

​
Why billing is based on slots, not activity

DMARCeye cannot reliably determine in real time whether a domain is genuinely active. DNS propagation delays, external configuration changes, and periods of no sending activity all make it impossible to use live domain state as a billing signal. The slot model avoids this ambiguity entirely — if a domain is in your account and not Parked, the slot is yours and billing applies consistently.