v2digga

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

Results for

facebook.com

Email authentication

The basics are in place but can be hardened.

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

SPF

Warning

Authorizes which servers may send mail for the domain

SPF is published but could be tightened.

Policy
none
DNS lookups
1 / 10
  • No all mechanism: the record has no default policy for unlisted senders.
  • Uses 1 of 10 allowed DNS lookups.
v=spf1 redirect=_spf.facebook.com

DKIM

Not set

Cryptographically signs outgoing mail (best-effort selector probe)

Only revoked DKIM keys (empty p=) are published.

  • A DKIM record with an empty p= value signals a revoked key, i.e. the domain publishes no active signing key (often a deliberate "sends no mail" marker).

DMARC

Pass

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

DMARC is enforced.

Policy
p=reject
Coverage
100%
  • Policy p=reject: failing mail is rejected outright.
  • Aggregate reports (rua) are configured.
v=DMARC1; p=reject; rua=mailto:[email protected]; ruf=mailto:[email protected]; pct=100

MTA-STS

Warning

Enforces TLS for inbound mail and prevents downgrade attacks

MTA-STS is published but not enforcing.

Mode
testing
Max age
86400s
  • Policy mode is testing: failures are reported but mail is still delivered.
v=STSv1; id=20191202T113700;

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.