Is wika.us down or not working?

What happened to wika.us, why did the website go down and not work? Here you can see who else is having the same problem with wika.us, 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, wika.us is working fine, but single failures are possible. If wika.us does not work for you, then report your problem and write a comment.

Add comment

What to do if the site wika.us is not available? Try our guide.

wika.us outage reports in the last 24 hours

wika.us - 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:

Home Page - WIKA USA - WIKA USA

Main page description:

Our new WIKA Claim: Smart in Sensing

Protocol:

https

Status code:

200

Page size:

199.0 KB

Response time:

0.987sec.

IP:

3.126.94.219

Response headers:

date:	Thu, 10 Oct 2024 07:38:06 GMT
content-type:	text/html; charset=UTF-8
transfer-encoding:	chunked
connection:	close
cache-control:	public, max-age=43200
x-xss-protection:	1; mode=block
x-content-type-options:	nosniff
referrer-policy:	strict-origin-when-cross-origin
last-modified:	Wed, 09 Oct 2024 08:40:08 GMT
vary:	Accept-Encoding
strict-transport-security:	max-age=31536000; includeSubDomains;
content-security-policy:	frame-ancestors https://*.wika.com/ 'self';
x-frame-options:	ALLOW-FROM https://apps.wika.com/
access-control-allow-headers:	content-type
access-control-allow-methods:	GET,OPTIONS,POST
access-control-allow-credentials:	true
cf-cache-status:	HIT
age:	21275
server:	cloudflare
cf-ray:	8d04f2eece316714-AMS

DNS records:

A	address	3.126.94.219
A	ttl	21600
AAAA	address	2a05:d014:532:ac00:ce4d:4314:607f:5520
AAAA	ttl	21600
MX	exchange	wika-us.mail.protection.outlook.com
MX	priority	100
NS	value	b.managed-ns.de
NS	value	a.managed-ns.com
TXT	entries	v=spf1 ip4:195.145.204.5 ip4:195.145.204.7 ip4:195.145.204.6 include:spf.protection.outlook.com -all
SOA	nsname	a.managed-ns.com
	hostmaster	domainadmin.managed-ip.com
	serial	2023115658
	refresh	43200
	retry	7200
	expire	1209600
	minttl	86400

SEO headers

h1 Smart in sensing

h2 Note

h3 Chillventa

h3 2024 AFPM Summit

h3 Mesures Solutions Expo

h3 75 years WIKA - look back with us

How to solve problems with wika.us

Errors on the wika.us 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 wika.us on your own.