A
Phishing Message Instant Analyzer
3.75
Derivation Chain
Step 1
Real-time digital financial fraud and phishing detection
→
Step 2
No way to instantly verify whether a suspicious text or link is safe when received
Problem
Smartphone users aged 50–60 receive an average of 2–3 smishing texts daily impersonating delivery notifications, health insurance refunds, or government benefits, but have no tool to verify authenticity in real time. The National Police Agency's 'CyberCop' requires filing a report and waiting for results, and carrier spam filters miss new tactics. A single wrong click causes an average of $9,000 in financial damage (per 2025 National Police Agency statistics, concentrated among ages 50–60), with a recovery rate below 30%.
Solution
A web page where users paste a suspicious message or URL for instant risk assessment on a 3-tier scale (Safe/Caution/Danger). The tool combines URL domain analysis (WHOIS registration date, SSL certificate, redirect chain), text pattern matching (impersonation keyword database), and cross-referencing against a recently reported URL database, presenting the reasoning behind each verdict. It also provides educational commentary explaining 'why you should be suspicious of this message.'
NUMR-V Scores
NUMR-V Scoring System
| N Novelty | 1-5 | How uncommon the service is in market context. |
| U Urgency | 1-5 | How urgently users need this problem solved now. |
| M Market | 1-5 | Market size and growth potential from proxy indicators. |
| R Realizability | 1-5 | Buildability for a small team with realistic constraints. |
| V Validation | 1-5 | Validation signal quality from competition and demand data. |
SaaS N=.15 U=.20 M=.15 R=.30 V=.20
Senior N=.25 U=.25 M=.05 R=.30 V=.15
Feasibility (68%)
Data Availability
18.3/25
Feasibility Breakdown
| Tech Complexity | / 40 | Difficulty of core implementation stack. |
| Data Availability | / 25 | Practical availability and cost of required data. |
| MVP Timeline | / 20 | Expected time to ship a usable MVP. |
| API Bonus | / 15 | Bonus for viable public API leverage. |
Market Validation (58/100)
Validation Breakdown
| Competition | / 20 | Signal quality from competitor landscape. |
| Market Demand | / 20 | Demand proxies from search and mention patterns. |
| Timing | / 20 | Fit with current shifts in tech, behavior, and regulation. |
| Revenue Signals | / 15 | Reference evidence for monetization viability. |
| Pick-Axe Fit | / 15 | How well the concept serves participants in a trend. |
| Solo Buildability | / 10 | Practicality for lean-team implementation. |
Technical Requirements
Frontend [low]
Backend [medium]
Data Pipeline [medium]