How we measure

Every number in a report has a source and a measurement time. This page explains what we check, how the score is calculated and when we show a price range.

What we load

For each analysis our server requests the start page via HTTP and HTTPS, robots.txt and the XML sitemap, performs one TLS handshake and reads public DNS records. Registration data comes from the registry via RDAP. If configured, speed data comes from Google PageSpeed Insights and the Chrome UX Report.

We never run vulnerability scans, never log in and never follow links beyond these pages. Our crawler does not access private networks.

The technical health score

Each scored check has a fixed weight. A good result earns the full weight, a result to improve half of it, a problem nothing. Informational results and data that is not available are not scored. The score is the share of points reached.

Area	Checks and weights
Reachability	Website responds (10), Redirects (1), IPv4 address (5), Name servers (2), Sender policy (SPF) (1), DMARC policy (1)
Security	HTTPS available (8), HTTP redirects to HTTPS (5), Certificate (8), Certificate valid for (4), TLS version (3), HSTS (3), Content Security Policy (2), MIME sniffing protection (1), Clickjacking protection (1), Software versions hidden (1)
Search engines	Page title (4), Meta description (3), Main heading (H1) (2), Allowed in search results (3), Mobile viewport (5), Language declared (1), XML sitemap (2), robots.txt (1), Image descriptions (alt) (1)
Speed	Server response (4), Compression (2), HTML size (1), Lighthouse score (mobile) (5), Core Web Vitals (5)

The Seoda Score

The Seoda Score summarises how established a website is, on a scale from 0 to 100. It only uses public, verifiable signals. A component without data is left out and lowers the confidence – it is never guessed.

Component	Weight	Source
Links from other websites	35 %	Open PageRank (based on Common Crawl link data), 0–10 scaled to 0–100
Popularity	25 %	Tranco top 1 million list, updated weekly; rank 1 = 100, rank 1,000,000 ≈ 22, not listed = 5
Age	10 %	Registration date (RDAP) or first capture in the Internet Archive; 10 points per year, maximum 100
Real visitor data	10 %	Chrome UX Report: Google only publishes data for websites with enough real visitors
Technical health	20 %	The technical health score described above

A score is only shown when components with at least 45 % of the total weight have data.

Domain price ranges

A price range is calculated only from documented sales of comparable domain names: same extension, a length within two characters, and the same use of hyphens and digits. At least 5 such sales are required.

The range shown is the middle half of these prices (25th to 75th percentile), rounded to two significant digits. If too few comparable sales exist, no range is shown.

Estimated domain value

If there are not enough comparable sales, the report shows an automatic estimate, clearly marked as such. It starts from a base value for the extension and is multiplied by factors for length, hyphens and digits, age, links from other websites, popularity and a working website. The range shown is 60 % to 160 % of the calculated value, rounded to two significant digits.

Factor	Effect
Extension	.com 400 €, .de 300 €, .ai 250 €, .io 200 €, .net/.org 150 €, others 60 €
Length of the name	≤ 3: × 15 · ≤ 5: × 6 · ≤ 8: × 3 · ≤ 12: × 1,5 · ≤ 16: × 1 · longer: × 0,6
Hyphens / digits	× 0,5 / × 0,6
Age	+5 % per year, up to 20 years
Links (Open PageRank)	× (1 + PR² / 4)
Popularity (Tranco rank)	× (7 − log₁₀ rank)^1,5
Working website	× 1,2

The estimate concerns the name only. The value of a website business depends on its earnings – use the website value calculator for that.

What a report is not

A report is not a business valuation. The value of a running website depends on revenue, costs, traffic sources and risks that are not visible from outside. Those can only be assessed with data provided by the owner.