Email Security Analysis of sonova.com

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

Last updated: April 15, 2026

73B
This domain is vulnerable to spoofing

SPF

OK
v=spf1 include:sonova.net include:spf.3uu.de include:spf.qb-feedback.com ip4:155.56.221.13 ip4:155.56.221.14 ip4:5.102.145.30 ip4:92.42.235.0/24 ip6:2a06:c01:1:1102::30 ip4:5.102.151.229 ip6:2a06:c00::56fd include:spf.mandrillapp.com include:_spf.tivian.com -all

DKIM

OK
Selectors: selector1, selector2, mandrill, s1, s2

DMARC

Warning
v=DMARC1; p=none; rua=mailto:gthwor3p38@rua.powerdmarc.com; ruf=mailto:gthwor3p38@ruf.powerdmarc.com; sp=none; fo=0:1:d:s
Read the guide

MX

OK
mail101.sonova.com, mail102.sonova.com, mail103.sonova.com, mail104.sonova.com

MTA-STS

Missing

No record found

Read the guide

Recommendations

  1. 1Change your DMARC policy from p=none to p=reject to block spoofing

    With p=none, your DMARC record only monitors — it doesn't actually block spoofed emails. Attackers can still send emails as your domain and they'll be delivered normally. Switching to p=reject instructs receiving servers to drop fraudulent messages before they reach the inbox.

  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.

Need help securing your domain?

If you're not sure how to apply these fixes, get in touch and we'll help you out.

Contact us

Run a live analysis

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

Analyze sonova.com live

Guides to understand these results