> ## Documentation Index
> Fetch the complete documentation index at: https://docs.notifly.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Send email

> Register a sending address or verify a sending domain before sending email with Notifly.

> [!WARNING]
>
> Send only to valid addresses. Verify addresses first with a code, confirmation link, or similar method. Sending to invalid addresses increases bounces and can hurt your domain's reputation. Mail providers may then filter or block your messages.
>
> See the [Notifly email monitoring policy](#notifly-email-monitoring-policy) for details on sending restrictions.

## Register a sending address or domain

Open **Settings > Channel Settings > Email**, then choose how to register your sender:

* Choose **Registered Sending Domains** to verify a domain and use sending addresses on that domain without verifying each one.
* Choose **Registered Sending Emails** to verify an individual address without verifying its domain.

![Registered sending domains and email addresses in email settings](https://mintcdn.com/notifly/0_mniRtlC78csfem/images/i18n/en/email/email-settings.png?fit=max\&auto=format\&n=0_mniRtlC78csfem\&q=85\&s=b0c3d1d581fbc93820658823732ce106)

### 1. Register an individual sending address

Under **Registered Sending Emails**, open the form to add an address. Enter the address and click **Verify and Register**. Follow the verification link sent to the address, if prompted.

### 2. Register and verify a sending domain

For bulk email, send from a domain your company manages. A familiar address helps recipients recognize your service, and you can authenticate the domain yourself.

1. Use a sender name and address that customers can recognize.
2. Authenticate your domain so receiving mail providers can verify your messages.

If you send from an unverified domain, the recipient may see a warning like this.

![A recipient warning for an email from an unverified sending domain](https://mintcdn.com/notifly/0_mniRtlC78csfem/images/i18n/en/email/email-warning.png?fit=max\&auto=format\&n=0_mniRtlC78csfem\&q=85\&s=2c473b61a357399f1bf3ff10d6242240)

Notifly recommends setting up SPF and DKIM to authenticate your domain. These records help prevent the warning shown above and reduce the chance that your mail is marked as spam.

> [!NOTE]
>
> *Notifly lets you register an individual sending address without verifying the domain. Receiving providers may still require domain authentication. Check their rules before sending in bulk.*

1. Under **Registered Sending Domains**, open the form to add a domain. Enter your domain, such as `example.com`, and click **Register**.

![Form for registering a sending domain](https://mintcdn.com/notifly/0_mniRtlC78csfem/images/i18n/en/email/email-domain-register.png?fit=max\&auto=format\&n=0_mniRtlC78csfem\&q=85\&s=254e3336ef1e560c3517252e6948f6e6)

2. After you register the domain, select it to view its details.

![Email domain verification settings](https://mintcdn.com/notifly/0_mniRtlC78csfem/images/i18n/en/email/email-domain-verification.png?fit=max\&auto=format\&n=0_mniRtlC78csfem\&q=85\&s=29effca3bb4e1d65c0d537452c06c50b)

![Details for a registered sending domain](https://mintcdn.com/notifly/0_mniRtlC78csfem/images/i18n/en/email/email-dkim-register.png?fit=max\&auto=format\&n=0_mniRtlC78csfem\&q=85\&s=71666f0a5c3c2abec5f6fd488dc87968)

3. Choose a custom subdomain such as `mail`. Click **Save**, then refresh the page to see the five DNS records used for verification.

![DNS records for email domain verification](https://mintcdn.com/notifly/0_mniRtlC78csfem/images/i18n/en/email/email-domain-verification-2.png?fit=max\&auto=format\&n=0_mniRtlC78csfem\&q=85\&s=afdc1a4af3e4c20f45007d43c0bea084)

4. Add the five records to the DNS settings on your domain host's website. See the guides for common providers below.

* [Squarespace DNS records for email](https://support.squarespace.com/hc/en-us/articles/31120985010957-Add-DNS-records-for-email)
* [Amazon Route 53 DNS settings](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/rrsets-working-with.html)
* [Cafe24 DNS settings (Korean)](https://help.cafe24.com/cs/cs_faq_view.php?idx=3766)
* [Gabia domain settings (Korean)](https://customer.gabia.com/manual/domain/287/1201)
* [Whois DNS settings (Korean)](https://cs.whois.co.kr/faq/?p=list\&service=1)

5. When verification finishes, the domain status turns green in Notifly settings. Open the domain details and confirm that the DKIM and SPF statuses show **SUCCESS**.

![Green status for a verified sending domain](https://mintcdn.com/notifly/0_mniRtlC78csfem/images/i18n/en/email/email-domain-status.png?fit=max\&auto=format\&n=0_mniRtlC78csfem\&q=85\&s=3b0db995db8ad21af7f0e96eedbbebb3)

![DKIM and SPF both show SUCCESS for the verified domain](https://mintcdn.com/notifly/0_mniRtlC78csfem/images/i18n/en/email/email-domain-success.png?fit=max\&auto=format\&n=0_mniRtlC78csfem\&q=85\&s=e522e1fdb387e600adaa571846c40729)

6. Add your sending address under **Registered Sending Emails**, for example [user@example.com](mailto:user@example.com). If you've verified the domain, Notifly registers the address immediately without a separate verification step.

## Notifly email monitoring policy

Notifly monitors email bounce rates to protect its sending infrastructure and reduce the risk that customer domains are flagged as spam. Notifly may restrict sending if the bounce rate is too high.

The bounce rate is the number of reported bounces divided by the number of sends.

* If a recipient server returns an email, Notifly may add the affected user to **Excluded Users** for email and skip the user in later email sends.
* Notifly does not send email to addresses at @kakao.com, @daum.net, @hanmail.net, or @nate.com.

## FAQ

> [accordion] What are SPF and DKIM?
>
> SPF (Sender Policy Framework) authorizes sending servers for the envelope sender domain. DKIM (DomainKeys Identified Mail) signs messages so the receiving provider can verify the signing domain. If you send from [user@example.com](mailto:user@example.com), the sender address the recipient sees can differ from the envelope sender. Configure SPF and DKIM for the domain you use with Notifly.

> [accordion] Why is my domain still unverified after setting up SPF and DKIM?
>
> DNS changes can take up to 48 hours to propagate. To check whether the records are correct before then, contact the Notifly team.

> [accordion] Why is the Email complaint count high?
>
> **Email complaint** counts how many times recipients reported your messages as spam.
>
> * If you send too many emails in a short time, use [Throttled Delivery](https://docs.notifly.tech/en/user-guide/campaigns/campaign-segments/segment.md#throttled-delivery) to space out delivery.
> * If your email is very short or contains only an external link, include a short summary of the linked content in the body alongside the link.
> * If your sender name, email address, and message content don't match, mail providers may mark the email as spam. Use a sending domain that matches your service name.

> [accordion] Can I send to Apple private email relay addresses?
>
> To send to an Apple private email relay address, register your sending domains or addresses with Apple and meet its sender authentication requirements. Ask Notifly to confirm the settings for your sending domain.
>
> If you publish a DMARC record for your verified domain, the following example configures reporting only.
>
> * Type: TXT
> * Name: \_dmarc.yourdomain.com (for example, \_dmarc.example.com)
> * Value: `v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com; ruf=mailto:forensic-reports@example.com; pct=100`
> * Set the `rua` and `ruf` values to valid email addresses. Replace the example addresses with your own.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.