Dataweaz

sika.com

Summary

Registrar
CSC Corporate Domains, Inc.
Status
clientTransferProhibited
Created on
July 30, 1995
Expires on
July 29, 2027
Name servers
ns04.sika.com, ns03.sika.com, ns02.sika.com, ns01.sika.com
Mail servers
mx1.sika.com, mx2.sika.com
DMARC
Reject
SPF
Strict
DKIM
No key found among the common selectors
Website
See the website

Spoofing protection (DMARC)

Reject

E-mails spoofing this domain are rejected.

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

Policy
Reject
Subdomain policy
Reject
Messages covered
100%
DKIM alignment
Relaxed
SPF alignment
Relaxed
Aggregate reports
[email protected]
Failure reports
—

Record

v=DMARC1; p=reject; rua=mailto:[email protected]; fo=1; pct=100; rf=afrf; ri=86400

Authorized senders (SPF)

Strict

E-mails sent by any other server are rejected.

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

RuleValueResult
ip4185.89.200.0Allowed
ip4185.89.200.1Allowed
mx—Allowed
all—Rejected

Top-level DNS lookups: 1 of 10 allowed

Record

v=spf1 ip4:185.89.200.0 ip4:185.89.200.1 mx -all

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 sika.com arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from sika.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 @sika.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

sika.com  MX  10 mx1.sika.com.
sika.com  MX  20 mx2.sika.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.sika.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

sika.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.sika.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.sika.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.sika.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.sika.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 sika.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.

No IP address: the domain does not point to any web server.

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
ns04.sika.com198.41.223.217
ns03.sika.com198.41.222.162
ns02.sika.com162.159.11.207
ns01.sika.com162.159.8.128

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @sika.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
5mx1.sika.com185.89.200.0
5mx2.sika.com185.89.200.1

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.sika.com.

NameContent
sika.comadobe-idp-site-verification=7203cfb5397aca5d7e61792859e7a4bc943068322f50a8c38d49b724be778f2e
sika.compardot682423=d8a55d768d375437e57ad3c41437fb0ccb2065e5025880e0c22d4c85aae7a3cd
sika.comdtm-domain-verification=Apaj82q8KdH58mjUY9c00T8JrL1xp6EJnJz_G3vYed8
sika.compardot682693=b8db6df44e7a8875e2aace56a7832a420047ea77dedf0f48dec7c5df081bad94
sika.compardot682683=5194809f6e37dcfd174db4851d51f1a3c988c7badc08ccbbd78f09dc9752241d
sika.comgoogle-site-verification=lLyJMXwWUMOrTQcPzTOGX8Yq-MGAd2o4UiNp2zEFxIY
sika.compardot682693=ffb0c392010b24b9032456ac203b3c44ece64c2f280daecbe0d66569abf186ed
sika.compardot682683=ba608e87fa910f19b36c1e00000c7c6c3d37f11cc0cabb486015c169c17f9340
sika.compardot789393=19b680fbd7ead57842216c7341c5653a736181c06faff4f46ad8b2e4b246eac9
sika.comsmartsheet-site-validation=wQfeWpo22dUisdAtMrBzk2w-NYpNiq_7
sika.comkvhfssmhnqztnhcctt1psp7m7c4sf9by
sika.comapple-domain-verification=3rD60XOKahFFdt7Y
sika.comQuoVadis=82b5562f-aee7-4758-a1d9-954d66bc244e
sika.compardot227082=7af0be7d25a5f98c056e22d5eb8ea942850c54ac8a294d944fa453594afd116e
sika.compardot682683=146fb78884309993d639d2302d283934bcd29657f994a4e43c356f2a6f354c65
sika.compardot682693=24b8ee7c32e2ef1f4d53a507214c23e2059ef4ad56e3bc934d0dcf6e5e077bed
sika.com4A719711-7B97-4729-88F5-03737323FBBA
sika.comanthropic-domain-verification-77k61r=IMwGGJz7L8hvZM5vFR0JtKI1b
sika.comtwilio-domain-verification=cec4739c7573f5817f3a80372b459618
sika.comteamviewer-sso-verification=f22541aa6f9e4b8d87de3c260388e569
sika.compardot789393=fcbc9dd9f0e2c7a4437239f1017bec88e70066c6c0cd55d3c4046e4bc4a1185a
sika.comrh5hnjybllll9320qkcpjsrvxyqj7qcr
sika.comEE66A23E-080F-4D88-A356-F4E3E9D45A3E
sika.compardot682693=ebc3f2b6429e164c52cac86199b0b5daa782bc66309f5f7e2f09ed0a6c442404
sika.comQuoVadis=6f46a37b-b3bc-4a60-a566-2e5f666b64e5
sika.compardot682423=8c53e45b9315405cfb41523a5f1307a69fddfc8bf8f4035b4633ddf6d56fffe9
sika.comv=spf1 ip4:185.89.200.0 ip4:185.89.200.1 mx -all
sika.comdtm-domain-verification=ujjpizL7etMaLJePSeo5U_V8EkwVrB5OobcqrWYScq0
sika.comgoogle-site-verification=OMj4kRUB_1s_pE_P9Ek2LR8teWAPGcDHy1vaNwHfVfU
sika.comgoogle-site-verification=91ftq2oYe3iL0qaoPyxGKnUR9e2TBtr_WoBKh4Q2ypc
sika.comgoogle-site-verification=Y6GCJy-RmqUmmzoHkbPqrayUWNZCojCtQ7WOUVtmWtU
sika.comMS=ms76565744
sika.comcisco-ci-domain-verification=135c10077fc22ff0c49e50cb0e8cbf6f86fc5343ce3603fbf8da9eb421a47790
sika.comswisssign-check=olXtB2vzqQGGNn3Y713sVL4cf84
sika.comatlassian-domain-verification=Yt3dodE50DcoI098Cuq3YbNtziMLM6VrGk2NIs98YcBT2kWf2J9gsPOXsPP5/GFv
_dmarc.sika.comv=DMARC1; p=reject; rua=mailto:[email protected]; fo=1; pct=100; rf=afrf; ri=86400

Related IP addresses

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

IP addressUsed for/24 block
198.41.223.217Name server ns04.sika.com198.41.223.0/24
198.41.222.162Name server ns03.sika.com198.41.222.0/24
162.159.11.207Name server ns02.sika.com162.159.11.0/24
162.159.8.128Name server ns01.sika.com162.159.8.0/24
185.89.200.0Mail server mx1.sika.com, Authorized by SPF185.89.200.0/24
185.89.200.1Mail server mx2.sika.com, Authorized by SPF185.89.200.0/24

WHOIS of the domain sika.com

Domain Name: SIKA.COM
   Registry Domain ID: 1821137_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.corporatedomains.com
   Registrar URL: http://cscdbs.com
   Updated Date: 2026-07-25T05:14:28Z
   Creation Date: 1995-07-30T04:00:00Z
   Registry Expiry Date: 2027-07-29T04: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: NS01.SIKA.COM
   Name Server: NS02.SIKA.COM
   Name Server: NS03.SIKA.COM
   Name Server: NS04.SIKA.COM
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-02T15:22:58Z <<<

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.