Email Security Analysis of booking.com
Complete verification of booking.com's SPF, DKIM, DMARC, and MTA-STS records. Find out if this domain is protected against email spoofing.
Last updated: April 14, 2026
SPF
OKv=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com -allDKIM
OKSelectors: mandrill, s1, zendesk1, zendesk2DMARC
OKv=DMARC1; p=reject; rua=mailto:dmarc_rua@emaildefense.proofpoint.com,mailto:booking@dmarc.postmastery.eu; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.comMX
OKmxb-0032a201.gslb.pphosted.com, mxa-0032a201.gslb.pphosted.comRecommendations
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 booking.com, run a live analysis.
Analyze booking.com liveGuides to understand these results
SPF Guide
Understand how SPF defines which servers are authorized to send emails for a domain.
DKIM Guide
Discover how DKIM cryptographically signs your emails to guarantee their authenticity.
DMARC Guide
Learn how DMARC orchestrates SPF and DKIM to protect your domain.
MTA-STS Guide
Learn how MTA-STS enforces TLS encryption to protect your emails in transit.
SPF vs DKIM vs DMARC
Compare the three protocols and understand how they work together.