v2digga

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

Results for

mxrecord.mx

Email authentication

Email authentication is well configured.

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

SPF

Pass

Authorizes which servers may send mail for the domain

SPF is published and within limits.

Policy
~all
DNS lookups
0 / 10
  • Ends in ~all (softfail): unauthorized senders are marked, not rejected.
  • Uses 0 of 10 allowed DNS lookups.
v=spf1 ip4:35.232.98.50 ip4:35.223.153.80 ip4:35.226.211.128 ip4:134.195.27.0/28 ip4:34.100.176.166 ip4:34.93.114.78 ~all

DKIM

Not set

Cryptographically signs outgoing mail (best-effort selector probe)

No DKIM key found for common selectors.

Selectors probed
30
  • DKIM selectors cannot be enumerated from DNS, so this only probes well-known selectors. A negative result is not proof that DKIM is missing.

DMARC

Pass

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

DMARC is enforced.

Policy
p=quarantine
Coverage
100%
  • Policy p=quarantine: failing mail is sent to spam.
  • Aggregate reports (rua) are configured.
v=DMARC1; p=quarantine; rua=mailto:[email protected];

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

Pass

Receives reports about TLS delivery failures

TLS reporting is configured.

Reports to
mailto:[email protected]
  • TLS delivery failure reports are being collected.
v=TLSRPTv1; rua=mailto:[email protected]

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.