Is g.co down or not working?

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

Add comment

What to do if the site g.co is not available? Try our guide.

g.co outage reports in the last 24 hours

g.co - 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:

g.co

Protocol:

https

Status code:

200

Page size:

2.1 KB

Response time:

0.068sec.

IP:

142.250.179.206

Response headers:

accept-ranges:	bytes
vary:	Accept-Encoding
content-type:	text/html
content-security-policy-report-only:	script-src 'nonce-Z-MYzjg3eZUFxaXtxAX6aA' 'report-sample' 'strict-dynamic' 'unsafe-eval' 'unsafe-inline' http: https:; object-src 'none'; report-uri https://csp.withgoogle.com/csp/static-on-bigtable; base-uri 'none'
cross-origin-resource-policy:	cross-origin
cross-origin-opener-policy-report-only:	same-origin; report-to="static-on-bigtable"
report-to:	{"group":"static-on-bigtable","max_age":2592000,"endpoints":[{"url":"https://csp.withgoogle.com/csp/report-to/static-on-bigtable"}]}
content-length:	2190
date:	Tue, 01 Oct 2024 05:12:10 GMT
pragma:	no-cache
expires:	Fri, 01 Jan 1990 00:00:00 GMT
cache-control:	no-cache, must-revalidate
last-modified:	Tue, 17 Sep 2024 03:08:00 GMT
strict-transport-security:	max-age=31536000; preload
x-content-type-options:	nosniff
server:	sffe
x-xss-protection:	0
alt-svc:	h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
connection:	close

DNS records:

A	address	142.250.145.100
A	ttl	300
A	address	142.250.145.139
A	ttl	300
A	address	142.250.145.102
A	ttl	300
A	address	142.250.145.138
A	ttl	300
A	address	142.250.145.113
A	ttl	300
A	address	142.250.145.101
A	ttl	300
AAAA	address	2a00:1450:4013:c14::64
AAAA	ttl	300
AAAA	address	2a00:1450:4013:c14::71
AAAA	ttl	300
AAAA	address	2a00:1450:4013:c14::66
AAAA	ttl	300
AAAA	address	2a00:1450:4013:c14::8b
AAAA	ttl	300
NS	value	ns2.google.com
NS	value	ns4.google.com
NS	value	ns1.google.com
NS	value	ns3.google.com
TXT	entries	facebook-domain-verification=uaginhz5vhf6ac0jdcja536qidzm35
TXT	entries	v=spf1 -all
SOA	nsname	ns1.google.com
	hostmaster	dns-admin.google.com
	serial	680495531
	refresh	900
	retry	900
	expire	1800
	minttl	60
CAA	critical	0
CAA	issue	pki.goog

SEO headers

h2 g.co

h2 About g.co

How to solve problems with g.co

Errors on the g.co 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 g.co on your own.