Skip to main content
Each activated subdomain occupies one domain slot, just like a root domain. This article explains what that means for your plan and how to manage slot usage across subdomains.

Subdomains count as independent slots

From a billing perspective, DMARCeye treats every monitored domain the same way — root domain or subdomain. Once you activate a subdomain, it occupies one slot in your account and counts toward your plan limit. Whether the subdomain has its own DMARC policy or inherits one from its parent domain makes no difference to slot consumption. The slot is tied to monitoring activity, not to DNS configuration.

Auto-detected subdomains do not consume slots

Subdomains that DMARCeye detects automatically from reports are placed in Parked status. A Parked domain does not occupy a slot. You are not charged for a subdomain simply because it was detected — only activation triggers slot usage. This gives you full control: you can review detected subdomains and decide which ones are worth monitoring before committing a slot.

Planning your slot count

If your root domain sends email across multiple subdomains — for example, separate subdomains for transactional mail, marketing campaigns, or regional operations — each one you choose to monitor will require its own slot. A practical way to plan: look at your Parked subdomains, identify which ones are active senders you want visibility into, and make sure your plan includes enough slots to cover both your root domains and those subdomains.

Example

You are on a Scale plan with 5 domain slots. You are currently monitoring example.com and shop.example.com — that is 2 slots used. DMARCeye then detects mail.example.com and newsletter.example.com in your reports and parks them automatically. You decide to activate mail.example.com, bringing your used slot count to 3. newsletter.example.com stays Parked and does not affect your billing.