How it works
From first login to first send in three steps. A verified domain is needed to send; for campaigns, contacts must also confirm their subscription (double opt-in). Both apply on every plan, Free included.
Step 1
Verify your sending domain
You sign up with a business email (not Gmail or similar) and add the domain you want to send from. In the console you get the DKIM records to add to your domain's DNS; once they are active, the domain shows as verified.
Without a verified domain you can't send, and its status is rechecked periodically: if a record disappears, sending from that domain stops.
Step 2
Import your contacts
Import a CSV file (up to 10,000 rows) and pick the email column and, if present, the name column. You can also add contacts one at a time. New contacts must confirm their subscription before receiving campaigns.
Campaigns only reach contacts who have confirmed (double opt-in), and every campaign carries an unsubscribe link. Importing a CSV does not grant any consent to click tracking.
Step 3
Write and send
Build the campaign with the drag-and-drop editor and send it to confirmed contacts, or send single messages from your backend through the API (POST /email/send), with templates and variables or free-form HTML. For each campaign or API send you pick the language among Italian, English, Spanish, German and French: it applies to service texts and does not translate your content.
Hard bounces and complaints are handled automatically: mailronix stops writing to that address. Opens are not tracked; clicks are tracked only if you turn on tracking for the brand and the recipient consents.
Why we ask for these things
The sending infrastructure is shared: one customer's traffic can affect the shared reputation. That is why we verify domains, require double opt-in for marketing and handle bounces and complaints automatically.
These are measures we take on our side, not a promise of delivery: where a message lands also depends on what you write and to whom.
Follow the outcomes. Choose whether to track clicks.
See deliveries accepted by the recipient's server, bounces, complaints and failures. Click tracking is off by default: you can turn it on for a brand, and only for recipients who have consented. Opens are not tracked.
Detected clicks can also be generated by scanners and previews. Recipients can withdraw consent from Preferences without unsubscribing.
Sending from your backend?
Send transactional email with an API key and set up webhooks from the console to receive signed events in your application. Find examples, errors and the OpenAPI specification in the documentation.
Ready to try it?
The Free plan is free with no trial period: 3,000 emails a month.
Up to 500 unique recipients per day. Sign up with a work email and verify your domain to send. No credit card.