the email tool that makes email marketing simple
Sign Up FreeNo credit card required.
Published: July 16, 2026
Landing Page Domains let you publish Maildroppa Landing Pages under an address that belongs to your business.
Instead of sharing only the standard Maildroppa address, you can use a subdomain such as newsletter.your-real-domain.com, add an optional path, and publish pages at addresses such as:
https://newsletter.your-real-domain.com/weekly-tips
Maildroppa checks that you control the subdomain, confirms that visitors are routed to the correct service, and prepares a secure HTTPS connection. The Landing Page Domains page brings the setup status, required DNS records, manual connection check, and domain removal together in one place.
A Landing Page domain is the hostname used for public Landing Pages created with Maildroppa's Signup Form Builder.
Maildroppa connects a subdomain rather than the root domain. For example:
newsletter.your-real-domain.com is a subdomain and can be connected.www.your-real-domain.com is also a subdomain and can be connected.your-real-domain.com is the root domain and cannot be connected through this CNAME-based setup.Using a separate subdomain keeps the Landing Page connection independent from your main website. Your website can remain on your-real-domain.com while Maildroppa serves Landing Pages on newsletter.your-real-domain.com.
You can connect up to ten Landing Page domains to one Maildroppa account. This is useful when you manage several brands, campaigns, countries, or public page groups. A connected domain can also host more than one Landing Page when each page uses a different path.
The Landing Page Domains page controls web addresses for published Landing Pages. It does not authenticate the email address used to send campaigns or Double Opt-in emails.
These are separate settings:
Connecting a Landing Page domain does not automatically make that domain an authenticated sending domain. Likewise, authenticating a sender domain does not automatically connect it as a Landing Page domain. Complete both setups separately when you want to use the same organizational domain for web pages and email sending.
Before connecting a domain, make sure that:
Do not disconnect an existing website, shop, or application to reuse its hostname. Choose a new subdomain when the desired name already has an A, AAAA, or CNAME record.
The examples in this guide show the required format. Replace them with a subdomain of a real domain that you control. Maildroppa rejects placeholder domains such as example.com and Maildroppa-owned domains.
Open “Settings” and select “Landing Page Domains”.
If you have not connected a domain yet, the page shows “No landing page domains yet”. Click “Add domain” to begin.
When domains already exist, the page shows:
The layout changes into compact cards on smaller screens, but the available information and actions remain the same.
Click “Add domain”. Enter only the complete subdomain, for example:
newsletter.your-real-domain.com
Do not enter:
https://newsletter.your-real-domain.comnewsletter.your-real-domain.com/signuplocalhostyour-real-domain.comMaildroppa removes surrounding spaces, converts the name to lowercase, and removes a final DNS dot. Other invalid formats are rejected before the domain is created.
Click “Create domain”. Maildroppa creates an individual verification for this subdomain and displays the two DNS records required for the connection.
If the subdomain is already connected to your own account, Maildroppa returns the existing setup instead of creating a duplicate. If it is connected to another Maildroppa account, use another subdomain or contact support when the domain belongs to you.
After creating the domain, open the DNS settings at the provider that manages your domain. Add both records exactly as Maildroppa displays them.
Each record has three parts:
Use the “Copy” buttons beside the name and value. Every domain receives its own values, so do not copy DNS details from another account, another domain, this guide, or an old screenshot.
The TXT record confirms that the subdomain belongs to you.
Its name begins with _maildroppa and includes the connected subdomain. Its value begins with md-verify= and contains the individual verification token generated for this domain.
For a subdomain such as newsletter.your-real-domain.com, the record follows this pattern:
Type: TXT
Name: _maildroppa.newsletter.your-real-domain.com
Value: md-verify=your-individual-token
The pattern above is only an explanation. Copy the exact name and value displayed in your Maildroppa account.
Do not place the token on the normal subdomain itself. Maildroppa looks for it at the special _maildroppa hostname.
Other unrelated TXT records can usually remain in place. The important point is that the exact Maildroppa value is present at the exact name shown.
The CNAME record routes visitors from your chosen subdomain to Maildroppa.
For a domain such as newsletter.your-real-domain.com, the CNAME name is the Landing Page subdomain itself. Its value is the Maildroppa target shown in the setup.
Type: CNAME
Name: newsletter.your-real-domain.com
Value: Copy the exact Maildroppa target displayed on the page.
The CNAME value is a hostname. Do not add https://, a path, spaces, or an IP address.
A hostname cannot normally have a CNAME and another routing record at the same name. If the chosen subdomain already has an A, AAAA, or different CNAME record, choose a different subdomain or remove the conflict only when you are certain the old service is no longer required.
DNS providers label their fields differently. A field may be called “Name”, “Host”, “Hostname”, or “Alias”.
Some providers expect the complete name displayed by Maildroppa. Others automatically append the main domain of the DNS zone.
For example, when you edit the DNS zone for your-real-domain.com, such a provider may expect:
_maildroppa.newsletter instead of _maildroppa.newsletter.your-real-domain.comnewsletter instead of newsletter.your-real-domain.comThe resulting public DNS name must still match the complete name shown in Maildroppa. If your provider displays a duplicated name such as newsletter.your-real-domain.com.your-real-domain.com, remove the automatically appended domain from the value you enter in the Name field.
Do not change the record Value to compensate for the provider's Name format. The Value must remain exactly as Maildroppa displays it.
If Cloudflare or another service can proxy the CNAME, use “DNS only” while connecting the domain.
In Cloudflare, this is the gray cloud rather than the orange proxied cloud. A proxy can hide the real CNAME target from the DNS check, which prevents Maildroppa from confirming the connection.
The TXT record is not proxied. Add it normally.
Save the records at your DNS provider. DNS changes are often visible within a few minutes, but they can take up to 48 hours to propagate.
Maildroppa checks domains in progress automatically. You can close the dialog or leave the settings page; the setup continues in the background.
The domain does not need to become ready during the same session in which you created it. Return to “Landing Page Domains” later to review its status.
Avoid repeatedly deleting and recreating the domain while DNS is propagating. Recreating it generates a new verification token, so an earlier TXT value will no longer complete the new setup.
Click “Check DNS” when both records have been saved.
Maildroppa checks the connection in stages:
If the records have not propagated yet, the domain remains pending. This does not mean that you need to create it again. Compare the displayed records with your provider, wait, and check later.
After a manual check, the button is briefly disabled and the page can show a countdown before another check is available. This pause prevents repeated DNS requests. Automatic checks continue independently.
When the connection is complete, Maildroppa shows “Domain verified” and changes the domain status to “Ready”. The “Check DNS” button is no longer shown for a ready domain.
The table uses a short status badge. During setup, more detailed text can explain the current stage.
Maildroppa has not found both required DNS records yet.
The detailed state can be:
Open the DNS details and compare each name and value. If you just saved the records, allow more time for propagation.
Maildroppa has found the required DNS connection and is preparing the secure public address.
The detailed state can be:
Do not change or remove the DNS records during this stage. You can publish the Landing Page through its standard Maildroppa address while waiting.
The TXT record, CNAME routing, and HTTPS connection are working. The domain can now be selected for a Landing Page.
Keep both DNS records in place. Removing or changing them later can make the domain unhealthy.
The domain was ready before, but its DNS or secure connection is currently unhealthy.
Open the DNS details, check whether the records were changed, and run “Check DNS”. Existing public pages may be affected, so resolve this status promptly or publish them through the standard address until the connection is healthy again.
The setup did not complete after repeated checks, or a previously working connection remained unhealthy.
Check the displayed failure information and both DNS records. If the values are correct, wait for propagation and try the check again. When an old or incorrect setup cannot be repaired, remove the unused domain and connect it again with the newly generated records.
Click the domain name, the DNS record count, or “Show details” in the actions menu to expand a domain.
The expanded table area shows the TXT and CNAME records again. You can copy each name and value without recreating the domain.
When you check a newly created domain in the setup dialog, Maildroppa can also show information from that check, including:
This information helps identify the difference between a missing record and a record that exists with the wrong value.
For example:
Connecting the domain does not automatically move an existing Landing Page to it. You select the public address separately for each page.
Open the Landing Page in the Signup Form Builder and open “Publish”, “Publish changes”, or “Manage publication”. In the public address section:
/ for the root of the connected subdomain.Only ready domains can be assigned to a new Landing Page route. Domains that are still waiting or connecting remain visible in domain management but are not ready for publication.
Each path on a domain can be used by only one Landing Page. For example, one domain can host:
https://newsletter.your-real-domain.com/weekly-tipshttps://newsletter.your-real-domain.com/webinarhttps://newsletter.your-real-domain.com/summer-guideOnly one page can use /, and two pages cannot use the same path on the same domain.
You can publish without a custom domain at any time by choosing the standard Maildroppa address. You can also change from the standard address to a ready custom domain later.
For the complete publication workflow, see Building and Publishing a Landing Page.
The Landing Page publication window and the Landing Page Domains settings page use the same domain list.
This means that:
The Settings page is the best place to review all domains in the account, compare their statuses, reopen DNS records, and remove domains that are no longer needed.
Open the three-dot actions menu beside the domain and select “Delete domain”. Confirm the deletion in the dialog.
Maildroppa prevents deletion while any Landing Page still uses the domain. This includes a domain selected in an unpublished draft and a domain used by a live public route.
To release a domain that is in use:
Deleting a domain from Maildroppa does not delete records at your DNS provider. After the domain is no longer used, remove its Maildroppa TXT and CNAME records manually if you no longer need them.
Do not remove the DNS records before moving live Landing Pages. Doing so can make their public addresses unavailable.
The connected name must be a real public subdomain. Enter the hostname only, without a protocol or path.
Correct format:
newsletter.your-real-domain.com
Incorrect formats:
https://newsletter.your-real-domain.comyour-real-domain.comnewsletter.your-real-domain.com/formnewsletter_your-real-domain.comCompare the record Type, Name, and Value separately. Verification tokens are account- and domain-specific. A value that looks almost identical can still be wrong.
Check for:
_maildroppa prefix on the TXT namemd-verify= valuehttps:// added to the CNAME valueThe Landing Page subdomain must route through the displayed CNAME. An existing A, AAAA, or different CNAME at the same name can prevent the connection.
The ownership TXT record uses its own _maildroppa name and should not be placed on the CNAME hostname.
Set the CNAME to DNS only during connection. This is especially important for Cloudflare's orange-cloud proxy, which hides the target Maildroppa needs to verify.
Even when your DNS provider immediately shows the new records, public DNS resolvers can still return older information. Wait and check again later. Propagation can take up to 48 hours.
When the setup dialog shows the values Maildroppa found, use them to compare the public result with the expected records. A missing result and a wrong result point to different problems:
Deleting and adding the same domain again changes its verification token. If you recreate it, replace the old TXT value with the new value shown by Maildroppa.
If the records have been unchanged for 48 hours and the domain is still not ready, contact support and include:
Do not send passwords, registrar login details, or private account credentials.
Before using a custom Landing Page domain, confirm that:
Once the domain is ready and the page is published, keep both DNS records in place and review the Landing Page Domains page if the public address ever stops working.
Helping founders and creators grow through easy, effective email marketing.
Stripe Climate memberCopyright © 2020-2026 Maildroppa.