Setting up a custom domain ensures your emails reach inboxes and aren’t flagged as spam. Sequenzy requires just 3 DNS records to verify your domain.
You can start sending emails immediately using the built-in sequenzymail.com domain without any DNS setup. However, this shared domain has shared reputation across all users, so emails may land in spam. For best deliverability, set up a custom domain.
When you send an email, receiving mail servers (Gmail, Outlook, etc.) check if the email is legitimate. Without a verified custom domain, your emails may:
Land in spam folders
Be rejected entirely
Damage your sending reputation
Domain verification proves:
You own the domain - Only someone with DNS access can add the required records
You authorize Sequenzy to send on your behalf - The records explicitly list Amazon SES as an authorized sender
Email authentication uses multiple protocols working together. When a receiving server gets your email:
SPF Check - “Is this server allowed to send for this domain?” → Looks up TXT record on bounce subdomain
DKIM Check - “Was this email modified in transit?” → Verifies cryptographic signature using public key from TXT record
DMARC is an additional layer that tells receiving servers what to do when authentication fails. While recommended for domain protection, it’s not required for domain verification in Sequenzy.
DKIM adds a digital signature to every email. Sequenzy generates a unique key pair for your domain — outgoing emails are signed with the private key, and receiving servers verify using the public key published in this record.
DMARC is not required for domain verification, but we recommend setting it up for better deliverability and domain protection. DMARC tells receiving servers what to do when authentication fails and where to send reports.
We strongly recommend sending from a subdomain (e.g., mail.example.com) rather than your root domain. This protects your domain reputation and isolates any deliverability issues.
