Your company’s Stripe account sends receipts, invoices and payment emails from your own domain instead of stripe.com, and this record proves you own it. Stripe checks it often: if it breaks and is not fixed within 48 hours, customer emails go back to coming from stripe.com.
Name: @ (the domain itself) Type: TXT Value: stripe-verification=71f63b4237a1a7a1b990de5d87b1a0c517a0079a1e368989651f62b0c2756bf4
| Added by | Stripe — custom email domain |
| Can it be deleted? | Keep it — the service checks it again, and removing it undoes the verification |
| Goes with | A Mail-From CNAME (often bounce), DKIM CNAMEs and a DMARC record |
| Several records? | One per Stripe account using the domain |
Look for it on your domain
Enter a domain: we look up its TXT records and say whether this one is there — naming every other record we recognise.
What it is for
Stripe’s custom email domain needs a proof-of-ownership TXT record plus mail records so the emails authenticate. It is not payment method domain registration for Apple Pay or Google Pay, which needs no DNS record, and not a Checkout custom domain, which uses a CNAME.
Why it is on your domain
- Someone set up a custom email domain in the Stripe Dashboard.
Can you delete it?
Keep it. Stripe says not to delete the records after verification: it checks them frequently, notifies you if one breaks, and after 48 hours sends customer emails from stripe.com instead.
Sources
Checked on 26 September 2026 against these official sources:
- Custom email domain — docs.stripe.com
- Register domains for payment methods — docs.stripe.com
- Use your custom domain — docs.stripe.com