Skip to content

Updated

Google "This browser or app may not be secure":
Fix

  1. Google's help page says it may block sign-in from browsers that do not support JavaScript, from insecure or unsupported extensions, from browsers controlled by software automation or embedded in another app, from outdated versions, and when a firewall, proxy or antivirus gets in the way.
  2. In a fingerprint browser the usual fixes are to update the browser core, sign in in a clean profile without extensions, sign in by hand rather than through a script, and keep one stable IP for the account.

Check it right after buyingExample output

curl -x http://USER:PASS@HOST:PORT https://ipinfo.io/json

ip
203.0.113.24
country
US
Matches the country you picked
Day 15
203.0.113.24
Same address for the whole term
Example addresses (203.0.113.0/24), not real exits
01 / 07What causes this message

Google's own list of causes is short; in a fingerprint browser the likely ones are an old core, extensions, automation and security software.

What causes this message

Google lists these causes: a browser that does not support JavaScript or has it off; extensions that are insecure or unsupported; a browser that is driven by software automation or embedded in another app; an outdated version; High or Strict privacy settings in browsers other than Chrome; a firewall, proxy or antivirus; and security rules set by a company.

In a fingerprint or Chromium-based browser the ones that apply most often are an old browser core, extensions added to the profile, an automation tool controlling the window, and a proxy or security software in the path.

Cause, check and fix

Cause, check and fix
ItemHow to checkWhat to do
Old browser coreLook at the browser or core version in the profile settings.Update the browser and the core, then open a new profile.
ExtensionsList the extensions in the profile.Turn them off while signing in and turn them back on afterwards.
Automation or embedded windowIs a script or another app driving the window?Sign in by hand in a normal browser window.
JavaScript off or strict privacyCheck the site settings for google.com.Turn on JavaScript and allow www.google.com.
Proxy or security softwareTemporarily switch off the firewall, antivirus or other proxy to test.If sign-in then works, allow Google in that software instead of leaving it off.
Company accountIs it a work or school account?Ask your administrator about company security settings.

From Google Account Help, read 20 November 2026.

Where the IP and profile signals fit in

Google's page does not list the IP address as a cause, so first work through the list above. If sign-in works from one browser and not from another, compare them.

For an account you keep for a long time, make the signals agree: one stable IP in the country where the account is based, a time zone and language that match it, and a browser that is up to date. If Google asks you to verify your identity or phone, complete it honestly.

Fix it in order

  1. Step 1

    Update the browser and its core, and open a fresh profile with no add-ons.

  2. Step 2

    Check the exit IP through the proxy with https://ipinfo.io/json so you know the profile really uses it.

  3. Step 3

    Turn on JavaScript, allow www.google.com, and turn off the browser add-ons you can.

  4. Step 4

    Sign in by hand. If a script or another app is driving the window, close it and use a normal window.

  5. Step 5

    If it still fails, try a different supported browser such as Chrome or Firefox once, to see whether the profile or the account is the cause.

Confirm the proxy exit outside the browser

curl -x http://LOGIN:PASSWORD@HOST:PORT https://ipinfo.io/json

Example only: replace the placeholders with the values from My assets. HTTP is port 2222 on Proxy302.

Questions about this Google message

What does "This browser or app may not be secure" mean?

Google may block sign-in from a browser or app it does not consider secure: no JavaScript, an unsupported or outdated browser, risky extensions, automation or an embedded window, or security software in the way.

Why does it appear in a fingerprint browser?

Fingerprint browsers are built on Chromium, so an old core, extensions in the profile or an automation tool controlling the window can match the causes Google lists.

Does changing the proxy fix it?

Google's page lists a proxy only as software that can get in the way. Test without it once; if sign-in then works, check the proxy and security software.

Will it stop for good after a fix?

No one can promise that. Keep the browser current, sign in by hand and keep the account's IP, time zone and language consistent.

Further reading

Setup guides Proxy302 publishes on GitHub on the same topic:

Reference links

2
  1. Google Account Help: Sign in with a supported browser

    Official documentation · Confirmed on:

    Read on 20 November 2026: Google may block sign-in from browsers that do not support JavaScript, have it off, or are not supported; insecure or unsupported extensions; browsers controlled by software automation or embedded in another app; outdated versions; High or Strict privacy settings on browsers other than Chrome; firewall, proxy or antivirus; company security settings. Listed fixes: use a supported browser (Chrome, Safari, Firefox, Opera, Edge), turn on JavaScript, turn off extensions while signing in, update the browser, allow www.google.com, check security software, ask the administrator.

  2. Proxy302 product facts and price list

    Product observation · Confirmed on:

    Product facts file of the site (values checked against the console, the backend and the price table on 18-19 October 2026): products, prices in US$ (1 PTC = US$1), lease terms, protocols and ports, countries, quantity limits, no free trial.

Ready to try it?

Create an account, top up once, then pick rotating residential, static ISP or datacenter IPs and have one running in your browser within minutes.