WispBinderResults below are dated; this page is updated when results change.
We check ourselves
We run the same checks on ourselves that we offer to you: the outside-in domain check on our own domain, and the same Windows check script you run, on the computer that handles client files. Every result shows the date it was observed.
Why we show our own exceptions
A page called "We check ourselves" that hid its own exceptions would contradict itself. We keep two exceptions on our own computer, and we list them below with what we do instead. That is the same method we ask of you: a finding, plus a written control that replaces it, rechecked on a schedule.
1. Our own domain: wispbinder.com
Checked with our own free domain check (public DNS only) on 4 Nov 2026, 14:47 UTC. Summary shown by the check: 2 look good, 0 need attention, 1 could not be checked.
| Item | Result on 4 Nov 2026 |
|---|---|
| Email provider | Looks good MX records point to mx1.hostinger.com and mx2.hostinger.com (our provider, Hostinger). The check names only Google Workspace and Microsoft 365, so it shows "another email provider". |
| SPF | Looks good One record, v=spf1 include:_spf.mail.hostinger.com ~all; 3 of 10 DNS lookups. |
| DMARC | Looks good Policy p=quarantine: fake mail using our domain is sent to spam. Reports go to dmarc@wispbinder.com. From 31 Oct to 4 Nov 2026 the policy was p=none while we read the first reports; we plan to move to p=reject after a few weeks without problems. |
| DKIM | Could not be checked Our provider signs with selectors (hostingermail-a/b/c) that the check does not try, so the check cannot see them. The check's limits apply to us as well. Separately, the receiving mailbox verified the DKIM signature of a test email from wispbinder.com on 4 Nov 2026 (shown in its message headers). |
| DNSSEC | Optional Our DNS answers are not signed yet. |
| MTA-STS and TLS reports | Optional Not set up. |
2. The computer that handles client files
Checked with the same Windows check script clients run (version 0.2.2-draft). First check 30 Oct 2026; rechecks after fixes on 31 Oct and 1 Nov 2026.
| Check | 30 Oct 2026 | 31 Oct – 1 Nov 2026 |
|---|---|---|
| W02 Disk encryption | NOT DETECTED on 30 Oct 2026: drive encrypted, but no key protector, so protection was off | DETECTED on 31 Oct 2026: protection on, recovery key stored away from the computer |
| W08 Accounts require a password | NEEDS WRITTEN CONFIRMATION on 30 Oct 2026 ("password not required" flag) | DETECTED on 31 Oct 2026 |
| W15 Remote-access software | Several remote-access tools installed (30 Oct 2026) | One remote-support tool kept on 31 Oct 2026; its unattended access is OFF since 1 Nov 2026 (no unattended password set). Remote sessions require someone at the computer to accept (see exceptions) |
| Peer-to-peer file-sharing software | Installed (30 Oct 2026) | Removed (31 Oct 2026) |
| W16 SMBv1 off | DETECTED on 30 Oct 2026 | DETECTED on 31 Oct 2026 |
| W04 Firewall, W05 Updates | Result not kept in our records for 30 Oct 2026 | DETECTED on 31 Oct 2026 |
| W06 Screen lock | NEEDS WRITTEN CONFIRMATION on 30 Oct 2026 (lock set through sleep settings, which the script does not read) | DETECTED by the script on 1 Nov 2026 (inactivity lock set to 15 minutes) |
| W03 Antivirus | NEEDS WRITTEN CONFIRMATION on 30 Oct 2026 (third-party antivirus; Windows lists it as on, but that is an unofficial reading) | NEEDS WRITTEN CONFIRMATION on 31 Oct 2026. We confirmed manually on 1 Nov 2026 that protection is on and up to date. We do not turn an unofficial reading into "Detected". |
Exceptions we chose to keep, and what replaces them
Written down and rechecked monthly.
| Exception | Why | What we do instead |
|---|---|---|
| One remote-support tool stays installed | Needed for other work on this computer | Unattended access is OFF: no unattended password is set, so every remote session requires someone at the computer to accept it (verified 1 Nov 2026, screenshot of the settings kept as evidence) |
| The daily account has administrator rights | Software development work on this computer needs them often | Windows asks for confirmation on every change (User Account Control set to "Always notify", verified 1 Nov 2026); client files will be kept in one folder on the encrypted drive only (we have no client files yet) |
Working rules
- The check script is rerun on this computer every month.
- Raw check results from clients are deleted within 30 days after the report is delivered.
- No peer-to-peer file-sharing software.
- Two-factor authentication on our mailbox, our hosting and email admin account, our code hosting account and our website hosting account (verified 1 Nov 2026).
3. The script you download
- Every published version of
wisp-check.ps1has its SHA-256 listed in /releases.json. See verifying the script. - On 30 Oct 2026 we downloaded version 0.2.1 through the live website hosting and checked that its hash matched the release. Version 0.2.2 was checked from a fresh copy of the source on 31 Oct 2026; the download test through the website is repeated at launch.
- Reports flag result files made with a script version that is not listed.
- The script reads settings only, changes nothing, and sends nothing.
Every claim on this page can be shown on request; a claim we cannot show is removed. Results describe settings detected on the dates shown. Not an audit, not a certification, not legal advice.