v2digga

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

Results for

cyberin.in

Email authentication

The basics are in place but can be hardened.

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

SPF

Pass

Authorizes which servers may send mail for the domain

SPF is published and within limits.

Policy
~all
DNS lookups
1 / 10
  • Ends in ~all (softfail): unauthorized senders are marked, not rejected.
  • Uses 1 of 10 allowed DNS lookups.
v=spf1 include:_spf.google.com ~all

DKIM

Pass

Cryptographically signs outgoing mail (best-effort selector probe)

DKIM key published for 1 known selector.

Selectors
mail
  • Found a DKIM key at mail._domainkey.cyberin.in

DMARC

Warning

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

DMARC is published but not fully enforcing.

Policy
p=none
Coverage
100%
  • Policy p=none: DMARC is in monitoring mode only and does not block spoofed mail.
  • Aggregate reports (rua) are configured.
v=DMARC1; p=none; 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

Not set

Receives reports about TLS delivery failures

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

BIMI

Warning

Displays your verified brand logo in supporting inboxes

BIMI is published with caveats.

Logo
https://www.cyberin.in/assets/images/cyberin.svg
  • A logo (l=) is published.
  • BIMI requires an enforcing DMARC policy (quarantine or reject) to be honored.
v=BIMI1;l=https://www.cyberin.in/assets/images/cyberin.svg;a=

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.