The Security overview (SS-13, "Mail records in DNS") reports a domain as "missing DMARC in public DNS" when the domain does publish a valid DMARC record, as long as that record isn't exactly the one inbuxa suggests. Reported on the forum in t/321, on console rc.20 against server rc.29.
checkRecords (src/features/dns/liveCheck.ts) gives each suggested record one of four states: live (exact match), different (something is published but doesn't match), missing, or error (the lookup failed).
coreChecks (src/features/hovercards/facts.ts) collapses those to live: true/false, and only an exact match counts.
askDns (src/features/security/load.ts) then lists every false as missing, and SS-13 says "is missing … in public DNS".
Effects
DMARC: a valid record with its own report addresses or extra tags is called missing. SS-18 already reads the published policy (dmarcPolicyOf), so the console knows the record is there.
SPF: a hand-tuned record, such as one with an extra include: or ~all, is called missing.
MX and DKIM: a record that differs is called missing, too. A mismatch here usually is a real problem, but "missing" is the wrong word for it.
Failed lookups: when the DNS lookup fails, the record is called missing instead of not checked.
Domain hover card: the "N of 4 key records live" count is low for the same reason.
Fix
coreChecks returns the state for each kind instead of a yes/no.
SS-13 handles each state:
missing stays important, as now;
a failed lookup is reported as not checked;
a published DMARC record that differs passes when it's valid (v=DMARC1 with a p=); SS-18 covers the policy;
a published SPF record that differs passes when it's valid (v=spf1); the Deliverability tab checks what it covers;
an MX or DKIM record that differs stays important, worded as "points elsewhere" or "doesn't match the key the server signs with".
The DNS page's comparison stays as it is: it shows the difference, which is right there.
Tests: the record above, an SPF with an extra include, and a failed lookup.
The Security overview (SS-13, "Mail records in DNS") reports a domain as "missing DMARC in public DNS" when the domain does publish a valid DMARC record, as long as that record isn't exactly the one inbuxa suggests. Reported on the forum in t/321, on console rc.20 against server rc.29.
Suggested by inbuxa:
```
v=DMARC1; p=reject; rua=mailto:[email protected]
```
Published (valid, and DMARC passes):
```
v=DMARC1; p=reject; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1
```
## Cause
- `checkRecords` (`src/features/dns/liveCheck.ts`) gives each suggested record one of four states: `live` (exact match), `different` (something is published but doesn't match), `missing`, or `error` (the lookup failed).
- `coreChecks` (`src/features/hovercards/facts.ts`) collapses those to `live: true/false`, and only an exact match counts.
- `askDns` (`src/features/security/load.ts`) then lists every `false` as missing, and SS-13 says "is missing … in public DNS".
## Effects
- **DMARC:** a valid record with its own report addresses or extra tags is called missing. SS-18 already reads the published policy (`dmarcPolicyOf`), so the console knows the record is there.
- **SPF:** a hand-tuned record, such as one with an extra `include:` or `~all`, is called missing.
- **MX and DKIM:** a record that differs is called missing, too. A mismatch here usually is a real problem, but "missing" is the wrong word for it.
- **Failed lookups:** when the DNS lookup fails, the record is called missing instead of not checked.
- **Domain hover card:** the "N of 4 key records live" count is low for the same reason.
## Fix
- `coreChecks` returns the state for each kind instead of a yes/no.
- SS-13 handles each state:
- missing stays important, as now;
- a failed lookup is reported as not checked;
- a published DMARC record that differs passes when it's valid (`v=DMARC1` with a `p=`); SS-18 covers the policy;
- a published SPF record that differs passes when it's valid (`v=spf1`); the Deliverability tab checks what it covers;
- an MX or DKIM record that differs stays important, worded as "points elsewhere" or "doesn't match the key the server signs with".
- The DNS page's comparison stays as it is: it shows the difference, which is right there.
- Tests: the record above, an SPF with an extra include, and a failed lookup.
jcoffey-dev
added this to the 27.1 milestone 2026-11-18 15:50:39 +00:00
jcoffey-dev
added the bug label 2026-11-18 15:50:39 +00:00
Fixed in #237. Thanks to Stefan for the report on the forum (t/321), with the exact record and the files to look at.
The Security overview now accepts a single valid DMARC (with a p=) or SPF record of the domain's own, even when it differs from the suggested one. A record that is really missing still says so. An MX or DKIM that differs, or a broken SPF or DMARC, is reported as not matching this server, with the reason. A domain whose DNS lookups all failed shows as not checked. The DNS page's comparison is unchanged.
It will be in the next console release candidate, and in a 2026 release for :latest.
Fixed in #237. Thanks to Stefan for the report on the forum (t/321), with the exact record and the files to look at.
The Security overview now accepts a single valid DMARC (with a `p=`) or SPF record of the domain's own, even when it differs from the suggested one. A record that is really missing still says so. An MX or DKIM that differs, or a broken SPF or DMARC, is reported as not matching this server, with the reason. A domain whose DNS lookups all failed shows as not checked. The DNS page's comparison is unchanged.
It will be in the next console release candidate, and in a 2026 release for `:latest`.
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 Security overview (SS-13, "Mail records in DNS") reports a domain as "missing DMARC in public DNS" when the domain does publish a valid DMARC record, as long as that record isn't exactly the one inbuxa suggests. Reported on the forum in t/321, on console rc.20 against server rc.29.
Suggested by inbuxa:
Published (valid, and DMARC passes):
Cause
checkRecords(src/features/dns/liveCheck.ts) gives each suggested record one of four states:live(exact match),different(something is published but doesn't match),missing, orerror(the lookup failed).coreChecks(src/features/hovercards/facts.ts) collapses those tolive: true/false, and only an exact match counts.askDns(src/features/security/load.ts) then lists everyfalseas missing, and SS-13 says "is missing … in public DNS".Effects
dmarcPolicyOf), so the console knows the record is there.include:or~all, is called missing.Fix
coreChecksreturns the state for each kind instead of a yes/no.v=DMARC1with ap=); SS-18 covers the policy;v=spf1); the Deliverability tab checks what it covers;Fixed in #237. Thanks to Stefan for the report on the forum (t/321), with the exact record and the files to look at.
The Security overview now accepts a single valid DMARC (with a
p=) or SPF record of the domain's own, even when it differs from the suggested one. A record that is really missing still says so. An MX or DKIM that differs, or a broken SPF or DMARC, is reported as not matching this server, with the reason. A domain whose DNS lookups all failed shows as not checked. The DNS page's comparison is unchanged.It will be in the next console release candidate, and in a 2026 release for
:latest.