Set up your sending domain
Your marketing emails are sent from a domain you own, such as mail.yourcompany.com. Before you can send a campaign,
that domain has to be set up and verified. You do this under Email Marketing → Sending. You need permission to
manage the sending identity.
Use a subdomain like mail.yourcompany.com rather than your main domain. If marketing email ever runs into a
spam problem, your everyday email isn’t affected. Free email domains such as gmail.com can’t be used.
1. Add the domain
Under Add your sending domain, enter the domain and choose who your emails are from:
- From name, for example your company name.
- From address, the part before the @, for example
helloornews. Avoidnoreply. - Reply-to address (optional), if replies should go somewhere else.
Click Add domain. Appneck sets the domain up with its email provider and shows the provider’s DNS records in the table, usually right away. If the domain shows Being prepared instead (“Our team is preparing your domain — usually within one business day.”), Appneck’s team is finishing the setup by hand and the records appear when it’s done. Your organization can have one sending domain at a time.
2. Add the ownership record — right away
The records table already shows one record, the Ownership record:
| Type | Name | Value |
|---|---|---|
| TXT | _appneck-verify.<your domain> | appneck-verify= followed by 32 letters and digits |
It proves that you own this domain. Its value is unique to your organization and is never reused. Add it at the company that runs your domain’s DNS, such as Cloudflare or GoDaddy, exactly as shown. Use the copy buttons. Then click Check DNS. The record gets a ✓ when Appneck finds it.
Keep this record in place for as long as you send from the domain. Your domain can’t be verified without it, and sending stops if it is removed later.
3. Add the email provider’s records
When the team is done, more records appear in the table, below the ownership record. They are usually a TXT record at the domain itself, one or two DKIM records (CNAME or TXT) and a DMARC record. Add each one exactly as shown, then click Check DNS.
Each record shows:
- ✓ Appneck found it.
- ✗ It isn’t there yet, or its value is different.
- ? The lookup itself failed. Try again in a minute.
DNS changes can take from a few minutes to a few hours to appear. Appneck also checks every 30 minutes.
Already have a DMARC record? Then the DMARC row shows ✓ with “Your existing DMARC record is fine — do not add a second one.” A domain may have only one DMARC record. Two make both invalid.
4. Verified
When every record has a ✓ (the ownership record included), the status shows DNS found — confirming. Appneck then confirms the domain with the email provider, usually on the next check (at most one business day), and it turns Verified.
To see an email arrive, open any template and send a test to your own address. It goes out from your new domain.
Before your first campaign
The Ready to send checklist on the Campaigns page lists what is still missing. Usually that is:
- a verified sending domain;
- a postal address under Email Marketing → Brand (every marketing email must show one);
- Email marketing included in your plan.
Your first campaign is also reviewed by Appneck before it goes out.
If something changes later
- DNS records missing. Appneck checks a verified domain every day. If a record disappears, sending stops and your organization’s owners get an email. Put the records marked ✗ back exactly as shown and click Check DNS. Sending resumes as soon as they’re found.
- Waiting for Appneck to confirm. Sometimes Appneck has to confirm a verified domain again, for example after a change on its side. Sending from it waits until that’s done. You don’t need to do anything.
- Sending is temporarily limited by the platform. Appneck can limit how much the whole platform sends in a day. A paused campaign carries on by itself when the limit resets.
- Changing the From name or address. Edit From settings on the same page. Messages not yet sent use the new From. Don’t revoke the domain to fix a typo.
- Revoking the domain stops all sending from it at once. To use the domain again, add it again: it gets a new ownership record, which you need to publish again.