← GVS Technologies
GVS Technologies · Security tooling

Email Validator

Connect your inbox, select the messages you're unsure about — or select all — and click Validate. Every message gets a glass-box verdict: Authenticated, To be Ignored, or To be Deleted. Review the reasoning, then apply the recommended action with one click.

On-device scoring, always Glass-box — every point explained You approve every action before it runs
Scope, disclosed: connecting your inbox is genuinely live — it uses Google's own client-side sign-in (Google Identity Services), so your inbox is read and modified directly from your browser using a token Google issues to you; GVS never sees your mail or your credentials. The one real friction: Google requires the account moving mail to be registered as a "test user" on this tool's OAuth screen until the app goes through Google's verification review — see setup below. That's Google's policy for any app requesting mailbox-modify access, not a GVS limitation.

1 Connect your inbox

Not connected

Need a Client ID first? Jump to the one-time setup panel.

2 Select and validate

Connect your inbox above, then click "Load inbox" to see your latest messages here.

＋ Or validate one email manually

For a forwarded email, a screenshot you've transcribed, or anything outside your connected inbox — paste the raw headers and body.

3 Log

Every validation — from your inbox or pasted manually — lands here, including which action was actually applied.

DateSubjectFromVerdictScoreAction taken

4 Parameters

Every weight and list below drives the scoring engine directly. A protected core (the flag names the engine keys off) can't be deleted, only tuned.

Scoring weights
Verdict thresholds
Authenticated below
To be Deleted at or above

Anything between the two is "To be Ignored" — moved to Spam.

Trusted domains (never flagged for mismatch)
Watched brand names (impersonation check)

5 Explain a verdict (optional, AI-assisted)

Translates an already-computed score into plain language — it never sets or changes the verdict. Your API key stays in this browser and goes directly to Anthropic, never to GVS.

⚙ One-time setup: connecting Gmail

Why this step exists: Google requires every app that reads or modifies a mailbox to have its own registered identity (an OAuth Client ID) — there's no way around this, for GVS or anyone else. It takes about five minutes, is free, and the Client ID itself is not a secret (it's safe to put directly in this page's code).
  1. Go to Google Cloud Console → Credentials and create a project (any name).
  2. Enable the Gmail API for that project (APIs & Services → Library).
  3. Configure the OAuth consent screen — External, add yourself under "Test users" so the unverified-app warning doesn't block you.
  4. Create an OAuth Client ID of type "Web application." Add this tool's exact URL (e.g. https://gvsgroup.netlify.app) under "Authorized JavaScript origins."
  5. Paste the Client ID below — it's saved only in this browser.

Going beyond your own account: while the app is unverified, only the Google accounts you've explicitly added as test users (up to 100) can connect. To let any of your users connect without a warning screen, submit the app for Google's OAuth verification — required for the gmail.modify scope, and can take one to a few weeks. This is a real step, not a formality to skip.