Domain Settings

Smartech has a standard process to verify that only authorised owners can send emails from your domain using the Smartech panel. This process of verification is important to ensure that domain names are not misused. Hence, before you can use Smartech for campaigning, you need to get your domain added in Smartech.

Adding the domain is a two-step process.
To validate and authorise email exchange domains, you can use the globally accepted system, called the Sender Policy Framework (SPF), or DKIM, or both.

Email Service Providers (ESPs) like,, etc. validate if the IP address from which email is sent and the sender’s domain belong to the same administrator. If the IP does not exist in the TXT record of sender’s domain (DNS) setting, then the incoming mails from the domain may be treated as SPAM.

As per the SPF system, you are required to add “include:” in the TXT records of the DNS records of your website.

Example: An ecommerce company, ShopCore, wants to send emails with sender domain as using the SMARTECH platform. To be able to do so, ShopCore must first add the TXT record of its website

Sample TXT record: 500 IN TXT “v=spf1 ip4: ~all”

Depending on the internet domain registrar of your website, the authentication process may vary. To learn about how to do this, you may refer to these links:
Manage DNS records in Big Rock
Manage DNS records in GoDaddy
Manage DNS records in c Panel

Multiple Domain:
You can enable multiple domain for your panel by contacting our customer support team

Steps to Add Multiple domain:
Once the multiple domain is enabled to your panel follow the below steps for domain addition:
Step 1: Click on Add, under “Domain Name for Sending Broadcast Email” and Add your Domain

Step 2: Authenticate and verify your domain post adding the record to your DNS setting. Once the verification is successful you can start sending the mail.

Updated 2 months ago

Domain Settings

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.