Gmail's asking for phone verification

sam.hunt0710

Elite Member
Executive VIP
Jr. VIP
Joined
Jan 8, 2010
Messages
13,650
Reaction score
7,714
Hello All

I am using AWS RDP for logging Gmail accounts .

After 1st login I am not making changes or doing any activity. After 24-36-48 hours when I trying to start work on those accounts either they are asking phone verification or QR code to be scanned.

I am not sure if I am doing anything wrong or everyone else is also facing same issue .

Would like to hear your suggestions / tips to avoid this or bypass this checkpoint.

Thanks
 
AWS RDP can be part of the problem because Google may see the login as coming from an unfamiliar environment or datacenter IP. I’d use a normal trusted device/network and complete the verification instead of trying to bypass the checkpoint.
 
AWS IPs are datacenter ranges that Google flags hard, so run the accounts on residential or mobile proxies instead and keep one IP fixed per account rather than sharing the RDP for all of them.
 
AWS IPs are datacenter ranges that Google flags hard, so run the accounts on residential or mobile proxies instead and keep one IP fixed per account rather than sharing the RDP for all of them.


I am using 1 RDP = 1 Gmail .

Sometime everything goes well and sometime its like no matter which region I choose for creating RDP , Gmails start asking for Phone Verification or to scan the qr code.
 
I am using 1 RDP = 1 Gmail .

Sometime everything goes well and sometime its like no matter which region I choose for creating RDP , Gmails start asking for Phone Verification or to scan the qr code.
Maybe you are using new Gmail? or Maybe AWS ip maybe flag by Google, Try to use different RDP than the AWS.
 
But what happens if you sms verify your gmail account, it works normally after that? because seems like you don't have too many emails, and if they work after verification just verify them, its like 7 cents per verification, and it's way cheaper than changing proxies. IMHO.
 
But what happens if you sms verify your gmail account, it works normally after that? because seems like you don't have too many emails, and if they work after verification just verify them, its like 7 cents per verification, and it's way cheaper than changing proxies. IMHO.
I have tried that too using smspva but then account getting suspended for multiple account abuse.

Previously this process was working fine for me 8/10 accounts I was able to work for long time. Currently its like 0/10 there is something off.

Maybe you are using new Gmail? or Maybe AWS ip maybe flag by Google, Try to use different RDP than the AWS.

Nopes I am not using new Gmail. I am purchasing Old Gmails.
 
AWS is a datacenter range, Google flags those hard, and a new login with zero activity for 24-48h is a classic trigger for the extra check. Residential or mobile IP, same one every time for each account, and don't jump between regions. Log in every few days and do normal stuff, plus add a recovery phone/email so you can pass the check when it shows up instead of losing the account
 
Since you're buying old gmails, the trigger is probably the jump from the seller's location to an AWS box. Ask the seller which country the accounts were created and used in, log in through a residential proxy from that same country and keep that IP fixed per account. If it still asks for a phone, verify with a number you can keep long term, google often asks for the same number again later and a one-time activation is gone by then.
 
the phone/qr prompt is google not trusting the session, fresh ip plus a new device fingerprint on an old account reads like a takeover to them. the rdp itself isnt the issue, its that every account logs in from the same box and ip. warm them slower and dont share one fingerprint across all of them
 
Back
Top