Domain TLD Risk Scorer

3.45

Derivation Chain

Step 1 .online domain issues trending

→

Step 2 Domain selection decision tool

→

Step 3 TLD-specific risk data service

Problem

As new TLDs like .online increasingly cause penalties in spam filters, email deliverability, and SEO, Startups and solo developers fail to assess TLD-specific risks before choosing a domain, resulting in emails landing in spam folders or SEO penalties after launch. Switching TLDs requires redirect configuration, certificate reissuance, and SEO resets, costing an average of 2–4 weeks and $375–$1,500 (50–200만원).

Solution

Enter a domain name to get real-time scores for TLD-specific spam blacklist rates, major email service (Gmail, Outlook) deliverability rates, and Google SEO visibility scores. Provides alternative TLD recommendations and a migration checklist.

Target: Early-stage Startup CTOs/developers (ages 20–30s), solo SaaS developers, small agencies

Revenue Model: Premium Monthly $3.70 (4,900원) (unlimited lookups + monitoring alerts), Free Plan (5 lookups/month), API Per Transaction $0.07 (100원)

Ecosystem Role: Supplier

MVP Estimate: 2_weeks

NUMR-V Scores

N Novelty

4.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 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 (67%)

Tech Complexity

29.3/40

Data Availability

17.5/25

MVP Timeline

20.0/20

API Bonus

0.0/15

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 (56/100)

Competition

8.0/20

Market Demand

6.2/20

Timing

14.0/20

Revenue Signals

7.5/15

Pick-Axe Fit

10.5/15

Solo Buildability

10.0/10

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

Backend [medium] Data Pipeline [medium] Frontend [low]

Dashboard