Add these TXT records at your DNS host so mail you send through SMTPS.IO is authenticated as coming from your own domain. Enter your domain to fill them in.
Use the root domain you send From — for you@mail.example.com, enter mail.example.com.
Authorises our relay to send mail for your domain. Without it, receivers are far more likely to reject or spam-folder your mail.
A domain may only have one SPF record. If you already have one, add include:spf.smtps.io to it rather than creating a second.
Signs your messages so receivers can prove they were not altered in transit.
This is our shared signing key — publish it as-is and your mail is signed straight away. If you'd rather have a key only your domain uses, generate one in the dashboard; it replaces this record.
Add your domain in the dashboard to generate the key — it shows the exact value to paste, including the selector if it differs from default.
Tells receivers what to do when SPF and DKIM fail, and where to send reports. Gmail and Yahoo require it for bulk senders.
Start with p=none, which only monitors. Once the reports show your mail passing, tighten it to p=quarantine and then p=reject.
DNS changes are not instant. Most hosts publish within minutes, but allow up to 48 hours before treating a record as broken — and leave the TTL at your provider's default.
Not sure whether your records are live? Check them with our email tools, or contact us and we'll look with you.