Is sick.com down or not working?

What happened to sick.com, why did the website go down and not work? Here you can see who else is having the same problem with sick.com, as well as possible solutions. According to our statistics, the following most often do not work: Website, Login, Account, Mobile App.

Current status: No failures

At the moment, according to our data, sick.com is working fine, but single failures are possible. If sick.com does not work for you, then report your problem and write a comment.

Add comment

What to do if the site sick.com is not available? Try our guide.

sick.com outage reports in the last 24 hours

sick.com - error and failure reports, troubleshooting methods

Leave your comment describing the failure and share with other users how to solve the problem.

No registration required.
Messages with obscene language and insults, as well as breaking the law, are not allowed to be published.
Active links in the text of the message are not published, but displayed in plain text.
It is forbidden to post your own and other people's personal data: addresses, phone numbers, emails, accounts in instant messengers, etc.

Your name:

Message:

Technical information

Main page title:

SICK | Sensor Intelligence

Protocol:

https

Status code:

200

Page size:

66.3 KB

Response time:

0.651sec.

IP:

80.72.131.66

Response headers:

content-type:	text/html; charset=UTF-8
last-modified:	Wed, 25 Sep 2024 09:37:40 GMT
etag:	W/"10901-192288b23be"
content-security-policy:	frame-ancestors https://.zscalertwo.net .sick.com .sickcn.net .sickcn.com *.crm4.dynamics.com;
access-control-allow-origin:	*
strict-transport-security:	max-age=31536000
cache-control:	public, max-age=3600
expires:	Tue, 01 Oct 2024 13:44:47 GMT
date:	Tue, 01 Oct 2024 12:44:47 GMT
transfer-encoding:	chunked
connection:	close, Transfer-Encoding
edge-cache-tag:	home, home
vary:	Accept-Encoding

DNS records:

A	address	80.72.131.66
A	ttl	300
MX	exchange	mxa-001e4f01.gslb.pphosted.com
MX	priority	10
MX	exchange	mxb-001e4f01.gslb.pphosted.com
MX	priority	10
NS	value	ns.sick.de
NS	value	pns.dtag.de
NS	value	secondary004.dtag.net
TXT	entries	mongodb-site-verification=NWEZOWcYam7dn3CzepxKEFTay8p8s0Cm
TXT	entries	v=spf1 include:spf.sick.com ?all
TXT	entries	google-site-verification=9t_HxLLW5Qd8ykuXqr8SIb9E0-GeVuYqqlMtAh5Mo8s
TXT	entries	NK3Ilqqelq1V799hx54C
TXT	entries	eea6c1a9-84d4-46d2-99eb-6676226f88b4
TXT	entries	google-site-verification: MC3uckrxXOWvJwmpsjwxloiZPWucB8ukLVS10BFaXQM
TXT	entries	successfactors-site-verification=YmY1ZmRlOGI1MTNlOTMzOTMwNGJjMTIxNGU4NjhhNjYwNjIyYmYzMzcwYjE3MzRiMDkwMDNhMzAxZWMxOTY2NA==
TXT	entries	ciscocidomainverification:6f51d0d88b5efdfcf1556f91927897e3dc134ce7839a0e95cabe4186b426f12b
SOA	nsname	ns.sick.de
	hostmaster	hostmaster.sick.de
	serial	2024092508
	refresh	28800
	retry	7200
	expire	604800
	minttl	300

How to solve problems with sick.com

Errors on the sick.com website can be either on the server side or on your side (client side). If there is practically nothing to be done about errors on the server side (it remains only to wait for the site to work again), then with errors on the client side it is possible to solve the problem with the availability of sick.com on your own.