Email Alias Forwarding Limits: What Each Plan Actually Meters

The two numbers that decide your plan

Understanding email alias forwarding limits requires looking past marketing pages that lump address inventory and message throughput into a single figure. Email alias forwarding limits meter two distinct operations: monthly forwarded message volume and daily alias creation velocity. What is metered is forwarded email, not aliases. On Emcognito, held aliases are unlimited on every tier. Inbound deliveries and outbound compose sends draw against the monthly forward quota: 2,500 messages per month on Plus and 15,000 on Pro.

Held aliases rarely cause bottlenecks. You can maintain thousands of distinct addresses without paying per-alias surcharges. The operational constraint is how many new addresses you provision in a 24-hour window. If you generate addresses by hand in your browser, that cap allows substantial reorganizations while preventing abuse.

Run this two-step sizing test before comparing subscription tiers:

1. Count the total inbound messages delivered across all your active aliases in a calendar month.
2. Determine the peak number of new aliases you need to provision in a single 24-hour burst during migrations or bulk credential resets.

An alias inventory paired with a restrictive message limit creates problems. A service may advertise unlimited aliases, yet throttle forwarding after a few dozen receipts. Creating specific aliases for banks, utilities, and retailers quickly leads to delayed or bounced notices once delivery thresholds are crossed.

What counts as a forwarded message

To evaluate forwarding quota management, you need to understand the unit of measurement. One inbound message delivered to your destination inbox equals one forwarded message. If an online store sends an order confirmation, that is one forward. If they follow up two hours later with a tracking link, that is a second forward. Delivery quotas meter individual SMTP transactions. Conversational threads do not pool into a single count; an exchange involving five messages consumes five units of quota. Message size also does not alter the count. Whether an email carries a five-megabyte PDF attachment or two lines of plain text, the system meters it as a single forwarded message.

Outbound messages draw on the same monthly forwarding allowance. When you compose new mail from any alias, each sent message consumes one unit of your monthly quota. Composing is not an independent allocation; sending a new email decrements the counter that inbound deliveries draw against.

Outbound sending also carries an operational velocity limit. Composing has a daily send cap: 20 a day on Plus and 100 a day on Pro, ramping up over the first 7 days. Hitting it does not stop inbound forwarding. Incoming deliveries continue uninterrupted as long as your overarching monthly quota has remaining capacity.

Consider a standard personal usage profile:

• 40 monthly newsletter editions routed through reading aliases
• 15 transactional verification codes and purchase receipts
• 10 customer service responses and authentication confirmations

This regular workflow totals 65 forwarded messages in a month. Against a monthly cap of 2,500 on the Plus plan, 65 messages consumes less than three percent of available volume.

Handling edge cases requires predictable mail routing. Under the Emcognito terms of service, incoming messages that exceed your plan capacity are held briefly. Emcognito collects no personal information beyond a destination address and does not retain message bodies after delivery, apart from a brief hold on mail that arrives over your monthly forward cap, but it keeps the delivery and operational logs any mail service needs. That is data minimisation, not a no-log policy. This brief hold prevents unexpected data loss while giving you time to adjust capacity or pause noisy senders.

Monthly caps vs. daily creation limits

Subscription tables frequently present quotas as simple monthly allowances without distinguishing between processing timeframes. A monthly forward quota resets on a recurring billing cycle anchored to your subscription renewal date. An alias-creation cap is an operational throttle that resets at 00:00 UTC.

For dashboard interactions, Emcognito enforces a uniform ceiling: 200 a day from the dashboard (Free included). For automated workflows, developer allocations depend on your chosen subscription tier. Through the developer API, creation is capped at 50 aliases a day on Plus and 200 aliases a day on Pro.

This daily creation pacing dictates how quickly you can execute an infrastructure migration. If you maintain 400 aliases on an external platform and decide to move them, you cannot provision all 400 records in a single batch. At a dashboard limit of 200 a day, your migration requires two calendar days.

Do not confuse the daily alias creation cap with API burst throttling. The REST interface enforces a burst limit of 60 requests a minute per key. A client script attempting to dispatch 50 creation calls in three seconds will trigger rate-limit handling even though the account remains below its daily creation quota.

How to measure your real forwarding volume before you buy

Most individuals overestimate their monthly volume requirements. Inboxes accumulate subscriptions, receipts, and automated digests, yet the actual message counts rarely reach enterprise proportions. As Pew Research Center research on email use documents, email remains central to everyday digital workflows, with message volume concentrating heavily inside primary communication channels.

Most accounts forward zero messages in a given month. Many accounts hold dormant addresses configured for infrequent emergency logins or discontinued commercial services. A forwarding cap is rarely the primary reason to upgrade. Do not purchase enterprise capacity for mailbox traffic you do not generate.

To calculate your real footprint, pull your actual numbers using this three-step audit:

1. Access your current alias dashboard or email provider search bar and filter for messages received over the previous 30 days.
2. Group the results by the receiving alias address to isolate your highest-frequency senders.
3. Separate recurring notifications from one-off transactional confirmations such as registration verifications or password resets.

Filling out this worksheet reveals which addresses generate unnecessary traffic. If an obscure address receives dozens of unsolicited messages every week, inspect the address before purchasing a larger tier. You can use the sudden spam diagnostic workflow to isolate the source. When a service experiences a breach or shares a database, isolating that specific alias lets you shut down the leak at the source without altering the rest of your identities.

Where free tiers fit now, and where they stop

Free tiers across the privacy industry have shifted toward tighter operational boundaries. Emcognito Free is closed to new accounts. Since 2026-10-29 a new account chooses Plus or Pro; there is no free sign-up and no way to open an account without a paid plan or a Pro trial. New Emcognito accounts choose Plus or Pro at checkout. Plus is charged at checkout, and the first payment can be refunded within 14 days, once per account; Pro starts with one 7-day free trial per account, which takes a card at checkout and charges nothing during the trial. The Free plan is only for accounts opened before October 29, 2026.

Accounts opened before October 29, 2026 keep the Free plan for now; any change to it comes with notice. New accounts choose Plus or Pro. Those legacy Free tiers maintain unlimited held aliases, but their message processing capacity remains strictly constrained: 35 forwarded messages per month for accounts created between October 19, 2026 and October 28, 2026. Accounts created before October 19, 2026 retain 100 forwards per month. Referral bonuses can raise those historical ceilings to at most 135 or 200 monthly forwards, respectively.

Legacy Free accounts also face structural functional restrictions. Free cannot compose new mail or reply from its own mail app. Reply securely in the delivery log is included on every Emcognito plan until November 3, 2026, and on Plus and Pro from then on. Replying from your own mail app is a Plus and Pro feature. If an account on the Free plan attempts to dispatch a response directly from a personal mail application, the delivery engine rejects the message and returns an upgrade notice.

Free forwards carry a first-party alias status bar, not a sponsor card. Plus and Pro forwards carry no footer. The legacy footer details the receiving alias, confirms whether tracking pixels were neutralized, displays current monthly usage, and provides direct links to pause delivery or block the sender. It does not remove scripts or rewrite links and does not scan for malware. Paid tiers eliminate the footer entirely, delivering messages unaltered directly to your inbox.

Comparing forwarding quotas across services without getting fooled

Evaluating vendor pricing requires verifying technical mechanisms. While broad consumer protections exist, such as FTC guidance on how websites and apps collect and use information, privacy tools themselves must be audited on exact technical constraints. Apply these five diagnostic criteria to evaluate any alias architecture:

1. Verify whether the plan limits total generated alias addresses, total monthly forwarded email transactions, or bandwidth volume measured in megabytes.
2. Establish whether composing new messages or replying to incoming inquiries reduces your monthly delivery count.
3. Determine if daily creation limits prevent rapid migrations or batch infrastructure configuration.
4. Check if a documented REST API exists, whether access requires top-tier plans, and how rate limits are structured.
5. Avoid systems that lock alias routing inside a proprietary password manager or a single commercial operating system.

Every architecture involves specific trade-offs, and Emcognito is the wrong choice for certain setups. Emcognito aliases currently use the shared emcognito.com domain. Custom domains are not available today; a custom subdomain at handle.emcognito.com is available on Pro. If configuring an independent apex domain using personal DNS records is an absolute requirement for your routing architecture, alternative providers like SimpleLogin or addy.io serve that specific need. Furthermore, Emcognito is closed source and runs only as a hosted service; if open source or self-hosting is a requirement, addy.io is the better fit.

When the API cap is the limit that binds

For technical users running programmatic workflows, monthly forwarding thresholds rarely cause problems. The binding constraint is the daily alias creation cap. If you maintain scripts that generate isolated credentials for continuous integration runs, programmatic test accounts, or customer provisioning, you hit creation limits long before exhausting inbound bandwidth.

The developer alias API exposes a minimal surface. Version 1 provides exactly two endpoints: GET /v1/aliases to retrieve paginated records using next_cursor or last_key, and POST /v1/aliases to generate an address. There is no PATCH, PUT or DELETE endpoint and no /v1/aliases/{id} resource in v1. Pausing, resuming, or deleting an alias are dashboard actions. The v1 API does not handle them.

POST /v1/aliases returns HTTP 200 with the new alias under "alias". The burst limit is 60 requests a minute per key; its 429 carries a Retry-After header giving the seconds until the window resets. The daily alias-creation cap (50 on Plus, 200 on Pro) resets at 00:00 UTC and its 429 carries no Retry-After. Emcognito sends no X-RateLimit-* headers.

Authentication requires an API key formatted with the prefix emk_ followed by 43 URL-safe characters. There is no live or test environment split; every generated address exists on the live routing cluster. The JSON response from POST /v1/aliases wraps properties inside an alias object:

{
  "alias": {
    "id": "alias_9x7k2m4p",
    "address": "k7m2p9x4q@emcognito.com",
    "status": "active",
    "created_at": 1793318400,
    "forward_count": 0,
    "label": "staging-checkout",
    "note": "automated test suite",
    "source": "api",
    "category": "testing",
    "single_use": false,
    "expires_at": ""
  }
}

The created_at attribute returns an integer epoch timestamp instead of an ISO-8601 string. Unset string attributes return an empty string instead of null.

When engineering background provisioning tasks, your code must handle the two distinct throttling mechanisms separately:

• If an API call returns HTTP 429 with a Retry-After header, your worker has exceeded the rolling 60-requests-per-minute burst ceiling. Parse the header value, sleep your process for the specified number of seconds, and retry.
• If an API call returns HTTP 429 without a Retry-After header, your account has consumed its daily allocation (50 on Plus, 200 on Pro). Pausing for 60 seconds will fail; execution must sleep until 00:00 UTC when the application limit resets.

Sizing your plan: three reader profiles

Heavy subscribers

You maintain active subscriptions to dozens of regular senders, including retail trackers, industry updates, technical digests, and service bills. You need dependable inbound throughput and the ability to compose outbound mail using your aliases. The Plus plan provides 2,500 monthly forwarded messages, full compose capabilities, and an API quota of 50 aliases a day. Plus has no trial; it is charged at checkout, and the first payment can be refunded in full from Billing within 14 days, once per account.

Active migrators

You are migrating hundreds of established accounts away from legacy setups or consolidating addresses into unique identities per vendor. You need higher daily creation throughput to build your catalog without waiting weeks, along with significant monthly delivery headroom. The Pro tier delivers 15,000 monthly forwards and expands daily creation to 200 aliases across both dashboard and API interfaces. Billed annually, Pro provides three months free compared to monthly billing and includes one 7-day trial per account. A card is taken at checkout, and nothing is charged during the trial period.

Developers

Programmatic alias generation is your primary operational objective. You are provisioning test environments, building custom signup automation, or writing deployment verification tools. Because programmatic creation velocity is paramount, the Pro plan provides the necessary capacity by lifting the API threshold to 200 aliases a day while maintaining access to all messaging capabilities.

What to do when you hit a cap

When email delivery stalls or an address creation attempt fails, systematically isolate the specific constraint before modifying your subscription:

1. If your script or dashboard returns a creation error while forwarding operates normally, you reached the daily creation limit (200 aliases in a UTC day, or 50 via the API on Plus). Wait until 00:00 UTC for the counter to reset.
2. If an outgoing reply is refused while incoming mail still arrives, you reached the outbound compose limit (20 a day on Plus, 100 on Pro during early account ramp-up). On Plus and Pro you can hit Reply in your own mail app (Gmail, Outlook, Apple Mail) on a forwarded message, and Emcognito sends the reply from the alias. It is accepted only from the mailbox you sign in with, and each reply uses one monthly send. On Free, replying from your mail app is a Plus feature; Free accounts can reply from the delivery log with Reply securely until November 3, 2026, after which Reply securely is Plus and Pro only.
3. If an automated integration receives an HTTP 429 response containing a Retry-After header, the client exceeded 60 requests in a 60-second window. Implement an exponential backoff algorithm in your client code.

You can manage quota consumption without immediately purchasing additional tiers. Any alias can be paused with one click using the "Pause alias" dashboard control. Suspending an address stops inbound routing, saving monthly delivery allowance for critical accounts. Pausing an alias also pinpoints which specific organization leaked or shared your information, as each site communicates with a distinct address. If an address is permanently abandoned, you can delete it from your dashboard after confirming the warning prompt.

Managing security threats also protects forwarding capacity. FTC phishing guidance highlights how deceptive messages flood mailboxes during credential-harvesting campaigns. When attackers target an alias with high-frequency junk, pausing that single address neutralizes the abuse instantly without altering your legitimate communication channels.

Frequently asked questions

Do email aliases have a monthly forwarding limit?

Yes. Forwarding providers meter operational throughput to maintain mail server reputation and prevent spam abuse. On Emcognito, the Plus plan provides 2,500 forwarded messages per calendar month, while the Pro plan provides 15,000 forwarded messages per month. Held aliases remain unlimited on all tiers.

What happens when I hit my monthly forward cap?

When an account reaches its monthly message ceiling, inbound mail is not silently dropped. Messages that arrive over your monthly forward cap are held briefly, allowing you time to upgrade your subscription tier or pause high-frequency senders to manage capacity.

Is the daily alias creation limit the same as the API rate limit?

No, they are enforced by different mechanisms. The API rate limit throttles bursts at 60 calls a minute per key, returning HTTP 429 with a Retry-After header. The daily alias creation cap (50 per day on Plus, 200 per day on Pro) resets at 00:00 UTC and returns an application-level HTTP 429 without a Retry-After header.

The honest next step

If your constraint is composing new mail from any alias, compare Plus and Pro on the pricing page: Plus is $20/year, Pro is $36/year with one 7-day trial per account.