To verify your domain, you must configure the DNS (Domain Name System) records provided in the Dashboard. These DNS records are necessary to ensure your ownership of the domain and reliable email delivery.
The procedure for adding DNS records to the DNS server for your domain depends on who provides your DNS service. Consult the documentation for your DNS service for specific instructions.
Here are instructions for a few popular providers:
It may take up to 72 hours for DNS record changes to be confirmed. We’ll let you know whether your domain has been verified.
If your domain hasn’t been verified after 72 hours, try the following:
- Correct any typos. You can check your domain records in the Dashboard’s email domain settings by clicking Verify domain to filter issues.
- Make sure you don’t have any records that share the same name as the provided CNAME records. CNAME records must be the only record present for a record name.
- Make sure the added record names don’t include your domain twice. Some providers automatically append DNS record names with the domain name. For example, to create a record with the name bounce.example.com, enter only
bounce in the Name field.
- Check that the DNS records are published. You can verify this by using a DNS lookup tool, which displays the published records for your domain.
If you’re still having trouble verifying your domain, contact your DNS provider.
Purpose of DNS records
Each category of record that needs to be configured has a purpose.
|Stripe proof-of-ownership||TXT||Before you can send email from a domain, we must confirm ownership of the domain you plan to use.|
|Mail From Domain||CNAME||This specifies the source of the message to the receiving email server and the Sender Policy Framework (SPF) policy to allow sending.|
|DomainKeys Identified Mail (DKIM)||CNAME||These allow a mail server to verify that a third party didn’t modify a message in transit.|
Don’t delete the provided DNS records from your domain after the domain is verified. We check these records frequently and notify you if records become invalid or go missing. Correct DNS records within 48 hours. If you don’t, we send customer emails from stripe.com until you resolve the problem.
As a best practice, always configure the Domain-based Message Authentication, Reporting & Conformance (DMARC) record on your domain. This record is especially valuable for preventing impersonation attacks, such as phishing.
The record value specifies a policy that email providers use to decide how to handle fraudulent emails. For example, you can create a DMARC policy that rejects an email that doesn’t pass SPF or DKIM checks. This policy makes it harder for malicious email senders to impersonate you.
If you’re already using this domain to send email, use caution when adding DMARC to ensure that it doesn’t interfere with your existing configuration. Consult an email or IT professional before adding or modifying this record.