Email Security Analysis of tsa.com

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

Last updated: April 14, 2026

82B
This domain is protected against spoofing

SPF

OK
v=spf1 include:spf.ess.barracudanetworks.com include:mailsenders.netsuite.com include:sent-via.netsuite.com include:mail.zendesk.com include:_spf.safewebservices.com include:md02.com include:spf.protection.outlook.com ip4:99.69.170.9/29 ip4:24.197.13.54/32 ip4:64.132.201.93/32 ip4:74.203.211.13/32 ip4:207.67.44.189/32 ip4:3.145.232.16/28 -all

DKIM

OK
Selectors: selector2, k1, s1, s2, zendesk1, zendesk2

DMARC

Warning
v=DMARC1; p=quarantine; fo=1; rua=mailto:rua+tsa.com@dmarc.barracudanetworks.com; ruf=mailto:ruf+tsa.com@dmarc.barracudanetworks.com
Read the guide

MX

OK
d154800a.ess.barracudanetworks.com, d154800b.ess.barracudanetworks.com

MTA-STS

Missing

No record found

Read the guide

Recommendations

  1. 1Upgrade your DMARC policy from p=quarantine to p=reject for full blocking

    With p=quarantine, spoofed emails are sent to spam instead of being blocked outright. Some recipients still check spam folders, and sophisticated attacks can be flagged as legitimate by users. p=reject ensures fraudulent emails never reach any folder.

  2. 2Add 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 tsa.com, run a live analysis.

Analyze tsa.com live

Guides to understand these results