Email Security Analysis of stop.org.nz

Complete verification of stop.org.nz'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 ip4:202.56.36.13 ip4:202.56.36.14 ip4:202.56.36.26 ip4:202.56.36.27 ip4:202.56.36.36 a:smtp.airnet.net.nz include:spf.protection.outlook.com include:spf.AU.exclaimer.net -all

DKIM

OK
Selectors: selector1

DMARC

Warning
v=DMARC1; p=quarantine; rua=mailto:dmarc-rua@stop.org.nz,mailto:dmarc_agg@vali.email; ruf=mailto:dmarc-ruf@stop.org.nz; pct=100;
Read the guide

MX

OK
stop-org-nz.mail.protection.outlook.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 stop.org.nz, run a live analysis.

Analyze stop.org.nz live

Guides to understand these results