Lab report — email & DNSscan/winsauer.cc

winsauer.cc

Scanned Oct 11, 2026 13:54 UTC · 7 checks · public report

Health grade

Solid base — two policy steps remain.

BGrade B

2 warnings3 passing2 not checkedNot-checked is by design — details inline below.

In one line

Can winsauer.cc be spoofed?

winsauer.cc publishes DMARC with p=none — spoofed mail is monitored but not blocked.

WarningSPF

Finding 01

SPF ends in '~all' (softfail) rather than '-all' — acceptable for DMARC (non-pass either way); hardening to '-all' is optional and only safe once every legitimate sender is in the record

2 of 10 DNS lookups used

AI explanation

Your SPF setup is working, but it uses a softer “fail” setting at the end, which means other mail servers are told to treat unknown senders with caution rather than reject them outright. This matters because it can leave a bit more room for spoofed email to slip through, though DMARC can still work with it. The fix, if you want stricter protection, is to switch to the harder reject setting only after you are sure every legitimate sender is included.

Current SPF

v=spf1 include:mailbox.org ~all

All findings — worst first

WarningDMARCDMARC is recorded but p=none (monitoring only — no protection)
Start monitoring winsauer.cc →
- no enforcement record is recommended yet — a scan alone could not confirm that your mail aligns (valid SPF and a DKIM signature), and moving off p=none without that evidence risks silently blocking legitimate mail. Gather aggregate-report evidence first, then step up: evidence before enforcement
- p=none only monitors — it does not block spoofing
- no np= tag: non-existent subdomains fall back to sp/p — RFC 9989 §4.7's np=reject can protect them now
AI explanation
Your domain has DMARC set up, but it is only in monitoring mode, so it is not actively blocking spoofed or fraudulent email. This matters because attackers can still try to send mail that looks like it came from your domain, which can hurt trust and deliverability. The fix is to change DMARC from monitoring to an enforcement mode so receivers know what to do with messages that fail authentication.
Current DMARC

Email me this report

One send: the full report — every finding and fix — lands in your inbox, with a free account waiting. Opening it signs you in and starts a 14-day Monitor trial. No card, and you can unsubscribe in one click.

Domain owner? Re-scan any time — or email hello@dnsdoctor.dev to have this page removed.

Running your DNS diagnostic…

Can winsauer.cc be spoofed?

SPF ends in '~all' (softfail) rather than '-all' — acceptable for DMARC (non-pass either way); hardening to '-all' is optional and only safe once every legitimate sender is in the record

All findings — worst first