Email Security Analysis of hnry.co.nz

Complete verification of hnry.co.nz'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

v=spf1 include:mailgun.org include:_spf.google.com include:servers.mcsv.net -all

Selectors: google, k1

Warning

v=DMARC1; p=none; sp=none; rua=mailto:re+e558b7f7c066@inbound.dmarcdigests.com; aspf=r; pct=100

aspmx.l.google.com, alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, aspmx3.googlemail.com, aspmx2.googlemail.com

Missing

No record found

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

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

Run a live analysis

The results above are updated daily. For an instant check of hnry.co.nz, 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.