The fix from #237 (#236) for the 2026 series, which :latest runs until 27.1 ships: a valid DMARC or SPF record of the domain's own is no longer reported as missing from public DNS.
Cherry-pick of the fix commit from main, applied cleanly.
Version 2026.10.26.8 with its CHANGELOG entry.
Checked locally on this branch: typecheck, lint, i18n:check, tests (959), changelog check, listen-ipv6 test, notice check, build.
The fix from #237 (#236) for the 2026 series, which `:latest` runs until 27.1 ships: a valid DMARC or SPF record of the domain's own is no longer reported as missing from public DNS.
- Cherry-pick of the fix commit from main, applied cleanly.
- `Version 2026.10.26.8` with its CHANGELOG entry.
Checked locally on this branch: typecheck, lint, i18n:check, tests (959), changelog check, listen-ipv6 test, notice check, build.
The Mail records check (SS-13) called every core record that wasn't
exactly the suggested value missing. Now each kind has a state:
missing records stay missing; a single well-formed DMARC (with p=) or
SPF of the domain's own passes, as SS-18 and the Deliverability tab
cover what it says; an MX or DKIM that differs, or a broken SPF or
DMARC, is named as not matching this server; and a domain whose
lookups all failed is not checked rather than missing. The DNS page's
comparison is unchanged.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The fix from #237 (#236) for the 2026 series, which
:latestruns until 27.1 ships: a valid DMARC or SPF record of the domain's own is no longer reported as missing from public DNS.Version 2026.10.26.8with its CHANGELOG entry.Checked locally on this branch: typecheck, lint, i18n:check, tests (959), changelog check, listen-ipv6 test, notice check, build.