Custom portal domain
By default, your membership portal lives at mailinapp.com/learn/<slug> and your landing pages at mailinapp.com/lp/<slug>. A custom portal domain replaces that shared host with one of your own — hub.yourbrand.com — so the root of your domain becomes your portal, and hub.yourbrand.com/lp/<slug> serves every landing page you publish, with nothing pointing back at mailinapp.com.
Set it up
Available on Lite and above, from Settings → Membership portal → Custom portal domain. Unlike a custom tracking domain, this doesn't require a verified sending domain — it works even if you send through your own SMTP relay.
- Claim your membership portal URL first, if you haven't already — the custom domain's root needs somewhere to point.
- Enter your hostname (e.g.
hub.yourbrand.com) and hit Connect. - Add the one CNAME record shown at your DNS provider.
- MailInApp automatically provisions a trusted TLS certificate once the CNAME resolves — no certificate files to upload, and no downtime while it verifies.
Once verified, hub.yourbrand.com/ renders your membership portal and hub.yourbrand.com/lp/<slug> renders your landing pages. The shared mailinapp.com/learn/<slug> and mailinapp.com/lp/<slug> URLs keep working side by side — connecting a custom domain adds a branded one, it doesn't retire the old ones.
What it doesn't change
One domain covers your whole account: every landing page you publish appears under it automatically, with no per-page setup. Landing pages stay scoped to your own account — your custom domain can never surface someone else's page, even if you happen to know their slug. Disconnecting the domain, or downgrading below Lite, takes it out of service immediately without breaking the shared mailinapp.com links.