Account & Security

Does MailBlastr require production approval?

No — there is no approval step. New accounts start on the Free plan limits, and higher limits come from upgrading your plan.

No. There is no production-approval step, no sending sandbox, and no verified-recipient restriction. As soon as you have a verified sending domain, you can send to any recipient — the only limits on a new account are the Free plan quotas.

What limits a new account

New accounts start on the Free plan:

100 emails per rolling 24 hours — an anti-abuse safety rail on the Free plan only.
3,000 emails per rolling 30 days (sent + received combined).
A send that would exceed either quota is rejected with a 429 (daily_quota_exceeded / monthly_quota_exceeded) — see Account quotas and limits.

Higher limits are self-serve: upgrade your plan for a larger monthly volume and no daily cap, or buy email credits to extend the monthly volume. There is no request-and-approval flow.

The one gate: domain verification

The only thing that blocks sending outright is an unverified from-domain. If you have added a domain but not yet published its DNS records, it stays Pending and you cannot send from it — that is a DNS problem, not an account approval.

Domain shows Pending → publish the SPF/DKIM/DMARC records so it verifies. See Managing domains.
Send rejected with a domain-related `validation_error` → the from address is not on one of your verified domains.

Getting to production volume

1
Verify your sending domain
Publish the SPF/DKIM/DMARC records MailBlastr generates so your domain is fully verified. See Managing domains.
2
Pick a plan that fits your volume
The Free plan is sized for testing and integration work. Upgrade to a paid plan for the monthly volume you need — paid plans have no daily cap.
3
Warm up gradually
Ramp volume over days rather than all at once, and keep your bounce and complaint rates healthy — see Account quotas and limits for the reputation guardrails.