yoshki.com

Checked 22 October 2026, 11:41 UTC · via 8.8.8.8
✗Problems found
10 passed 4 warnings 2 failed 3 info

SPF

fail

No SPF record found

Checks

  • ✗
    No SPF record
    No SPF record was found for this domain. SPF is important for preventing email spoofing. Add an SPF record to specify which servers are authorized to send email for your domain.
    #6

DMARC

fail

No DMARC record found

Checks

  • ✗
    No DMARC record
    No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5

DKIM

pass

Selectors: google

Found

Selectors
google
_domainkey
NOERROR
SelectorKeyFlags
googleRSA 2048 bits

Checks

  • ✓ Keys found: google #7
    DKIM keys found for this domain with selectors: google
  • ✓ Strong keys #23
    DKIM keys are strong enough: google: RSA 2048 bits.
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

warn

Not signed

Found

DNSKEY records
No (0)
DS at parent
No

Checks

  • !
    Not enabled
    DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8

MX

warn

4 mail servers

Found

PriorityHostRecordsReverse DNS
1aspmx.l.google.comA 142.251.127.26 AAAA 2a00:1450:4001:c21::1blcfrai-in-f26.1e100.net ✓ lcfrai-in-f27.1e100.net ✓
5alt1.aspmx.l.google.comA 142.250.147.27 AAAA 2a00:1450:4025:c01::1brd-in-f27.1e100.net ✓ rd-in-f27.1e100.net ✓
5alt2.aspmx.l.google(does not resolve)
10alt3.aspmx.l.google.comA 192.179.20.27 AAAA 2404:6800:4000:1027::1bncboms-in-f27.1e100.net ✓ ncboms-in-f27.1e100.net ✓

Checks

  • ✓ 4 MX records #9
    Found 4 MX records for this domain.
  • !
    Hosts without IP addresses
    The following MX hosts could not be resolved to IP addresses: alt2.aspmx.l.google
    #10
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: alt2.aspmx.l.google
    #11
  • ✓ Redundant MX hosts #12
    Found 4 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 4 MX records, which is within the recommended range (1-5).
  • ✓ No localhost targets #14
    No MX records pointing to localhost found.
  • ✓ No private IP addresses #15
    No MX records resolving to private IP addresses found.
  • ✓ No CNAME targets #22
    No MX records point to a CNAME.
  • ✓ Reverse DNS confirmed #30
    All 6 MX addresss have a PTR record that resolves back to them.

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 4 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
aspmx.l.google.comnone-
alt1.aspmx.l.google.comnone-
alt2.aspmx.l.googlenone-
alt3.aspmx.l.google.comnone-

Checks

  • !
    Not configured
    MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.
    #32
  • i
    Not configured
    TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.
    #35
  • i
    Not used
    No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.
    #36

BIMI

info

No BIMI record

Checks

  • i
    Not configured
    BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.
    #38