Why verify your email domain?
Admins and Department admins can configure and users can send emails from Zoho Meeting using their company's email address. This can help companies improve the authenticity and credibility of their message. However, when a third-party service like Zoho Meeting sends out an email on your behalf, there's a chance that these emails may be considered spoofing, phishing attempts and marked as spam by the recipient’s email services based on their DMARC (Domain-based Message Authentication Reporting and Conformance) policy. To handle situations like this, we have introduced email domain verification in Zoho Meeting using Domain Keys Identified Mail (DKIM) method.
What is DKIM?
DKIM is an email authentication method that helps companies take responsibility of their message in transit, and mailbox providers to check the source of each message using cryptographic techniques. For each email, DKIM will attach a signature during the transmission to verify the authenticity of the message source. This way, companies can prevent spammers from sending out emails impersonating them, and enable third-party services to send emails on their behalf without them being marked as spam.
How DKIM works in Zoho Meeting?
A public key will be published as a TXT record for your domain's DNS Manager, and every outgoing email from Zoho Meeting will have a signature attached to its header, generated using the private key of your domain.
Your recipient's email server will check the email header of each message with the public key stored in your DNS record every time.
This will help email services to verify your domain ownership.
Emails will land in the spam folder of your recipient's mailbox if this verification failed.
For example, if malcolm@zylker.com is sending a document to frida@zoho.com using Zoho Meeting, the email from Malcolm will have a signature added to its header (generated using the private key of the domain-zylker) and the public key of the domain - zylker will be already published as a TXT record in the zylker's DNS Manager. Frida's email server will validate the email's legitimacy with Malcolm's email header and the public key stored in Malcolm's DNS record. If the verification is successful, the email sent by Malcolm will land into Frida's inbox instead of being classified as SPAM.

To verify your email domain ownership using DKIM in Zoho Meeting, you need to complete the three steps as mentioned below:
Add domain name
Add TXT record
Verify domain ownership
Add domain name
This step is necessary for Zoho Meeting to recognize your domain, and generate a key (hostname, value) for that domain.
Add TXT record
Login to your domain providers's account. (For example, GoDaddy, namecheap, among others) where your domain's name server is pointed.
Access your domain and navigate to it's DNS page. Select the TXT Method tab in the Domain Verification page.
Create a TXT record in your DNS with the title as the host name. You can copy the host name from Host Name field in Zoho Meeting.
In the TXT record value, You should paste the content you copied from the Host Value field in Zoho Meeting.
Save the TXT record in the DNS Manager.
Go to Zoho Meeting and click Verify

Note:
Verify domain ownership
Ensure you have completed adding the TXT record in the DNS Manager.
Click the Verify button in the Domain Management tab in Zoho Meeting.
If the entry has been added correctly, your domain would be marked as verified and emails sent from Zoho Meeting will be signed and verified using the key pairs.
You should not remove this TXT record from your domain hosting console as long as you continue to use that email address in Zoho Meeting. If not your email domain will be marked as not verified again and your emails may land in spam.