To verify your domain, you need to sign in to your domain host like
Cloudflare - If using DNS or domain
Once you login to you domain DNS manager setup the below 4 records.
Type: TXT record
Value: v=spf1 a mx include:saino.io ~all
For example, if your domain already has the record: v=spf1 a mx include:_spf.google.com ~all, then you would just add: include:saino.io
The final record would look like this: v=spf1 a mx include:_spf.google.com include:saino.io ~all
Type: TXT record
Type: CNAME record
Type: TXT record
Note - The above setting will not necessarily bounce email, but indicate to the recipient server they should consider quarantining it (Store in junk or spam folder).
Now go to Saino First Email App, Under Manage section and visit Varify Domain Tab and click on verify on your configured domain.
It can take from 2 Minutes to 48 hours to fully start working. It depends on your domain host or DNS provider. This period, called propagation, is the projected length of time it takes for root name servers and cache records across the entire web to be updated with your website's DNS information.
Once all records updated successfully you are ready to send emails.
This section will help you with understanding during domain verification.
An SPF (Sender Policy Framework) record is in place to identify which mail servers are authorized to send mail for a given domain. It is used to prevent spamming. It helps the receiver mail server to authenticate the message.
This helps you, as an email sender, the ability to specify which email servers are permitted to send an email on behalf of your domain.
DKIM (DomainKeys Identified Mail) allows receiving servers to confirm that mail coming from a domain is authorized by the domain's administrators. This email authentication technique that allows the receiver to check that an email was indeed sent and authorized by the owner of that domain.
Saino First tracks - opens, clicks, unsubscribes, complaint etc. To do the same we must rewrite links and use web pages links. Setting up a "tracking record" brands these rewritten links and pages with your own custom domain. so finally all tracking links sent via your own custom domain.
DMRC (Domain-based Message Authentication) allows a sender's domain to indicate that their emails are protected by SPF and/or DKIM, and tells a receiver server what to do if neither of those authentication methods passes – such as junk, bounce the email, reject the message or quarantine it. Reporting & Conformance is an email authentication protocol that is built on top of SPF and DKIM protocols.
DMARC removes the guesswork from the receiver’s handling of these failed emails, limiting or eliminating the user’s exposure to potentially fraudulent & harmful emails. DMARC also provides a way for the email receiver to report back to the sender server about emails that pass and/or fail DMARC validation.
A mail exchanger record (MX record) specifies the mail server responsible for accepting email messages on behalf of a domain name.
For most of our users, you will not required to be adding or changing any MX records in your domain's DNS. The only reason why you would change or add an MX record for use of Inbound Email Notifications. It is not required for sending the outbound emails.