What is double opt-in?
Double opt-in is a subscription process where, after someone submits their email, you send a confirmation link they must click before being added to your list. It proves the address is real and that the person genuinely consented.
Single vs. double opt-in
With single opt-in, an address is added to your list the moment it's submitted. It's frictionless but accepts typos, fake addresses, and people who didn't really mean to subscribe.
Double opt-in adds a confirmation step: you email the address a link, and only confirmed clicks join the list. This filters out invalid and unintended addresses up front, at the cost of a small drop in raw signup numbers.
Why double opt-in helps deliverability and compliance
Because every confirmed subscriber proved their address works and that they want your mail, double opt-in lists have lower bounce rates, fewer spam complaints, and higher engagement — all signals that improve sender reputation and inbox placement.
It also strengthens your consent record, which matters under regulations like GDPR where you must be able to demonstrate that a person agreed to receive marketing.
Double opt-in and verification together
Verification and double opt-in are complementary. Real-time verification at the form stops invalid and disposable addresses before you even send the confirmation, so you don't waste a confirmation email on an address that can't receive it.
Using both gives you the cleanest possible list: verification removes the technically bad addresses, and the confirmation click proves genuine intent. Mailbeam's real-time check slots neatly in front of a double opt-in flow.
The record that makes consent demonstrable
GDPR Article 7(1) puts the burden of proof on the controller. Double opt-in matters because it produces the one field you cannot fabricate afterwards.
subscriber jdoe@example.com
consent_text the exact wording shown at signup
consent_at 2026-06-13T09:14:22Z
source_url https://example.com/newsletter
source_ip 192.0.2.44
confirm_token single-use, time-limited
confirmed_at 2026-06-13T09:17:05Z <- the second step
Without confirmed_at you have a claim that somebody typed
an address. With it you have evidence that the person who
owns the mailbox acted on it.GDPR Article 7(1) requires the controller to demonstrate consent, and the confirmation timestamp is what turns a submitted address into evidence that the mailbox owner acted.
Sources
Checked against these sources on .
In practice
A visitor enters their address in your newsletter form. Mailbeam verifies it in real time (valid, not disposable), so you send the confirmation email; the visitor clicks the link and is added. A mistyped or throwaway address would have been caught before the confirmation was ever sent.
Frequently asked questions
Verify emails with confidence
Mailbeam handles all of this for you — syntax, MX, SMTP, catch-all, and disposable checks in one API call. 1,000 free verifications/month, no credit card.