Annual licences add capacity to a shared pool of managed base domains. Eligible subdomains do not add to the count. Each SPF domain still needs its own DNS setup.
One base domain can cover several SPF records
Emailmetry's annual licences add capacity to a shared pool. One unit of annual cover can accommodate one managed base domain and its eligible subdomains. For example, example.com, news.example.com and accounts.example.com count as one base domain. A separate domain such as example.net increases the count to two. No licence is assigned to a particular domain.
Annual cover costs USD $36 per licence for 12 months upfront. Domains above that cover are monthly extras at USD $5 per uncovered base domain for the billing month, excluding tax. The pricing article explains what that charge pays for.
A worked domain example
Suppose a business wants flattening for its main domain and newsletter subdomain, and also uses a separate brand domain. At the standard rate:
| SPF domain | Counts toward managed base domains | Extra base-domain count |
|---|---|---|
| example.com | Yes | 1 |
| news.example.com | Eligible subdomain of example.com | 0 |
| example.net | Yes, separate base domain | 1 |
That is two managed base domains, even though there are three SPF records. With no annual cover, two monthly extras would cost USD $10 for a billing month if both count at its peak. With two annual licences, cover would cost USD $72 upfront for 12 months. One annual licence plus one monthly extra would combine the two rates. These examples exclude tax and any volume discount.
Count the domain the message actually uses
The visible From address does not establish which domain needs SPF. SPF normally checks the MAIL FROM domain, also called the envelope sender or return-address domain.
Amazon SES, for example, uses an Amazon-owned domain by default, but also supports a custom MAIL FROM domain. Adding an application does not necessarily create another SPF record under your control.
Inspect a message from the application with the email header analyser and check the sending service's account settings before counting records for flattening.
Cover still needs a separate DNS setup
An SPF record at example.com does not automatically apply to news.example.com. Each domain using the service needs its own DNS record pointing to its corresponding hosted policy.
Pool coverage also does not mean every subdomain needs flattening. A subdomain with a short, supported policy may work well with ordinary provider includes. The subdomain guide explains that separation; the billing page covers pooled annual cover and monthly extras.
Sources and further reading
- Microsoft: Configure SPF
- Amazon SES: SPF authentication
- Emailmetry: pricing
- Emailmetry: domain licences and billing
Sources reviewed 27 September 2026.