Do you think Amazon could be detecting GoLogin Browser?

I've been making Amazon buyer accounts, and lately things have been strange.

To rest your mind, I've done the following:
1. Residential Static Proxies
2. Random Agents
3. Account Warming: 15+ minutes of browsing Amazon
4. Signing up 24 hours after warming the account up.

My amazon accounts are going onto hold with me taking every step most of you would take. I'm stating to wonder if GoLogin itself is being detected somehow?

Yeah, it’s definitely possible. Amazon’s been getting smarter with browser-level fingerprints ,even with tools like GoLogin, some subtle traces can slip through. I’d try running the same flow on a different browser or setup just to rule that out. Sometimes that alone clears it up.

Disabled WebRTC can trigger it.

LazyMasterpiece8903 said:

I've been making Amazon buyer accounts, and lately things have been strange.

To rest your mind, I've done the following:
1. Residential Static Proxies
2. Random Agents
3. Account Warming: 15+ minutes of browsing Amazon
4. Signing up 24 hours after warming the account up.

My amazon accounts are going onto hold with me taking every step most of you would take. I'm stating to wonder if GoLogin itself is being detected somehow?

Click to expand...

Hi! Switch to rotating residential proxies or use proxies from multiple providers to diversify IP ranges. Ensure each account uses a unique IP that hasn’t been used for other Amazon accounts. Test proxy quality using tools like WhatWaf to check if they’re flagged by Amazon’s AWS WAF.

Also you should search in BHW similar treads, with this problem and solutions, I have seen it

Rankroverpro said:

Yes, possible. Amazon tracks fingerprinting, IP patterns, and behavior—so even with GoLogin, spoofing needs to be well-optimized.

Click to expand...

Would love to hear more about "behavior"? Scrolling, clicking - somethinge else?

LazyMasterpiece8903 said:

1. Residential Static Proxies

Click to expand...

Maybe it's flagged by Amazon. Try 10 more providers. I'm not exaggerating. It's not so easy to find clean proxies.

LazyMasterpiece8903 said:

2. Random Agents

Click to expand...

Use the most common fingerprints possible. Try using iphone.

Yes, even with precautions, platforms like Amazon can detect fingerprinting tools like GoLogin if their browser fingerprints or behavior patterns don’t fully mimic real users; combining proxies with more advanced fingerprint randomization and slower, more natural browsing patterns can help reduce holds.

Yeah I would test rotating residential proxies as well, if that solves the issue then the problem was the proxies

I’ve used GoLogin and other antidetect browsers for Amazon tasks, but detection is definitely possible. Amazon looks at fingerprint consistency, behavioral patterns, and even network anomalies. GoLogin helps spoof fingerprints, but if your proxies or cookies are sloppy, they’ll flag it. Best results came when I mirrored legit user behavior and rotated environments carefully—otherwise bans happen faster than you’d expect.

Make sure it uses all known browser fingerprints like canvas, webrts, sounds etc. Take in mind that sites can analyze user behaviour, not only browser fingerprints.

It's possible GoLogin itself is somehow flagged. Amazon gets pretty sophisticated with detection. Have you tried varying your browser fingerprint settings within GoLogin beyond just the default randomization?

LazyMasterpiece8903 said:

I've been making Amazon buyer accounts, and lately things have been strange.

To rest your mind, I've done the following:
1. Residential Static Proxies
2. Random Agents
3. Account Warming: 15+ minutes of browsing Amazon
4. Signing up 24 hours after warming the account up.

My amazon accounts are going onto hold with me taking every step most of you would take. I'm stating to wonder if GoLogin itself is being detected somehow?

Click to expand...

With the steps you have done, the possibility is not in the process but in the overall fingerprint. GoLogin is powerful but can still be detected by Amazon if you use duplicate configuration or not fine-tuned deeply. In addition, Amazon can cross-check IP activity + navigation behavior in great detail. Try switching to VM farm or Android emulation + App login, the trust rate will be significantly higher.

FindYourHost said:

Yeah, it’s definitely possible. Amazon’s been getting smarter with browser-level fingerprints ,even with tools like GoLogin, some subtle traces can slip through. I’d try running the same flow on a different browser or setup just to rule that out. Sometimes that alone clears it up.

Click to expand...

Yes amazing is detecting browsers and timezones canvas if your account don't match the cretiria it will be flagged suspicious

Yes, GoLogin might be getting detected. I had accounts banned too despite using proxies and warm-up. Switched to MultiloginPro, and hold rates dropped fast. It's more stealthy and reliable for Amazon setups.

Amazon's getting stricter, and even with good setups, small patterns can trigger holds. GoLogin might leave subtle fingerprints, or it could be proxy trust, device data, or repetitive setups. Try 4G/5G proxies, randomize device details more, and warm accounts over a few days. Also test with a different anti-detect browser to rule out tool issues.

LazyMasterpiece8903 said:

I've been making Amazon buyer accounts, and lately things have been strange.

To rest your mind, I've done the following:
1. Residential Static Proxies
2. Random Agents
3. Account Warming: 15+ minutes of browsing Amazon
4. Signing up 24 hours after warming the account up.

My amazon accounts are going onto hold with me taking every step most of you would take. I'm stating to wonder if GoLogin itself is being detected somehow?

Click to expand...

Nah, Gologin wokrs good, the problem is not there

Piter Grifi said:

Nah, Gologin wokrs good, the problem is not there

Click to expand...

I found out 1 issue with gologin was my PC was booting up with VPN active and it was causing the proxy on GoLogin to completely deactivate, causing my Ip to be revealed.

Whole thing about commercial anti-detect browsers is a bubble. Cybersecurity teams have been reverse engineering and researching mays to mitigate them for years now.

LazyMasterpiece8903 said:

I've been making Amazon buyer accounts, and lately things have been strange.

To rest your mind, I've done the following:
1. Residential Static Proxies
2. Random Agents
3. Account Warming: 15+ minutes of browsing Amazon
4. Signing up 24 hours after warming the account up.

My amazon accounts are going onto hold with me taking every step most of you would take. I'm stating to wonder if GoLogin itself is being detected somehow?

Click to expand...

Hey buddy, I also use GoLogin and I can tell you the problem isn’t really in the antidetect itself or the steps you listed, but in some of Amazon’s nuances. Here’s what I mean:

Platforms like Amazon use a multi-layered detection system — it collects hundreds of signals and makes a decision based on their combination. These are the most common triggers that usually lead to account holds:

1) IP / Network reputation. Even “residential” proxies carry history. If an IP was previously flagged for suspicious activity, it may already be on their radar.

2) Browser fingerprint. Things like User-Agent, canvas/WEBGL, fonts, timings, etc. form a unique signature. Tools like GoLogin help manage this, but if your fingerprint looks “auto-generated” or overlaps with other accounts — that’s a red flag.

3) Connections between accounts. Shared payment cards, phone numbers, email domains, shipping addresses, or even device IDs will instantly link accounts together.

4) Payment data. Fresh or anonymous cards, virtual cards with poor reputation, or unusual bank/currency combos often trigger extra checks.

5) On-site behavior. Unrealistic actions (jumping between many pages too fast, always direct URLs, or perfectly even browsing patterns) look bot-like.

6) Cookies / localStorage. If there are traces of previously blocked sessions (old cookies, tokens, identifiers), Amazon can connect your new profile to that history.

7) CAPTCHA / verification. Failed verifications, frequent phone resets, or account detail changes are another signal.

8) Tool & proxy quality. Bad proxies, poorly configured profiles (like leaking real MAC or network details), or buggy antidetect setups also give away signals.

Keep these in mind and you’ll reduce the chance of getting hit with holds. Hope this helps at least part of the issue

LazyMasterpiece8903 said:

I found out 1 issue with gologin was my PC was booting up with VPN active and it was causing the proxy on GoLogin to completely deactivate, causing my Ip to be revealed.

Click to expand...

Yeah, that’s a common pitfall. When you boot your PC with VPN already active, GoLogin (and pretty much any antidetect) can lose its proxy binding and default back to your real IP. That’s not just GoLogin-specific — it happens with most antidetect setups if there’s a conflicting extension or VPN layer in the mix. The problem is that antidetect browsers are designed to control the entire network route themselves. Once you add another tunneling tool (VPN, extension, system-level proxy), it breaks the chain and exposes your real connection. Amazon (or any platform) instantly sees the IP switch and flags it. Simple advice buddy Never run VPN, proxy, and antidetect together it breaks the chain and leaks your real IP. Stick to a single clean proxy inside your antidetect profile, and make sure to disable any auto-start VPNs or extensions before launch. Always check for leaks on sites like whoer.net, and if you need redundancy, just use a trusted proxy provider directly in the antidetect instead of stacking a VPN on top.