Email Security Analysis of stripe.com

Complete verification of stripe.com's SPF, DKIM, DMARC, and MTA-STS records. Find out if this domain is protected against email spoofing.

Last updated: April 14, 2026

90A

This domain is protected against spoofing

v=spf1 ip4:198.2.180.60/32 ip4:13.111.2.227/32 include:spf1.stripe.com include:greenhouse-outbound-mail.stripe.com include:_spf.qualtrics.com ~all

Selectors: google, mandrill, s1, s2, zendesk1, zendesk2, cm

v=DMARC1; p=reject; pct=100; fo=1; rua=mailto:dmarc-reports@stripe.com; ruf=mailto:dmarc-forensics@stripe.com;

aspmx.l.google.com, alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, aspmx2.googlemail.com, aspmx3.googlemail.com

Missing

No record found

1Add MTA-STS to enforce TLS encryption for incoming emails
Without MTA-STS, an attacker performing a man-in-the-middle attack can downgrade the connection between mail servers to plaintext, intercepting emails in transit. MTA-STS tells sending servers to only deliver via TLS with a valid certificate, preventing downgrade attacks.

Run a live analysis

The results above are updated daily. For an instant check of stripe.com, run a live analysis.

Understand how SPF defines which servers are authorized to send emails for a domain.

Discover how DKIM cryptographically signs your emails to guarantee their authenticity.

Learn how DMARC orchestrates SPF and DKIM to protect your domain.

Learn how MTA-STS enforces TLS encryption to protect your emails in transit.

Compare the three protocols and understand how they work together.