B

PhishGuard: Real-Time Phishing Link Detector

3.15

Derivation Chain

Step 1 Recurring scam patterns targeting tech workers
→
Step 2 Phishing/scam URL detection service

Competitor references

No usable source links are available for this idea. Its signal notes and scores need independent verification.

Problem

Even IT professionals are repeatedly falling for sophisticated phishing links (fake SaaS login pages, fake open-source donation pages, fake job offers, etc.). In Korea specifically, phishing links distributed via KakaoTalk and Telegram bypass traditional email security filters, and post-fraud credit card refund processes take an average of 2-4 weeks.

Solution

When a URL shared via KakaoTalk, Telegram, or Slack is submitted through copy-paste or the share function, the service: (1) instantly analyzes domain creation date, SSL certificate, and WHOIS information, (2) cross-references known phishing databases (PhishTank, OpenPhish), and (3) returns a page screenshot with highlighted risk factors—all within 3 seconds.

Target: IT company employees (ages 25-50), security leads at small IT teams (5-30 people), Freelancer developers
Revenue Model: Premium: Free (30 lookups/month) / Pro $14/month (unlimited lookups, API key, Slack bot integration) / Team $37/month (team dashboard, phishing attempt analytics)
Ecosystem Role: Infrastructure
MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty
2.0/5
U Urgency
3.0/5
M Market
3.0/5
R Realizability
4.0/5
V Validation
3.0/5
NUMR-V Scoring System
N Novelty1-5How uncommon the service is in market context.
U Urgency1-5How urgently users need this problem solved now.
M Market1-5Market size and growth potential from proxy indicators.
R Realizability1-5Buildability for a small team with realistic constraints.
V Validation1-5Validation signal quality from competition and demand data.
N=.15 U=.20 M=.15 R=.30 V=.20

Feasibility (70%)

Tech Complexity
32.0/40
Data Availability
17.5/25
MVP Timeline
20.0/20
API Bonus
0.0/15
Feasibility Breakdown
Tech Complexity/ 40Difficulty of core implementation stack.
Data Availability/ 25Practical availability and cost of required data.
MVP Timeline/ 20Expected time to ship a usable MVP.
API Bonus/ 15Bonus for viable public API leverage.

Market Validation (50/100)

Competition
8.0/20
Market Demand
6.2/20
Timing
14.0/20
Revenue Signals
7.5/15
Pick-Axe Fit
7.5/15
Solo Buildability
7.0/10
Validation Breakdown
Competition/ 20Signal quality from competitor landscape.
Market Demand/ 20Demand proxies from search and mention patterns.
Timing/ 20Fit with current shifts in tech, behavior, and regulation.
Revenue Signals/ 15Reference evidence for monetization viability.
Pick-Axe Fit/ 15How well the concept serves participants in a trend.
Solo Buildability/ 10Practicality for lean-team implementation.

Technical Requirements

Backend [medium] Frontend [low]
Dashboard