DNS & email auth

warnLast checked
Findings5 findings

Recommended (4)

  • The record uses softfail (~all), which is weaker than fail (-all).

    SPF

    How to fix

    Move to -all once you're confident every legitimate sender is listed.

  • No DKIM key was found for the common selectors checked.

    DKIM

    Custom selectors may still exist outside the common probe list.

    How to fix

    If this domain sends mail, enable DKIM signing at the email provider and publish the selector records it gives you.

  • DMARC policy is p=none, so it monitors but does not enforce.

    DMARC

    How to fix

    Once your legitimate senders pass, move to p=quarantine and then p=reject.

  • The record has no rua= aggregate reporting address, so no one is told when DMARC fails.

    DMARC

    How to fix

    Add rua=mailto:you@example.com to the record to receive daily aggregate reports from receivers.

Healthy (1)

  • 1 MX record found.

    MX

Evidence

MX

1 record
  • work-mx.app.hey.compriority 10

SPF

1 of 10 lookups
DNS lookups1 / 10
eggcarton.io
include:_spf.hey.com

Root TXT

1 record
  • v=spf1 include:_spf.hey.com ~all

DKIM selectors

0 records

Probed with no records: selector1, selector2, google, 20230601, 20210112, k1, k2, s1, s2, default, dkim, mail

DMARC

1 record
v=DMARC1; p=none;
v=DMARC1
Identifies this TXT record as a DMARC policy. Must be the first tag.
p=none
Monitoring only: receivers deliver failing mail normally and just send reports.
sp=nonedefault
No sp= tag is published, so subdomains inherit the domain's p= policy.
pct=100default
No pct= tag is published, so the policy applies to all failing mail.
adkim=rdefault
No adkim= tag is published, so DKIM alignment is relaxed: any subdomain of the From domain may sign.
aspf=rdefault
No aspf= tag is published, so SPF alignment is relaxed: the envelope sender may be any subdomain of the From domain.
Raw JSON