WispBinder

DRAFT Not published yet. Results 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 the same outside-in method as the free domain check (public DNS only).

ItemResult (31 Oct 2026)
Email providerIdentified from public MX records
SPFDETECTED on 31 Oct 2026: exactly one SPF record, ending in ~all
DKIMThree DKIM keys published by our email provider. Our own browser check shows "cannot be confirmed (common selectors only)" for our domain too, because our provider uses selectors the check does not try. The check's limits apply to us as well.
DMARCDETECTED on 31 Oct 2026, policy p=none, with reports sent to us since 31 Oct 2026

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.

Check30 Oct 202631 Oct – 1 Nov 2026
W02 Disk encryptionNOT DETECTED on 30 Oct 2026: drive encrypted, but no key protector, so protection was offDETECTED on 31 Oct 2026: protection on, recovery key stored away from the computer
W08 Accounts require a passwordNEEDS WRITTEN CONFIRMATION on 30 Oct 2026 ("password not required" flag)DETECTED on 31 Oct 2026
W15 Remote-access softwareSeveral 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 softwareInstalled (30 Oct 2026)Removed (31 Oct 2026)
W16 SMBv1 offDETECTED on 30 Oct 2026DETECTED on 31 Oct 2026
W04 Firewall, W05 UpdatesResult not kept in our records for 30 Oct 2026DETECTED on 31 Oct 2026
W06 Screen lockNEEDS 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 AntivirusNEEDS 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.

ExceptionWhyWhat we do instead
One remote-support tool stays installedNeeded for other work on this computerUnattended 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 rightsSoftware development work on this computer needs them oftenWindows 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

3. The script you download

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.