Skip to main content
If you’re building a platform that sends email on behalf of your own users, you might want to allow your customers to use their own domains for sending. The core requirements for authenticating a domain for sending we described here still apply, and you’ll be in charge of exposing the domain verification flow to your end users within your UI.

​
Verify your customers’ domains for sending

That process typically looks like this:
  1. Your customers choose the domain they want to send from
  2. You use the Domains API to add your customer’s domain as a new sending domain
  3. You display the DNS records generated by Helo to your end user
  4. Your customer adds those records to their DNS provider
  5. Helo verifies the domain once the records appear — and once that’s done, your user can start sending via your platform using their own sending domain.

​
Best practices for a smooth domain verification process for your end users

Working with DNS records can be an intimidating experience — especially if the end users of your platform are less tech-savvy. Here’s what you can do to make the experience as painless as possible for your users:

​
Provide DNS-provider specific instruction

DNS providers have different workflows for DNS updates, so it might be helpful for you to add instructions for the most popular ones to your end user documentation.

​
Create a “send instructions to a coworker” flow

Is the human who’s using your platform unlikely to be the human to have access to their domain’s DNS? A “send instructions to a coworker” flow will make it easier for them to pass the DNS record instructions along to the colleague who does.

​
Provide clear user feedback in your domain verification UI

Showing your users whether the domain verification process was successful (or not) will help them gain confidence (and reduce support questions on your end). You can use our Domains API endpoint to fetch a domain’s verification status to provide feedback to your users.