AI 产品解读Gmail pre-send verification popup that intercepts the Send button and displays TO/CC/BCC recipients grouped by domain for manual confirmation before sending
Prevents accidental email mis-sending to wrong recipients by forcing a domain-by-domain visual confirmation step before the Send button becomes available
User composes email in Gmail → clicks Check button (red, replaces Send) → modal popup appears showing all recipients grouped by domain with color-coded TO/CC/BCC labels → user clicks each gray domain group to verify and turn green → when all groups are confirmed green, original Send/Send & Archive buttons appear → user clicks Send to deliver the email
Hides native Gmail Send button and replaces it with a 'Check' buttonOpens a modal dialog showing all TO/CC/BCC recipients grouped by email domainColor-coded display: TO=red, CC=green, BCC=purple for easy visual distinctionClick-to-confirm workflow: each domain group starts gray, user clicks to turn greenSend button only appears after all recipient groups are confirmed (turned green)Displays subject line and attachment list for additional pre-send verification
- 目标用户
- Japanese business professionals sending emails to customers / Users concerned about email mis-sending in corporate/enterprise environments / Gmail users who need an extra verification step before sending important emails
- ChEx.js is a utility library (~29KB) used for DOM observation; full audit not needed for login/paid decisions as it contains no auth or billing logic
- No background script exists - the extension is purely content-script based with minimal attack surface
付费分析未识别到付费功能
No payment, subscription, license, or upgrade mechanisms exist in the code. All keyword matches for 'paid', 'pro', 'license' are false positives from jQuery library internals (.prop() method calls, jQuery MIT license comments). No billing APIs, no premium feature gating, no payment UI.
- 置信度
- 98
- 支付平台
- --
- 来源
- AI / 高
- 需要登录
- 否
- 登录理由
- The extension is a pure content script injected into Gmail pages. It has no authentication UI, no login API calls, no user account system, and no external service communication. It simply modifies the Gmail compose UI. The only 'login' involved is the user's existing Gmail session, which is the destination service's login, not the extension's.