opendns.com

Checked 22 October 2026, 10:10 UTC · via 8.8.8.8
✗Problems found
20 passed 6 warnings 1 failed 3 info

SPF

warn

SPF record published

Found

Record
v=spf1 ptr include:_nets.opendns.com include:mail.zendesk.com include:amazonses.com include:_netblocks.google.com include:_netblocks2.google.com include:_netblocks3.google.com ip4:173.37.147.246 ip4:173.37.147.247 ip4:72.163.7.179 ip4:72.163.7.180 ip4:192.28.150.255 ?all
DNS lookups
7 of 10
Void lookups
0 of 2

Checks

  • !
    Uses deprecated ptr mechanism
    The ptr mechanism in SPF records is deprecated due to performance issues and should be avoided.
    #1
  • ✓ 7 of 10 DNS lookups #2
    SPF record needs 7 DNS lookups (limit is 10).
  • !
    Ends with ?all (neutral)
    SPF record uses ?all (neutral), which gives no protection against unauthorized senders. Use -all or ~all instead.
    #3
  • ✓ 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.opendns.com)

Found

Record
v=DMARC1; p=none; rua=mailto:hostmaster@opendns.com
Found at
_dmarc.opendns.com
TagValueMeaning
vDMARC1Version
pnonePolicy
ruamailto:hostmaster@opendns.comAggregate report addresses

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.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:hostmaster@opendns.com
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: default, mail, google

Found

Selectors
default, mail, google
_domainkey
NOERROR
SelectorKeyFlags
defaultRSA 1024 bitstest mode (t=y)
mailRSA 1024 bitstest mode (t=y)
googleRSA 1024 bits

Checks

  • ✓ Keys found: default, mail, google #7
    DKIM keys found for this domain with selectors: default, mail, google
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: default (1024 bits), mail (1024 bits), google (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Key in test mode
    These keys have t=y, so receivers treat DKIM failures as a test: default, mail. Remove t=y once DKIM works.
    #24

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

pass

3 mail servers

Found

PriorityHostRecordsReverse DNS
10alln-mx-01.cisco.comA 173.37.147.230 AAAA 2001:420:1201:6::ad25:93e6alln-mx-01.cisco.com ✓ alln-mx-01.cisco.com ✓
20rcdn-mx-01.cisco.comA 72.163.7.166 AAAA 2001:420:1101:7::48a3:166rcdn-mx-01.cisco.com ✓ rcdn-mx-01.cisco.com ✓
30aer-mx-01.cisco.comA 173.38.212.150 AAAA 2001:420:4621::ad26:d496aer-mx-01.cisco.com ✓ aer-mx-01.cisco.com ✓

Checks

  • ✓ 3 MX records #9
    Found 3 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 3 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 3 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 3 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
alln-mx-01.cisco.comnone-
rcdn-mx-01.cisco.comnone-
aer-mx-01.cisco.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