v2digga

Apex, subdomain, or URL. We figure it out.

Results for

hello.co

Email authentication

Spoofing protection has gaps that need attention.

  • 2Pass
  • 0Warning
  • 1Fail
  • 3Not set

SPF

Pass

Authorizes which servers may send mail for the domain

SPF is published and within limits.

Policy
~all
DNS lookups
4 / 10
  • Ends in ~all (softfail): unauthorized senders are marked, not rejected.
  • Uses 4 of 10 allowed DNS lookups.
v=spf1 include:_spf.mi.com.co include:_spf.google.com ip4:52.20.146.153 ip4:34.232.192.154 ip4:34.239.6.196 ip4:52.1.27.116 ip4:3.22.92.185 ip4:200.25.12.158 mx ~all

DKIM

Pass

Cryptographically signs outgoing mail (best-effort selector probe)

DKIM key published for 3 known selectors.

Selectors
s1, s2, mail
  • Found a DKIM key at s1._domainkey.hello.co
  • Found a DKIM key at s2._domainkey.hello.co
  • Found a DKIM key at mail._domainkey.hello.co

DMARC

Fail

Tells receivers what to do with mail that fails SPF and DKIM

No DMARC record. Failing mail is not actively rejected or quarantined.

  • No v=DMARC1 TXT record found at _dmarc.hello.co
  • DMARC ties SPF and DKIM together and enables reporting.

MTA-STS

Not set

Enforces TLS for inbound mail and prevents downgrade attacks

No MTA-STS policy. Inbound mail can be delivered without TLS.

TLS-RPT

Not set

Receives reports about TLS delivery failures

No TLS-RPT record. You get no reports about failed TLS delivery.

BIMI

Not set

Displays your verified brand logo in supporting inboxes

No BIMI record. No brand logo is published for inboxes.

Checks query live DNS over Cloudflare and the public MTA-STS policy endpoint. DKIM selectors cannot be listed from DNS, so DKIM detection probes common provider selectors only.