AI 产品解读Proxy/VPN tool to help users in China access Google services and other geo-restricted websites
Enables users in China to bypass geographic restrictions and access Google Search, Gmail, Google+, and other blocked websites, while also solving Chrome extension auto-update issues
Extension starts automatically, calls cron_chrome_session() every 180 minutes to fetch proxy configuration from ghelper.net API servers, configures Chrome proxy settings via PAC scripts, and renders popup/options UI from server-side endpoints. User interacts with server-rendered HTML forms for login and settings.
Automatic browser proxy configuration via PAC scriptsPeriodic proxy session refresh via API serversDNS-over-HTTPS resolution for API endpoint discoveryAuto-detection and disabling of competing proxy extensionsServer-side rendered UI for settings and statusSpeed testing for proxy servers
- 目标用户
- Researchers and academics / Cross-border e-commerce workers / Overseas shopping users / Developers / Users in China needing access to Google services
- Extension uses server-rendered UI (popup and options pages fetch HTML from API endpoints), making it impossible to fully analyze the login and payment flows from static code alone
- The minified JS files obscure detailed logic
- Cannot determine if ghelper.net has paid plans from extension code alone
付费分析未识别到付费功能
No payment processing code found in the extension source. No keywords like 'premium', 'subscription', 'upgrade', 'price', 'pay', '会员', 'vip' found. No Stripe, PayPal, or other payment platform references. The 'pro' keyword matches are all false positives from CSS vendor prefixes (progid:). The extension itself does not gate features behind payment UI or billing APIs. However, as a proxy service, ghelper.net may have paid plans that are not visible in the extension code.
- 置信度
- 70
- 支付平台
- --
- 来源
- AI / 中
- 需要登录
- 是
- 登录理由
- The extension contains a complete login form CSS (login.css with .form-signin styles for input[type='email'] and input[type='password']), a token-based authentication system where tokens are stored in chrome.storage.local and sent to the /session API endpoint, and server-rendered UI from ghelper.net API. The set_token handler in options.min.js confirms the server can set authentication tokens. While the core proxy function runs automatically via cron_chrome_session(), the login infrastructure and token system indicate the destination service (ghelper.net) requires authentication.