themarker.com

Checked 22 October 2026, 11:02 UTC · via 8.8.8.8
✗Problems found
15 passed 6 warnings 2 failed 4 info

SPF

fail

SPF record published

Found

Record
v=spf1 a mx include:mymarketing.co.il include:spf.messagelabs.com include:activetrail.com include:impactia.com ip4:35.210.93.228 a:sendmail.haaretz.com a:sendmail.themarker.com ~all
DNS lookups
16 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✗
    16 DNS lookups, over the limit of 10
    SPF record needs 16 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.
    #2
  • ✓ 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

fail

p=none (_dmarc.themarker.com)

Found

Record
v=DMARC1;p=none
Found at
_dmarc.themarker.com
TagValueMeaning
vDMARC1Version
pnonePolicy

Checks

  • ✗
    Policy: none (monitoring only)
    DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • !
    No aggregate reports (rua)
    DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19

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

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
10cluster5.eu.messagelabs.comA 195.245.230.200 A 195.245.231.69 A 85.158.142.215 A 195.245.230.201 A 195.245.231.72 A 85.158.142.210 A 85.158.142.214 A 195.245.231.75mail858.messagelabs.com ✓ mail874.messagelabs.com ✓ mail839.messagelabs.com ✓ mail859.messagelabs.com ✓ mail876.messagelabs.com ✓ mail834.messagelabs.com ✓ mail838.messagelabs.com ✓ mail879.messagelabs.com ✓
20cluster5a.eu.messagelabs.comA 34.91.159.228228.159.91.34.bc.googleusercontent.com ✓
30mail.themarker.comCNAME mailx.themarker.com A 192.118.73.6lookup failed
40mailx.themarker.comA 192.118.73.6lookup failed

Checks

  • ✓ 4 MX records #9
    Found 4 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: cluster5.eu.messagelabs.com, cluster5a.eu.messagelabs.com, mail.themarker.com, mailx.themarker.com
    #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.
  • !
    Hosts are CNAMEs
    MX records must point to a host name with A/AAAA records, not to a CNAME: mail.themarker.com -> mailx.themarker.com
    #22
  • i
    Could not be checked
    The reverse lookup failed for: 192.118.73.6, 192.118.73.6.
    #30

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
cluster5.eu.messagelabs.comnone-
cluster5a.eu.messagelabs.comnone-
mail.themarker.comnone-
mailx.themarker.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