Skip to main content
Screenshot of lido.fi

Live website intelligence

lido.fi

Lido Liquid Staking

Empowering and securing Ethereum since 2020

Last refresh

Updated 9h ago

Analyst read

Professional

25/100 trustFinance

Detected stack

React

Quick read

How to read lido.fi quickly

lido.fi looks like finance. Traffic estimates are limited, so use the trust and structure modules first. Current AI trust scoring is 25/100.

What to do next

  • The stack appears to include React.
  • Open the Traffic tab if you need audience scale and geography before outreach.
  • Open the Business tab if trust, monetization, or positioning is your first decision filter.

Provider Completeness

37/56 fields populated (66%)

11 providers

Providers with missing fields

publisher: 3/5files: 2/3traffic: 0/10whois: 4/6radar: 0/4
View field-level status

visual: 4/4

All expected fields present

meta: 3/3

All expected fields present

seo: 5/5

All expected fields present

dns: 4/4

All expected fields present

ads: 5/5

All expected fields present

publisher: 3/5

Missing: directCount, resellerCount

files: 2/3

Missing: robotsSitemapUrls

traffic: 0/10

Missing: monthlyVisits, globalRank, countryRank, bounceRate, avgVisitDuration, pagesPerVisit, topCountry, topRegions, topKeywords, trafficSources

whois: 4/6

Missing: whois.registrar, whois.expiresAt

radar: 0/4

Missing: globalRank, rankBucket, categories, sourceTimestamp

ai: 7/7

All expected fields present

Why this module matters

Technology data helps you qualify implementation maturity

This section shows what the site appears to run on, which providers support it, and whether the technical footprint looks modern, stable, and discoverable.

  • Stack tags are useful for sales, partnerships, and benchmarking.
  • DNS and files help you judge operational hygiene.
  • Provider health and timing reveal how complete the current read is.

Technology Stack

React

Infrastructure

DNS Provider

ProviderGoogle

Mail Exchange

MX 11 aspmx.l.google.com
MX 210 alt3.aspmx.l.google.com
MX 310 alt4.aspmx.l.google.com
MX 415 gkk2mpqucco5kghoyx6blnlo7vzvazchd6vzkvryrl4zc7wpiiwa.mx-verification.google.com
MX 55 alt1.aspmx.l.google.com
MX 65 alt2.aspmx.l.google.com

NS Records

NS 1jaime.ns.cloudflare.com
NS 2nancy.ns.cloudflare.com

TXT Records

"atlassian-domain-verification=2m38Ru/lN1P9wGbJ2ZCkPVeOVVlLE1t6ooVC5hTHX4h/WB9cYr2PZYdVkuQWzzbf"

"google-site-verification=3Ek4MVfdNsoX7P_tcYdkM1_4_F8nNzXN0dn3txb-QEQ"

"notion-domain-verification=6BDeHJSnPGN0DEItsIDuPDFCK0ZHERq8BIExfIwVgpF"

"slack-domain-verification=3HeiUExnMwKLvfOQZtehmWfSYoTPaB6wDIpPjhwl"

"v=spf1 a mx include:_spf.google.com -all"

"wallet-connect-dns-verification=3883e5c07bb7b57eab65b3b4c2e78df9959d73b6528a8734d00d913d62e8721a"

Technical Files

Robots

robots.txtFound

Sitemap

sitemap.xmlFound

Provider Health

whois.provider

traffic.provider

TRAFFIC_NO_DATA

Performance Metrics

0ms

Browser

6918ms

Fetch

0ms

AI

6918ms

Total

HTML Source Info

Source Methodnone
HTML Size0.0 KB

Keep exploring

Keep exploring from this report

Good pSEO pages should not strand the visitor. These links keep the journey moving through adjacent directories and comparable live reports.

Need fresh data for another site? Trigger a fresh analysis or open the directory to continue browsing.