zonealarm.com

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

SPF

fail

SPF record published

Found

Record
v=spf1 include:spf1.zonealarm.com include:mail.zendesk.com include:_spf.mailing.checkpoint.com include:spf.protection.outlook.com include:2checkout.com -all
DNS lookups
15 of 10
Void lookups
0 of 2
Problem
include:_spf.mailing.checkpoint.com could not be resolved: DNS query for _spf.mailing.checkpoint.com returned SERVFAIL

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✗
    15 DNS lookups, over the limit of 10
    SPF record needs 15 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record. Problems found: include:_spf.mailing.checkpoint.com could not be resolved: DNS query for _spf.mailing.checkpoint.com returned SERVFAIL.
    #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

warn

p=reject (_dmarc.zonealarm.com)

Found

Record
v=DMARC1; p=reject; rua=mailto:dmarc_us@checkpoint.com; ruf=mailto:dmarc_us@checkpoint.com; sp=none; ri=86400
Found at
_dmarc.zonealarm.com
External report address
mailto:dmarc_us@checkpoint.com (not authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
spnoneSubdomain policy
ruamailto:dmarc_us@checkpoint.comAggregate report addresses
rufmailto:dmarc_us@checkpoint.comFailure report addresses
ri86400Report interval (seconds)

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_us@checkpoint.com
  • !
    Subdomains unprotected (sp=none)
    DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • !
    Report address not authorized
    These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:dmarc_us@checkpoint.com (needs zonealarm.com._report._dmarc.checkpoint.com). Ask the report provider to publish the record, or check the address.
    #29

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

1 mail server

Found

PriorityHostRecordsReverse DNS
0zonealarm-com.mail.protection.outlook.comA 52.101.73.145 A 52.101.185.24 A 52.101.91.153 A 52.101.103.36 AAAA 2a01:111:f403:ca38::a AAAA 2a01:111:f403:ca3c::8 AAAA 2a01:111:f403:c967::a AAAA 2a01:111:f403:ca38::8mail-am6pr02cu00301.inbound.protection.outlook.com ✓ mail-zrxpr07cu00100.inbound.protection.outlook.com ✓ mail-matpr04cu00101.inbound.protection.outlook.com ✓ mail-miypr05cu00104.inbound.protection.outlook.com ✓ mail-wa4pr05cu00102.inbound.protection.outlook.com ✓ mail-zrxpr05cu00100.inbound.protection.outlook.com ✓ mail-cpjpr05cu00102.inbound.protection.outlook.com ✓ mail-wa4pr04cu00100.inbound.protection.outlook.com ✓

Checks

  • ✓ 1 MX record #9
    Found 1 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.
  • !
    Single MX host, no backup
    Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • ✓ At most 5 MX records #13
    Found 1 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 8 MX addresss have a PTR record that resolves back to them.

TLS

fail

MTA-STS record without policy · no TLS-RPT · DANE on 0 of 1 MX hosts

Found

MTA-STS record
v=STSv1; id=20251013100000
Policy URL
https://mta-sts.zonealarm.com/.well-known/mta-sts.txt
Policy error
https://mta-sts.zonealarm.com/.well-known/mta-sts.txt returned HTTP 404

DANE (TLSA records)

MX hostTLSADNSSEC
zonealarm-com.mail.protection.outlook.comnone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 20251013100000.
  • ✗
    Policy not reachable
    The MTA-STS record exists but the policy could not be fetched, so senders ignore MTA-STS: https://mta-sts.zonealarm.com/.well-known/mta-sts.txt returned HTTP 404.
    #33
  • !
    Not configured
    MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".
    #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