wella.com

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

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:198.203.169.10 ip4:92.103.63.132 ip4:208.84.65.221 ip4:208.86.201.177 ip4:92.103.63.133 ip4:194.15.48.173 ip4:194.15.48.141 ip4:172.210.94.127 ip4:52.190.47.198 ip4:35.242.247.107 ip4:34.107.8.58 ip4:168.245.98.23 include:spf.protection.outlook.com include:_spf.timeforstorm.com include:_spf.timeforstorm.eu include:_spf.connectstorm.jp include:_spf-dc55.sapsf.eu ~all
DNS lookups
5 of 10
Void lookups
0 of 2

Checks

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

p=none (_dmarc.wella.com)

Found

Record
v=DMARC1; p=none; ruf=mailto:Wella.MSS.SOC@accenture.com,mailto:Wella.ACI@accenture.com; rua=mailto:Wella.MSS.SOC@accenture.com,mailto:Wella.ACI@accenture.com
Found at
_dmarc.wella.com
External report address
mailto:Wella.MSS.SOC@accenture.com (not authorized)
External report address
mailto:Wella.ACI@accenture.com (not authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
ruamailto:Wella.MSS.SOC@accenture.com,mailto:Wella.ACI@accenture.comAggregate report addresses
rufmailto:Wella.MSS.SOC@accenture.com,mailto:Wella.ACI@accenture.comFailure 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:Wella.MSS.SOC@accenture.com, mailto:Wella.ACI@accenture.com
  • !
    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:Wella.MSS.SOC@accenture.com (needs wella.com._report._dmarc.accenture.com); mailto:Wella.ACI@accenture.com (needs wella.com._report._dmarc.accenture.com). Ask the report provider to publish the record, or check the address.
    #29

DKIM

warn

Selectors: selector1, s1, s2

Found

Selectors
selector1, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 2048 bits
s1RSA 2048 bits
s2RSA 1024 bits

Checks

  • ✓ Keys found: selector1, s1, s2 #7
    DKIM keys found for this domain with selectors: selector1, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: s2 (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

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
10wella-com.mail.protection.outlook.comA 52.101.41.28 A 40.93.192.4 A 52.101.41.54 A 52.101.42.170 AAAA 2a01:111:f403:c902::7 AAAA 2a01:111:f403:c918::5 AAAA 2a01:111:f403:c92c::7 AAAA 2a01:111:f403:c91d::bmail-sj0pr03cu01504.inbound.protection.outlook.com ✓ mail-dm2pr04cu00404.inbound.protection.outlook.com ✓ mail-sj2pr05cu00506.inbound.protection.outlook.com ✓ mail-mw5pr21cu00102.inbound.protection.outlook.com ✓ mail-sj0pr02cu00107.inbound.protection.outlook.com ✓ mail-byapr05cu00805.inbound.protection.outlook.com ✓ mail-dm3pr04cu00107.inbound.protection.outlook.com ✓ mail-mw2pr02cu00603.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

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
wella-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