Connect your domain
You send from your own domain, so receiving servers need proof that weneed.email may send for it. Setup adds records to your DNS. It never replaces or removes records you already have.
Setup has two rounds of DNS records: first one record to prove you own the domain, then the records that let weneed.email send for it. Between the two, weneed prepares your domain.
Round 1: ownership
Section titled “Round 1: ownership”- Register the exact domain you’ll send from on your project page, for example
yourdomain.com. Use the name only, withouthttps://or a path. - Publish the ownership record. The project shows one TXT record named
_email-verify.yourdomain.comwith a value that starts withemail-verify=. Add it at your DNS provider exactly as shown. - Select Check DNS records, or wait for the automatic check. The page updates by itself when the result arrives.
If someone else manages your DNS, select Download instructions and send them the sheet. It contains only the public records and what each is for, nothing secret.
Between the rounds: weneed prepares your domain
Section titled “Between the rounds: weneed prepares your domain”Once ownership is proven, weneed automatically creates your domain’s signing key and return path. Until then, the
project shows customer_preparation_not_requested
or customer_preparation_pending. You
don’t need to do anything.
Round 2: authentication records
Section titled “Round 2: authentication records”When preparation is done, the project lists each record with its purpose, host, type and expected value:
- DKIM: signs your messages so receivers can verify them.
- Bounce MX on a dedicated return-path subdomain: receives bounce reports for your messages.
- SPF on the same return-path subdomain: authorizes the sending servers.
- DMARC on
_dmarc.yourdomain.com: tells receivers what to do with mail that fails checks. If you already have one, keep it. weneed.email never changes it for you.
Publish them, then select Check DNS records. Keep the ownership TXT record as well; it’s checked again.
Worked example
Section titled “Worked example”For the domain example.com, Control lists records like these. Copy the values from Control:
the selector, signing key, mail server and IP address are specific to your domain.
| Purpose | Type | Name | Value |
|---|---|---|---|
| Ownership | TXT | _email-verify.example.com |
email-verify=… |
| DKIM signing | TXT | <selector>._domainkey.example.com |
v=DKIM1; k=rsa; p=… |
| Bounce routing | MX | bounce.example.com |
Priority 10, then the server name shown |
| Envelope SPF | TXT | bounce.example.com |
v=spf1 ip4:… -all |
| Existing DMARC policy | TXT | _dmarc.example.com |
Keep yours. If you have none, Control suggests one. |
The SPF and MX records go on bounce.example.com, not on example.com, so they don’t touch your
existing receiving mail or SPF record. If your DNS provider adds the domain automatically, type only
the part before it: _email-verify, <selector>._domainkey, bounce, _dmarc. Once ownership is
verified, Control shows the short names for your DNS zone.
Checks
Section titled “Checks”- Ownership and authentication are checked automatically. The project shows the last and the next check for each.
- While a record isn’t right yet, checks repeat, first quickly, then up to every 30 minutes. Once everything passes, it’s checked again every 20 minutes.
- You can request a check yourself, at most once every 30 seconds per domain and 20 times an hour per organization.
- A result older than 24 hours counts as stale. It no longer counts until a new check passes.
Each record shows its state as a symbol and a word:
| State | Meaning |
|---|---|
| ✓Verified | Found, with the expected value. |
| ✕Not found yet | Not visible yet. Add the record; checks continue. |
| ✕Value does not match | A record exists with a different value. Replace it with the value shown. |
| ✕Wrong name | The value was found under another name, often because the domain was added twice. |
| ↺Needs a fresh check | The last result is older than 24 hours. It no longer counts until a new check passes. |
| ○Preparing record | weneed is still preparing this record. You don’t need to do anything. |
| ○Not checked yet | No check has run yet. |
Show what needs fixing opens the details of every record that hasn’t passed.
Under Next actions, the project says what’s still open and whether it’s yours or weneed’s to do. Each reason code has a page in Troubleshooting. Warnings, such as a DMARC policy set to monitoring only, are listed separately.
When every record passes, Control shows Continue to credentials. Invited alpha accounts then receive sending access automatically. See How sending becomes available.
Changing or removing a domain
Section titled “Changing or removing a domain”Open Change or remove this domain under the domain. Both need a recent authenticator check in Account security.
- Get a new ownership record: issues a new ownership value. The current proof stops counting until the new record is found.
- Remove domain: type the domain to confirm. This is permanent. The old ownership value and records are no longer valid; remove them from your DNS. Register the domain again to start over.
Common mistakes
Section titled “Common mistakes”- Host name doubled. Many DNS providers append your domain automatically. If the dashboard shows
_dmarc.yourdomain.com, you may need to type only_dmarc. - A second SPF record. A name may have only one SPF record. Merge instead of adding. See Multiple SPF records.
- Proxy enabled. Records added with a proxy (for example Cloudflare’s orange cloud) must be set to DNS only.
- Removing existing records. Keep your receiving MX, SPF and DMARC records. Setup only adds.
- Impatience. Some providers take minutes to hours to publish changes.