whdh.com

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

SPF

pass

SPF record published

Found

Record
v=spf1 mx ip4:192.55.82.60 include:servers.mcsv.net include:spf.protection.outlook.com include:whdh-com.spf.smtp25.com -all
DNS lookups
4 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 4 of 10 DNS lookups #2
    SPF record needs 4 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

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

fail

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NXDOMAIN

Checks

  • ✗
    No DKIM keys published
    _domainkey.whdh.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #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
10primary.us.email.fireeyecloud.comA 34.223.36.123 A 3.93.93.53 A 3.93.93.51 A 3.93.93.52 A 34.223.36.121 A 34.223.36.122mx.us.email.fireeyecloud.com ✓ mx.us.email.fireeyecloud.com ✓ mx.us.email.fireeyecloud.com ✓ mx.us.email.fireeyecloud.com ✓ mx.us.email.fireeyecloud.com ✓ mx.us.email.fireeyecloud.com ✓
20alt1.us.email.fireeyecloud.comA 3.93.93.51 A 3.93.93.53 A 34.223.36.121 A 34.223.36.123 A 34.223.36.122 A 3.93.93.52mx.us.email.fireeyecloud.com ✓ mx.us.email.fireeyecloud.com ✓ mx.us.email.fireeyecloud.com ✓ mx.us.email.fireeyecloud.com ✓ mx.us.email.fireeyecloud.com ✓ mx.us.email.fireeyecloud.com ✓
30alt2.us.email.fireeyecloud.comA 34.223.36.121 A 3.93.93.53 A 34.223.36.123 A 3.93.93.52 A 34.223.36.122 A 3.93.93.51mx.us.email.fireeyecloud.com ✓ mx.us.email.fireeyecloud.com ✓ mx.us.email.fireeyecloud.com ✓ mx.us.email.fireeyecloud.com ✓ mx.us.email.fireeyecloud.com ✓ mx.us.email.fireeyecloud.com ✓
40alt3.us.email.fireeyecloud.comA 3.93.93.51 A 34.223.36.122 A 34.223.36.121 A 3.93.93.53 A 3.93.93.52 A 34.223.36.123mx.us.email.fireeyecloud.com ✓ mx.us.email.fireeyecloud.com ✓ mx.us.email.fireeyecloud.com ✓ mx.us.email.fireeyecloud.com ✓ mx.us.email.fireeyecloud.com ✓ mx.us.email.fireeyecloud.com ✓

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: primary.us.email.fireeyecloud.com, alt1.us.email.fireeyecloud.com, alt2.us.email.fireeyecloud.com, alt3.us.email.fireeyecloud.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.
  • ✓ No CNAME targets #22
    No MX records point to a CNAME.
  • ✓ Reverse DNS confirmed #30
    All 24 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
primary.us.email.fireeyecloud.comnone-
alt1.us.email.fireeyecloud.comnone-
alt2.us.email.fireeyecloud.comnone-
alt3.us.email.fireeyecloud.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