Dataweaz

wella.com

Summary

Registrar
CSC Corporate Domains, Inc.
Status
clientTransferProhibited
Created on
January 6, 1996
Expires on
January 5, 2027
Name servers
udns2.cscdns.uk, udns1.cscdns.net
Mail servers
wella-com.mail.protection.outlook.com
SPF
Soft

Spoofing protection (DMARC)

Monitoring

E-mails spoofing this domain are only reported, not blocked.

DMARC tells mail servers what to do with an e-mail that claims to come from wella.com but fails SPF and DKIM checks.

Policy
Monitoring
Subdomain policy
Monitoring
Messages covered
100%
DKIM alignment
Relaxed
SPF alignment
Relaxed

Record

v=DMARC1; p=none; ruf=mailto:[email protected],mailto:[email protected]; rua=mailto:[email protected],mailto:[email protected]

Authorized senders (SPF)

Soft

E-mails sent by any other server are accepted but flagged as suspicious.

SPF lists the servers allowed to send e-mails for wella.com.

RuleValueResult
ip4198.203.169.10Allowed
ip492.103.63.132Allowed
ip4208.84.65.221Allowed
ip4208.86.201.177Allowed
ip492.103.63.133Allowed
ip4194.15.48.173Allowed
ip4194.15.48.141Allowed
ip4172.210.94.127Allowed
ip452.190.47.198Allowed
ip435.242.247.107Allowed
ip434.107.8.58Allowed
ip4168.245.98.23Allowed
includespf.protection.outlook.comAllowed
include_spf.timeforstorm.comAllowed
include_spf.timeforstorm.euAllowed
include_spf.connectstorm.jpAllowed
include_spf-dc55.sapsf.euAllowed
all—Suspicious

Top-level DNS lookups: 5 of 10 allowed

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

E-mail signing (DKIM)

DKIM keys published by wella.com under the most common selectors. Other keys may exist under selectors specific to each sending service.

SelectorLikely serviceKeyStatus
selector1Microsoft 365RSA 2048 bitsActive
s1SendGridRSA 2048 bitsActive
s2SendGridRSA 1024 bits · shortActive

RSA keys shorter than 2048 bits, called short keys, are discouraged: they are easier to break.

MX, SPF, DKIM and DMARC: the e-mail records

Four DNS records make a domain's e-mail work. MX says where e-mails sent to wella.com arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from wella.com was really sent by this domain, which protects it against spoofing.

MX

An MX (Mail Exchanger) record designates a server that receives e-mails sent to the domain. When someone writes to an @wella.com address, their mail server queries the DNS for the domain's MX records, then delivers the message to the server they point to.

Example record

wella.com  MX  10 mx1.wella.com.
wella.com  MX  20 mx2.wella.com.

What the record contains

10, 20
Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
mx1.wella.com.
Host name of the mail server. It must point to an A or AAAA record: an IP address or an alias (CNAME) is not allowed here.
0 .
An MX "0 .", called a null MX, declares that the domain accepts no e-mail: sending servers give up at once instead of retrying.

Declaring at least two servers with different priorities avoids losing e-mails during an outage: sending servers retry for several days and fall back on the backup server. Without any MX, they try to deliver directly to the IP address of the domain.

SPF

SPF (Sender Policy Framework) is a TXT record listing the servers allowed to send e-mails on behalf of the domain. The receiving server checks that the sender is on this list. The final "all" rule says what to do with other servers: reject them (-all), flag their e-mails as suspicious (~all) or make no decision (?all).

Example record

wella.com  TXT  "v=spf1 mx include:_spf.google.com ip4:192.0.2.10 -all"

What the record contains

v=spf1
Identifies the record as an SPF policy. It must come first.
ip4, ip6
Allows a specific IP address or an address range, for example ip4:192.0.2.0/24.
a, mx
Allows the addresses of the domain itself (A record) or those of its mail servers (MX).
include
Allows the servers of another domain, usually a sending service: include:_spf.google.com for Google Workspace.
-all, ~all
Final rule, applied to every other server. Its qualifier decides what happens to them: - rejects them, ~ flags their e-mails as suspicious, ? makes no decision, + accepts them (avoid it).

A domain must publish only one SPF record, and its evaluation cannot exceed 10 DNS lookups (include, a, mx, exists, redirect). Beyond that, mail servers treat it as invalid.

DKIM

DKIM (DomainKeys Identified Mail) signs every outgoing e-mail with a private key. The matching public key is published in a TXT record at selector._domainkey.wella.com, so the recipient can check that the message really comes from the domain and was not altered on the way. The selector is chosen by each sending service and cannot be guessed: Dataweaz checks the most common ones (Google Workspace, Microsoft 365, Mailchimp, SendGrid…), so a key published under another selector may exist without appearing here.

Example record

google._domainkey.wella.com  TXT  "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA…"

What the record contains

v=DKIM1
Protocol version. Optional but recommended, in which case it must come first.
k
Key algorithm: rsa, the most common, or ed25519.
p
Public key, base64-encoded. An empty value means the key has been revoked.
t
Flags: y marks a key in testing, whose failures must not be penalized; s forbids its use for subdomains.

Each sending service publishes its key under its own selector (google, selector1, k1…), which allows several keys and seamless rotation. A 2048-bit RSA key is recommended today.

DMARC

DMARC (Domain-based Message Authentication, Reporting and Conformance) builds on SPF and DKIM. Published on _dmarc.wella.com, it tells mail servers what to do with an e-mail that fails these checks (let it through, send it to spam or reject it) and where to send reports.

Example record

_dmarc.wella.com  TXT  "v=DMARC1; p=quarantine; rua=mailto:[email protected]; adkim=r; aspf=r"

What the record contains

v=DMARC1
Identifies the record as a DMARC policy. It must come first.
p
Policy applied to e-mails that fail the checks: none (monitoring only), quarantine (spam folder) or reject.
sp
Subdomain policy. Without it, subdomains follow the domain's policy.
rua
Address that receives daily aggregate reports about e-mails sent on behalf of the domain, whether they pass the checks or not.
ruf
Address that receives detailed failure reports, message by message. Few providers still send them.
pct
Percentage of e-mails subject to the policy, for a gradual rollout. 100 by default.
adkim, aspf
DKIM and SPF alignment: r (relaxed, a subdomain of the same domain is enough) or s (strict, the domain must be identical).

To roll out DMARC without blocking legitimate e-mails, start with p=none and an rua address, analyze the reports to find every service sending on behalf of the domain, then move to quarantine and finally to reject.

DNS records of wella.com

IP addresses (A and AAAA)

An A record maps the domain name to an IPv4 address: the address of the server that browsers contact to display the website. The AAAA record does the same for an IPv6 address. A domain can have several of them to spread visits across several servers.

TypeIP address
A18.239.18.26
A18.239.18.39
A18.239.18.41
A18.239.18.9
AAAA2600:9000:2449:e400:1b:de1e:1100:93a1
AAAA2600:9000:2449:6e00:1b:de1e:1100:93a1
AAAA2600:9000:2449:5600:1b:de1e:1100:93a1
AAAA2600:9000:2449:4800:1b:de1e:1100:93a1
AAAA2600:9000:2449:6400:1b:de1e:1100:93a1
AAAA2600:9000:2449:e200:1b:de1e:1100:93a1
AAAA2600:9000:2449:6000:1b:de1e:1100:93a1
AAAA2600:9000:2449:2200:1b:de1e:1100:93a1

Name servers (NS)

NS records designate the authoritative DNS servers of the domain: they answer every question about its other records (A, MX, TXT…). They are provided by the registrar, the hosting provider or a dedicated DNS service, and several servers are declared so that the domain keeps working if one of them fails.

ServerIP address
udns2.cscdns.uk204.74.111.1
udns1.cscdns.net204.74.66.1

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @wella.com addresses. Each server has a priority: the one with the lowest number is tried first, the others take over if it fails. Without an MX record, the domain cannot receive e-mails.

PriorityServerIP address
10wella-com.mail.protection.outlook.com52.101.50.4

TXT records

TXT records hold free text. They are used to prove ownership of the domain to online services (Google, Microsoft, Facebook…) and to publish e-mail security rules: SPF on the domain itself, DMARC on _dmarc.wella.com.

NameContent
wella.comglobalsign-domain-verification=acec981dd01d89ae7ace68f47077f5dd
wella.comglobalsign-domain-verification=628A1CB95BA970A1C98EF53A8880174F.
wella.comglobalsign-domain-verification=B7DC2C05BC63BEC42047AE48272F684D.
wella.comgoogle-site-verification=5XvG6bVUXG9fLRrpiTE6-RcjHiLbf4ysvftn2Ssw3rQ
wella.comgoogle-site-verification=9TxHDw15HCx7Wm_86VSiTNhLkOFK-njD9hF993xcy8E
wella.comgoogle-site-verification=HYUFUC2nLKWp-pEraF0nqdaz7rhGXQ55KQgFY8-zflc
wella.comgoogle-site-verification=POQUgop_W_bt0ADbgR0dV43UVW4SF8suiLEiayA_c_E
wella.comgoogle-site-verification=WKI6l8SUetwjCMWPTFSANnP42q9peV4XIlmLz_vU4JU
wella.comgoogle-site-verification=_mw0I8TnlF0qgD9OZq5kfpIwTMKjYrVWRa7L8pHKH3Y
wella.comgoogle-site-verification=ahh7QdKuRTEKQd5mEweS_EAqYSfbaFvYAA4eLMJ8P9o
wella.comgoogle-site-verification=u2SGnwas2wn4UOLQqzUw5sLDffmYnvr__PwuDLMoQdE
wella.comgoogle-site-verification=umMjqLPiyOikFmwNCwvNqZrrlFlD9_VOUIA5U0BS5ZA
wella.comglobalsign-domain-verification=K9ZBZYNiNsNNOiaY2Tbjn-Bfe0dWwAwpstKoOOVJWO
wella.comglobalsign-domain-verification=S5sT68OBACJ_9CvrzRsz8-5yhYGkz7zbctTR8vnC7B
wella.com_globalsign-domain-verification=KeZgChgTjpOuapyuB61TrjLtaBNRT3wuws5CsNOsLQ
wella.com_globalsign-domain-verification=QaQYl8b02G-zoGdEvbe3nRntBqiSAAhuMYfZYmMnA9
wella.com_globalsign-domain-verification=UyxZnT6xW0HDaWCdVK5UzLTPG4jssfzbiGpwnK5CSF
wella.com_globalsign-domain-verification=wBLWlrecNbufx3SooV84iaRaDLa_NMtj2Fjp1VySNO
wella.combv-domain-verification=717d574001300db83adf614a6b350dac07c017ab123515044cc4ff6019443a88
wella.comadobe-idp-site-verification=b09e5eaa17a4aca8faf53f1bd9140b1d2ae7c323df0e930f5ab13d1de853e62a
wella.comatlassian-domain-verification=AsDgmKQFL10h5RcxmSngEP7C2jZ12IZ87YMELRG19scmKWiAruCXJzykdVwOzPxn
wella.comsuccessfactors-site-verification=YmM2MDc1ZWMyZWY4OWMzMDUzMDE0ZjZkMGJlZmFlMjk0MmRmY2EzM2UzOTllYjE3ZTg1NGIwNjU1MGY4YWJjNw==
wella.comv=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
wella.comMS=ms45357150
wella.comnintex.698de5754c6c0a44bc9f67f5
wella.comyandex-verification: 73c3d2e822724faf
wella.comapple-domain-verification=5DKkIo4f7Nipiih1
wella.comK/q0TDTqUefFrWWcG+qmMdF8E4uqg7Mj4KDwP9hqhSM=
wella.comflexera-domain-verification-wgijpaolyehrjrlz
wella.comdocusign=95d1c26f-e4c6-43f5-aae7-65c4069d5ffc
wella.comdocusign=991eeeed-d067-4403-a180-d8c04b4b275d
wella.comsprout-social-6fbe1fb2-0ad0-4477-a9a9-0ebf6eeed7fe
wella.comshopify-verification-code=PBGTLLcn89HhlGRyZw2fvQLl1iZfgO
wella.comshopify-verification-code=vuvCTGkreKWXufan4aB87zr0uipltq
wella.commiro-verification=f3983a02dd6c402a2bed15b87d5a1b38cfe765e6
wella.comdomain-verification-394150=2cc594d2ef5410e07cfdee6e341b1874
wella.comfacebook-domain-verification=iveh6ivh36l5la7g4hhk7ogapjwafj
wella.comfacebook-domain-verification=qny2ydzmb6ovegealhu582zq780qz7
wella.comonetrust-domain-verification=da2496d50a164770a35c7a2253bfdacf
wella.comglobalsign-domain-verification=1A96C83D6FF0E520FE165950239ACED9
wella.comglobalsign-domain-verification=507CB20C84FCF1B89651BD36AB8ECA4C
wella.comglobalsign-domain-verification=A1E47D9AC07A708B7E700B5926A550D1
wella.comglobalsign-domain-verification=E66E30A64F40BB70AB82F9FB18BC1ABE
wella.comglobalsign-domain-verification=E8D7FD5DAC3634F426446B0BDB577426
_dmarc.wella.comv=DMARC1; p=none; ruf=mailto:[email protected],mailto:[email protected]; rua=mailto:[email protected],mailto:[email protected]
selector1._domainkey.wella.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvVyKksXBaaWrKX+HWhqGVXcc9o9t5GkWolTx3XZaqS8+8+KyQxB4YuZSzBOfQXRKTLOsat3nZ/i+7C393YAMi/pfjU7bhzMU/z6QWoUEw5IDi0udS0G/nMGf5jwImx/IzYCG3G+oMyYwND0cj0myJK2C2gh956xDakFyCYvw4DUd2j3MbTARkRjpvc5/DQ/PqqVXd91tPGEy2FxiY/qJzSZcrfAFLDljvctI3QTVh4N3Un9Gf0l844wFWeJHOcqyvJgdFZ27REN+ddoi3ueSlVIqHm4JK9uknzQzZRuIkN2yFZHP1okyP48iG2nnoYmk8KMoKc/wftEECV7RqzktcQIDAQAB;
s1._domainkey.wella.comk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAmhNQ2Zt3YgKPmmjPI795nSC0+X6G2v8394aRZns6tpHdjy5CyOs93Xzx8LAlPDsbENNDYO5hLOkWM2qrqhkCdK8nk5yg3VOeRnj9YE9CBvR6A3Rgj9rLaOCQ7zOtyJJOJFH34lwCkNB2ywxHGRB6MpfOqu0BqdyeX1nMW3Hhn99WmrnRqc9so99EsaHTpwUHHfRR0UjJXLHsp40mBqeJ9aHHLIKqVqzvReqD3pbOWF3yfb8tXGcgIORfByQBM2ser+pHvf4KvWNjPWVVCSnVqAIIZwGg1V0y5E+fXlf52RFoBXDUGlIMteb5GwpF6L1UsMCEiMH891b0F+ORb8AGHQIDAQAB
s2._domainkey.wella.comk=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDQi2dgJS/QOf2xFJFJEOl+bXm9o6S1wEI2QhQiXzwP6k8mCIVFS27WLAz9NzSqTljC28jPYNFqR2K28EPSnoE8Lo15oBjUio/X2k/19OEsCXZ2ZV19p+NYZsudk433Dm6K8kmZKSIwBxAdTzM3sDdQRsdAiWiD2bAt8z/2JYqgmwIDAQAB

Related IP addresses

IPv4 addresses used by wella.com: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
18.239.18.26Website18.239.18.0/24
18.239.18.39Website18.239.18.0/24
18.239.18.41Website18.239.18.0/24
18.239.18.9Website18.239.18.0/24
204.74.111.1Name server udns2.cscdns.uk204.74.111.0/24
204.74.66.1Name server udns1.cscdns.net204.74.66.0/24
52.101.50.4Mail server wella-com.mail.protection.outlook.com52.101.50.0/24
198.203.169.10Authorized by SPF198.203.169.0/24
92.103.63.132Authorized by SPF92.103.63.0/24
208.84.65.221Authorized by SPF208.84.65.0/24
208.86.201.177Authorized by SPF208.86.201.0/24
92.103.63.133Authorized by SPF92.103.63.0/24
194.15.48.173Authorized by SPF194.15.48.0/24
194.15.48.141Authorized by SPF194.15.48.0/24
172.210.94.127Authorized by SPF172.210.94.0/24
52.190.47.198Authorized by SPF52.190.47.0/24
35.242.247.107Authorized by SPF35.242.247.0/24
34.107.8.58Authorized by SPF34.107.8.0/24
168.245.98.23Authorized by SPF168.245.98.0/24

WHOIS of the domain wella.com

Domain Name: WELLA.COM
   Registry Domain ID: 39669_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.corporatedomains.com
   Registrar URL: http://cscdbs.com
   Updated Date: 2026-01-01T06:06:01Z
   Creation Date: 1996-01-06T05:00:00Z
   Registry Expiry Date: 2027-01-05T05:00:00Z
   Registrar: CSC Corporate Domains, Inc.
   Registrar IANA ID: 299
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: 8887802723
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Domain Status: serverDeleteProhibited https://icann.org/epp#serverDeleteProhibited
   Domain Status: serverTransferProhibited https://icann.org/epp#serverTransferProhibited
   Domain Status: serverUpdateProhibited https://icann.org/epp#serverUpdateProhibited
   Name Server: UDNS1.CSCDNS.NET
   Name Server: UDNS2.CSCDNS.UK
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-02T00:10:28Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar.  Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability.  VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.