Email Security Analysis of virbac.com

Complete verification of virbac.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:_spf.salesforce.com ip4:81.255.76.84 +a:smtp.ehc.adp.com ip4:83.231.220.146 ip4:212.95.71.174 ip4:195.154.120.164 include:amazonses.com ip4:194.51.68.102 ip4:195.115.84.125 ip6:2a01:4f8:221:d6c::2 ip4:88.99.97.95 ip4:208.73.5.244 ip4:213.32.49.231 ip4:167.235.87.185 ip4:167.235.87.182 ip4:213.95.243.154 ip4:213.95.223.20 ip4:52.49.235.189 include:_spf.google.com -all

DKIM

OK
Selectors: google, s1, s2

DMARC

Warning
v=DMARC1; p=none; rua=mailto:virbac.rua@emailsecurity.merox.io
Read the guide

MX

OK
aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt4.aspmx.l.google.com, alt3.aspmx.l.google.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 virbac.com, run a live analysis.

Analyze virbac.com live

Guides to understand these results