Pre-warmed inboxes
Pre-Warmed Domains and Accounts
Pre-warmed domains and accounts on EmailPal are leased mailboxes on 90-day-aged domains that already finished warming, with SPF, DKIM and DMARC in place and a measured inbox-placement rate attached. Ready to send 15 cold emails a day from day one.
What are pre-warmed domains and accounts?
A new domain and mailbox have no sending history. Inbox providers treat that as unknown, which is why a brand-new Google Workspace seat or a brand-new SMTP account usually needs two to three weeks of warmup before campaign volume is safe.
Pre-warmed domains and accounts skip that wait on your side. EmailPal registered the domain, parked it for 90+ days, warmed the mailboxes against real Gmail, Yahoo and AOL accounts, and listed each address with the inbox-placement rate measured across that ramp.
You do not bring a custom domain name or pick mailbox handles. The listing is a domain with its mailboxes already named, authenticated and warmed — one company story, ready to claim.
This is the same category Instantly's "Pre-Warmed Domains and Accounts" article and Smartlead's "Pre-warmed Mailboxes" article occupy. EmailPal's version is a lease at $3/mo per mailbox, a 15/day send cap, measured placement on the listing, and warming included for the life of the lease.
The full product write-up is Pre-warmed Mailboxes by EmailPal. The definition of the phrase: What "pre-warmed" means.
What is already done for you
- Domain age of at least 90 days — DNS has had time to settle
- MX, SPF (hard fail), dual DKIM (RSA-2048 + Ed25519) and DMARC
p=rejectwritten and re-verified on public resolvers - Warming finished against real provider accounts, not EmailPal-to-EmailPal loops
- Inbox rate visible on the listing before you pay
- Warming stays on after you claim, included in the $3/mo lease
- Personas already assigned so the set reads as one company
- Passwords rotated at handover — the inventory list never shows them
That is the bundle. Age without the ramp is aged, unwarmed domains, a different SKU. A domain you registered this morning with "warming" as a label is not pre-warmed.
Pricing
| Item | Price | Notes |
|---|---|---|
| Pre-warmed mailbox | $3 / month | Per address, billed monthly |
| Warming on a leased mailbox | Included | Do not add $0.60 |
| Minimum term | 90 days | Then month to month |
| Cold send cap | 15 / day | Hard cap per mailbox |
| Plan mailbox slot | Not used | Leases sit outside Starter/Growth/Scale counts |
You claim by domain so the addresses read as one company. The monthly charge is $3 × the number of inboxes on that domain. Releasing before day 90 does not waive the remaining term. Pre-warmed billing and the 90-day term.
There is no free trial of the shelf. You can read measured placement before you confirm.
How to get them
Dashboard
- Sign in with a payment method on file.
- Open Pre-warmed. Each row is a domain with one or more inboxes already named.
- Expand a row: addresses, domain age, messages measured, inbox rate.
- Claim. Confirm the monthly total and the 90-day term. Nothing is billed until you confirm.
- A job rotates passwords and assigns the mailboxes. Usually minutes, not hours.
- Export SMTP/IMAP from Mailboxes into Instantly, Smartlead, Plusvibe, or send through our API.
Step-by-step including API and MCP: How to claim pre-warmed inboxes.
REST / MCP
GET /api/public/v1/inventory/prewarmed lists the shelf (no passwords). POST with count, domain_id or mailbox_ids starts a claim job. MCP exposes the same tools. Set EMAILPAL_MCP_READ_ONLY=true if an agent should inspect, not buy.
How this differs from warming a mailbox you already own
| Warming a mailbox you own | Pre-warmed domain / account | |
|---|---|---|
| What you buy | $0.60/mo on a mailbox you created or connected | $3/mo lease of inventory we prepared |
| Domain | Yours (registered, BYO, or Google/Outlook) | Ours; you lease |
| Names | You choose | Already assigned |
| Time to send | Typically 14+ days (7 on aged) | Minutes after claim |
| Send cap | 40/day once campaign-ready | 15/day immediately |
| 90-day term | No | Yes |
If you registered a domain yourself, or connected Gmail / Outlook / your own server, use Email warming by EmailPal at $0.60/mo. That path still needs the ramp.
Pre-warmed inventory is for sending on day one without running that ramp. Pre-warmed vs email warmup.
Sending rules after you claim
- 15 cold emails per day per mailbox. Hard cap. Volume means more inboxes, not a higher number.
- Leave warming on. It is included. Pausing it is how you undo the reason you paid $3.
- Verify the list before the first campaign. How to verify an email list before sending.
- Do not add a forwarding domain, extra DKIM, or a second SPF. Authentication is already done.
- Replies land in the unified inbox, with warming traffic filtered out by default.
Unlike a fresh mailbox, you do not start at 20–30/day and add five a day. The ramp already happened. The 15/day ceiling is how we keep that measurement from collapsing the first week you use the address.
FAQs
Can I customize the domain or mailbox names?
No. Personas are already assigned. If you need names you choose, register a domain or bring your own and create mailboxes there, then warm them.
Are these Google or Outlook accounts?
No. They are EmailPal-hosted SMTP/IMAP mailboxes on domains we registered. Credentials export after the claim job. See SMTP vs Google vs Outlook for cold email. Instantly and Smartlead accept them as SMTP accounts.
How soon can I send?
As soon as the claim job finishes and passwords rotate — usually minutes. Warming already ran before the address was listed.
The shelf is empty.
Inventory lists itself when pool inboxes finish their second week of warming. Check back, or provision your own domains and run warming. Aged, unwarmed domains are the middle path.
Do I get the domain if I leave?
No. The domain stays ours. A registered domain you bought through EmailPal is a different product and remains yours.
Can I pick two inboxes on a domain and leave the rest?
The dashboard claims a domain as a set so the company story stays intact. The API can pass mailbox_ids when you need a subset; prefer claiming the domain.
Need more help?
Open a support ticket or read the pre-warmed collection.