Skip to main content

Error 404--Not Found

Cannot connect to the real www.google.co.in

Something is currently interfering with your secure connection to www.google.co.in.

Try to reload this page in a few minutes or after switching to a new network. If you have recently connected to a new Wi-Fi network, finish logging in before reloading.

If you were to visit www.google.co.in right now, you might share private information with an attacker. To protect your privacy, Chrome will not load the page until it can establish a secure connection to the real www.google.co.in.


Reload
What does this mean?

www.google.co.in normally uses encryption (SSL) to protect your information. When Chrome tried to connect to www.google.co.in this time, www.google.co.in returned unusual and incorrect credentials. Either an attacker is trying to pretend to be www.google.co.in, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Chrome stopped the connection before any data was exchanged.

Network errors and attacks are usually temporary, so this page will probably work later. You can also try switching to another network.


Technical details

www.google.co.in has asked Chrome to block any certificates with errors, but the certificate that Chrome received during this connection attempt has an error.
Error type: HSTS failure
Subject: *.google.co.in
Issuer: Google Internet Authority G2
Public key hashes: sha1/4u7GU93yrQnOkqbDam0NixsVRmo= sha256/D0ADPy8F/NxFbajtE2KWtRxccSORficjoXHYK0By5qE= sha1/Q9rWMO5T+KmAym79hfRqo3mQ4Oo= sha256/7HIpactkIAq2Y49orFOOQKurWxmmSFZhBCoQYcRhJ3Y= sha1/wHqYaI2J+6sFZAwRfap9ZbjKzE4= sha256/h6801m+z8v3zbgkRHpq6L29Esgfzhj89C1SyUCOQmqU= sha1/SOZo+SvSspXXR9gjIBBPM5iQn9Q= sha256//1aAzXOlcD2gSBegdf1GJQanNQbEuBoVg+9UlHjSZHY=


Error 404--Not Found

From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:

10.4.5 404 Not Found

The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.

Popular posts from this blog

BSNL Broadband error

Dear Sir/Madam
As you are a premium Broadband user of BSNL,We would like to inform that you have exhausted your mandated broadband speed (as per plan chosen by you).
We want you to continue browsing at higher speed.
Please click on "Upgrade" option as per your convenience.

SingPass

We are sorry but there seems to be an error.

We are unable to process your request at the moment. Please consider trying again.

If the problem persists, please contact the SingPass helpdesk with the Error code below for further assistance.

Error code: 137

SingPass Helpdesk at: +65 6643 0555 or e-mail: support@singpass.gov.sg
We apologise for any inconvenience caused.

tnpds - GOVERNMENT WEBSITE ERROR

Whitelabel Error Page This application has no explicit mapping for /error, so you are seeing this as a fallback.
Sat Oct 22 19:03:39 IST 2016 There was an unexpected error (type=Not Found, status=404). /pages/registeracard/home.xhtml Not Found in ExternalContext as a Resource https://tnpds.com/pages/registeracard/