Email Security Analysis of broadcom.com

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

Last updated: April 15, 2026

90A

This domain is protected against spoofing

v=spf1 include:broadcom.com._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all

Selectors: google, default, mail, s1, s2

v=DMARC1; p=reject; pct=100; rua=mailto:dmarc_agg@vali.email,mailto:dmarc-admin.pdl-it@broadcom.com; ruf=mailto:dmarc-ruf-admin.pdl@broadcom.com

mx1.smtp.goog, mx2.smtp.goog, aspmx.l.google.com, alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, mx3.smtp.goog, mx4.smtp.goog

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 broadcom.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.