honeywell.com

Checked 22 October 2026, 09:12 UTC · via 8.8.8.8
!Passed with warnings
25 passed 5 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:199.64.176.32/29 ip4:199.64.34.172/30 ip4:199.64.210.11/29 include:spf.protection.outlook.com include:mktomail.com include:_spf.salesforce.com include:spf.mandrillapp.com include:spf_c.oraclecloud.com include:_spf1.honeywell.com -all
DNS lookups
9 of 10
Void lookups
0 of 2

Checks

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

warn

p=reject (_dmarc.honeywell.com)

Found

Record
v=DMARC1; p=reject; sp=none; adkim=r; aspf=r; fo=1; pct=100; rf=afrf; ri=3600; rua=mailto:SVXSOARDEV@honeywell.com; ruf=mailto:SVXSOARDEV@honeywell.com
Found at
_dmarc.honeywell.com
TagValueMeaning
vDMARC1Version
prejectPolicy
spnoneSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:SVXSOARDEV@honeywell.comAggregate report addresses
rufmailto:SVXSOARDEV@honeywell.comFailure report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)
fo1Failure reporting options
rfafrfFailure report format
ri3600Report 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:SVXSOARDEV@honeywell.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 addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: mail, email, k1, selector1, selector2, s1, s2

Found

Selectors
mail, email, k1, selector1, selector2, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 1024 bits
emailRSA 1024 bits
k1RSA 2048 bits
selector1RSA 2048 bits
selector2RSA 2048 bits
s1RSA 2048 bits
s2RSA 2048 bits

Checks

  • ✓ Keys found: mail, email, k1, selector1, selector2, s1, s2 #7
    DKIM keys found for this domain with selectors: mail, email, k1, selector1, selector2, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), email (1024 bits). Rotate to a 2048-bit key.
    #23
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
34505, 2371
Signatures valid until
4 December 2026, 16:15 UTC

Checks

  • ✓ Signed, DS published at parent #8
    DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
  • ✓ Signatures valid until 2026-12-04 #21
    DNSKEY signatures are valid until 2026-12-04T16:15:24Z.

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
10honeywell-com.mail.protection.outlook.comA 52.101.202.153 A 52.101.40.3 A 52.101.8.32 A 52.101.60.163mail-ph0pr02cu00101.inbound.protection.outlook.com ✓ mail-cy4pr03cu00203.inbound.protection.outlook.com ✓ mail-dm8pr21cu00100.inbound.protection.outlook.com ✓ mail-bn3pr04cu00103.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.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: honeywell-com.mail.protection.outlook.com
    #11
  • !
    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 4 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
honeywell-com.mail.protection.outlook.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