Is gawker.com down or not working?

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

Add comment

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

gawker.com outage reports in the last 24 hours

gawker.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:

Gawker

Main page description:

Gawker. It's a website on the internet.

Protocol:

https

Status code:

200

Page size:

12.8 KB

Response time:

0.413sec.

IP:

75.2.60.5

Response headers:

age:	0
cache-control:	private,no-cache,no-store,max-age=0,must-revalidate
cache-status:	"Netlify Durable"; fwd=miss, "Netlify Edge"; fwd=miss
content-type:	text/html; charset=utf-8
date:	Tue, 01 Oct 2024 07:58:49 GMT
netlify-vary:	cookie=__next_preview_data:presence\|__prerender_bypass:presence,query
server:	Netlify
strict-transport-security:	max-age=31536000
vary:	RSC,Next-Router-State-Tree,Next-Router-Prefetch,Accept-Encoding
x-middleware-next:	1
x-nf-render-mode:	ssr
x-nf-request-id:	01J93HDK5A4WXGNVQ5D0F1ENRB
x-powered-by:	Next.js
connection:	close
transfer-encoding:	chunked

DNS records:

A	address	75.2.60.5
A	ttl	300
MX	exchange	acjftnpzlguzam4jwnhybkolodlp3ziavgurt3jt7q3qppxvh5gq.mx-verification.google.com
MX	priority	15
MX	exchange	alt2.aspmx.l.google.com
MX	priority	5
MX	exchange	aspmx.l.google.com
MX	priority	1
MX	exchange	alt1.aspmx.l.google.com
MX	priority	5
MX	exchange	alt4.aspmx.l.google.com
MX	priority	10
MX	exchange	alt3.aspmx.l.google.com
MX	priority	10
NS	value	ns-1588.awsdns-06.co.uk
NS	value	ns-47.awsdns-05.com
NS	value	ns-1377.awsdns-44.org
NS	value	ns-719.awsdns-25.net
TXT	entries	google-gws-recovery-domain-verification=47827603
SOA	nsname	ns-47.awsdns-05.com
	hostmaster	awsdns-hostmaster.amazon.com
	serial	1
	refresh	7200
	retry	900
	expire	1209600
	minttl	86400

SEO headers

h1 Gawker. It's a website on the internet.

h3 IMPORTANT STORIES:

h4 KRIS KRISTOFFERSON LEAVES THE STAGE: A STAR IS GONE AT 88 2024-09-29

How to solve problems with gawker.com

Errors on the gawker.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 gawker.com on your own.