planet.com

Checked 22 October 2026, 10:14 UTC · via 8.8.8.8
!Passed with warnings
27 passed 4 warnings 0 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all
DNS lookups
1 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 1 of 10 DNS lookups #2
    SPF record needs 1 DNS lookups (limit is 10).
  • ✓ Ends with ~all #3
    SPF record properly uses ~all to restrict unauthorized senders.
  • ✓ Record published #6
    SPF record exists for this domain.
  • ✓ Single record #16
    Exactly one SPF record is published.
  • ✓ Valid syntax #25
    All SPF mechanisms and modifiers are valid.
  • ✓ No void lookups #26
    All include/redirect targets exist.
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

pass

p=reject (_dmarc.planet.com)

Found

Record
v=DMARC1; p=reject; sp=quarantine; rua=mailto:dmarc_agg@vali.email
Found at
_dmarc.planet.com
External report address
mailto:dmarc_agg@vali.email (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
spquarantineSubdomain policy
ruamailto:dmarc_agg@vali.emailAggregate report addresses

Checks

  • ✓ Policy: reject #4
    DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Applies to 100% of mail #18
    DMARC policy applies to all failing mail.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:dmarc_agg@vali.email
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NOERROR

Checks

  • !
    No key under common selectors
    The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7

DNSSEC

warn

Signed, but no DS at parent

Found

DNSKEY records
Yes (3)
DS at parent
No
Algorithms
ECDSAP256SHA256 (13)
Key tags
8184, 46351, 2553
Signatures valid until
22 October 2026, 18:00 UTC

Checks

  • !
    Signed, but no DS at parent
    The zone is signed (DNSKEY present) but the parent has no DS record, so the chain of trust is incomplete. Publish the DS record at your registrar.
    #8
  • !
    Signatures expire in 8h0m0s
    DNSKEY signatures expire at 2026-10-22T18:00:00Z (in 8h0m0s). Check that re-signing works.
    #21

MX

pass

5 mail servers

Found

PriorityHostRecordsReverse DNS
10aspmx.l.google.comA 142.251.127.26 AAAA 2a00:1450:4001:c21::1blcfrai-in-f26.1e100.net ✓ lcfrai-in-f27.1e100.net ✓
20alt1.aspmx.l.google.comA 142.250.147.27 AAAA 2a00:1450:4025:c01::1brd-in-f27.1e100.net ✓ rd-in-f27.1e100.net ✓
30alt2.aspmx.l.google.comA 172.253.152.27 AAAA 2a00:1450:4010:c22::1ayulpptr-in-f27.1e100.net ✓ yulpptr-in-f26.1e100.net ✓
40aspmx2.googlemail.comA 142.250.147.27 AAAA 2a00:1450:4025:c01::1brd-in-f27.1e100.net ✓ rd-in-f27.1e100.net ✓
50aspmx3.googlemail.comA 172.253.152.27 AAAA 2a00:1450:4010:c22::1ayulpptr-in-f27.1e100.net ✓ yulpptr-in-f26.1e100.net ✓

Checks

  • ✓ 5 MX records #9
    Found 5 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • ✓ All hosts have IPv6 #11
    All MX records resolve to IPv6 addresses.
  • ✓ Redundant MX hosts #12
    Found 5 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 5 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 10 MX addresss have a PTR record that resolves back to them.

TLS

warn

MTA-STS testing · TLS-RPT · DANE on 0 of 5 MX hosts

Found

MTA-STS record
v=STSv1; id=20260402230623Z;
Policy URL
https://mta-sts.planet.com/.well-known/mta-sts.txt
Mode
testing
Allowed MX
aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, aspmx2.googlemail.com, aspmx3.googlemail.com
Max age
86400 seconds
TLS-RPT record
v=TLSRPTv1; rua=mailto:tls-report@vali.email

DANE (TLSA records)

MX hostTLSADNSSEC
aspmx.l.google.comnone-
alt1.aspmx.l.google.comnone-
alt2.aspmx.l.google.comnone-
aspmx2.googlemail.comnone-
aspmx3.googlemail.comnone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 20260402230623Z.
  • !
    Policy in testing mode
    With mode: testing, senders only report TLS problems (via TLS-RPT) and still deliver without TLS. Switch to mode: enforce once reports are clean.
    #33
  • ✓ All MX hosts covered #34
    Every MX host matches an mx: line of the MTA-STS policy.
  • ✓ Reports enabled #35
    TLS reports are sent to: mailto:tls-report@vali.email
  • 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