Skip to security report
Domain security and threat intelligence
lidosunover.app favicon

lidosunover.app

In short

lidosunover.app is a Lido impersonation page detected by PhishDestroy on 2026-10-23. Risk: critical (75/100). Registrar: PDR. Status: Last known active. Hosting: CloudFLARENET-EU. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

“Lido Fi — Money clarity and FI goals”

Registrar
PDR
Resolved IP
188.114.96.3
Registered
Aug 29, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Stored blocklist matches: 2 Automated brand label: Lido
OTX: 2 refs Oct 23, 2026 1 Report Sent CDN
API
This domain has been flagged as malicious
Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
Source evidenceVirusTotal 0 / 92 · OTX 2 references 6 sources

VirusTotal

0 / 92 engine detections

Open report

OTX

2 community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Critical
VirusTotal
0 / 92
OTX
2 community refs
Page captures
11

PhishDestroy threat report

Overview

PhishDestroy’s intake AI classified the site as malicious because it uses the Lido brand in its title “Lido Fi — Money clarity and FI goals,” implying an unauthenticated association. The page was first observed by PhishDestroy on 2026-10-23 and returned an HTTP 200 response at that time. The domain was registered on 2026-08-29, 55 days before the first sighting, and the internal PhishDestroy blocklist marks the domain as malicious.

How the scam works

Brand‑impersonation phishing creates a site that mimics a well‑known service’s name or visual cues to lure visitors into disclosing credentials, wallet addresses, or other sensitive data. The attacker relies on the trusted reputation of the brand to lower suspicion. While no credential‑capture form was observed on this page, the use of the Lido name alone is a known lure in crypto‑related phishing campaigns.

Evidence

VirusTotal scanned the domain on 2026-10-23 with 92 engines and reported zero detections and zero suspicious findings. Google Safe Browsing checked the same date and did not flag the site. URLScan captured the page on 2026-10-19 and again on 2026-10-23; its overall verdict was clean, though its machine‑learning engine assigned a malicious score of 97. OTX listed two pulses referencing the domain on 2026-10-23, while a later check reported zero pulses. PhishDestroy’s internal blocklist includes the domain as malicious.

Infrastructure

The domain was registered through PDR Ltd. d/b/a PublicDomainRegistry.com on 2026-08-29, with a client‑transfer‑prohibited status. The recorded DNS entries pointed to Cloudflare addresses 188.114.96.3, 188.114.97.9, 104.21.55.163 and others, and the site was served through Cloudflare’s network observed in the United Kingdom. The TLS certificate, issued by Google Trust Services, was valid from 2026-08-29 to 2026-11-27 and covered lidosunover.app and its subdomains.

What to do

Visitors should avoid entering any Lido‑related credentials, wallet addresses, or personal information on this site and, if they have already done so, change affected passwords and monitor associated crypto accounts. Defenders should add lidosunover.app to URL filtering and intrusion‑detection rules, review logs for connections to the recorded Cloudflare IPs, and treat any traffic to the domain as suspicious.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

URLScan · 2026-10-23T02:15:51Z

Observed: · Retrieved:

Uuid
01a1668a-d9f4-705e-ba1a-261c98e797a1
Final url
https://lidosunover.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://lidosunover.app/",
        "from": "http://lidosunover.app/",
        "status": 307
    }
]
Ip
104.21.55.163
Contacted domains
[
    "static.cloudflareinsights.com"
]
Contacted IP addresses
[
    "104.16.79.73",
    "104.21.55.163"
]
Asns
[
    "13335"
]
Document hash
3a59b5707cbd858a25eab3770ff93ea9318d3b0e98da79909b345e09f5229f0a
Script hashes
[
    "e6ea74505858857b2f83a43025d045dc53091ff77ac953d3897fa8d54bcf4dc0"
]
Globals
[
    "__cfBeacon"
]
Tls
{
    "san": [
        "lidosunover.app",
        "*.lidosunover.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "lidosunover.app",
    "protocol": "QUIC",
    "valid_to": "2026-11-27T16:52:51Z",
    "valid_from": "2026-08-29T15:54:21Z"
}
Domain age days
54
Apex age days
54
Tls age days
54
Tls valid days
90
Requests
7
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 97,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html"
}
Cloudflare Radar · 2026-10-23T01:42:58Z

Observed: · Retrieved:

Uuid
12e3783f-d010-40d0-be6f-0be795ba0499
Final url
https://lidosunover.app/
Status
200
History
[
    {
        "url": "https://lidosunover.app/",
        "status": 200
    }
]
DOM structure hash
5af4a0f9e8dea15eae0a1b18699425359c9f2028bc2337a3cd00134babd3b99c
Document hash
3a59b5707cbd858a25eab3770ff93ea9318d3b0e98da79909b345e09f5229f0a
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "lidosunover.app",
        "type": "A",
        "value": "104.21.55.163"
    },
    {
        "name": "lidosunover.app",
        "type": "A",
        "value": "172.67.149.51"
    },
    {
        "name": "lidosunover.app",
        "type": "AAAA",
        "value": "2606:4700:3032::6815:37a3"
    },
    {
        "name": "lidosunover.app",
        "type": "AAAA",
        "value": "2606:4700:3032::ac43:9533"
    }
]
Dnssec valid
false
Ip
104.21.55.163
VirusTotal · 2026-10-23T02:06:19Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 39
}
Reputation
0
Created
2026-08-29T00:00:00Z
First seen
2026-08-29T17:15:43Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.149.51"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "emma.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "neil.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.55.163"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3032::6815:37a3"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3032::ac43:9533"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "emma.ns.cloudflare.com"
    }
]
Dns at
2026-10-23T02:11:46Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "lidosunover.app",
        "*.lidosunover.app"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "4f8950b585d6029813c5a485f266d6fe",
    "sha256": "dc2e2b79ea8f65f3b93c0c1d500c9a9806951ba623c08cf923e19e7230ab4e73",
    "subject": "lidosunover.app",
    "valid_to": "2026-11-27T16:52:51Z",
    "valid_from": "2026-08-29T15:54:21Z"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "last changed": "2026-08-29T16:51:57Z",
        "registration": "2026-08-29T16:51:56Z",
        "registrar expiration": "2027-08-29T16:51:56Z",
        "last update of RDAP database": "2026-10-21T13:49:50Z"
    },
    "registrar": "PDR Ltd. d/b/a PublicDomainRegistry.com",
    "registrar_iana_id": "303"
}
Website checks · 2026-10-23T01:47:13Z
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "lidosunover.app"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true
}
Page title and metadata
{
    "title": "Lido Fi — Money clarity and FI goals",
    "themeColor": "#142b35",
    "description": "Lido Fi is a private personal-finance companion for accounts, budgets, and financial-independence goals.",
    "canonicalUrl": "https://lidosunover.app/"
}
Trackers
{
    "requests": 5
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 4,
        "tls": 23,
        "wait": 43,
        "connect": 9,
        "download": 0
    },
    "response_ms": 79
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 1082,
    "co2_grams": 0,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.33.211",
            "host": "neil.ns.cloudflare.com"
        },
        {
            "ip": "172.64.32.112",
            "host": "emma.ns.cloudflare.com"
        }
    ],
    "zone": "lidosunover.app"
}
Location
{
    "ip": "2a06:98c1:3121::9",
    "asn": "13335",
    "org": "CloudFLARENET-EU",
    "city": "London",
    "country": "GB"
}
Ssl
{
    "issuer": "Google Trust Services / WE1",
    "subject": "lidosunover.app"
}
DNS records
{
    "A": [
        "188.114.97.9",
        "188.114.96.9"
    ],
    "NS": [
        "neil.ns.cloudflare.com",
        "emma.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"emma.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2414006954, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "AAAA": [
        "2a06:98c1:3120::9",
        "2a06:98c1:3121::9"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2a06:98c1:3120::9",
    "family": 6
}
Redirects
{
    "chain": [
        "https://lidosunover.app"
    ]
}
Tech stack
{
    "technologies": [
        "Cloudflare",
        "PWA",
        "HTTP/3"
    ]
}
Page links
{
    "internal_count": 1
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html"
    }
}

Questions about lidosunover.app

Is lidosunover.app legit?

No. PhishDestroy classifies lidosunover.app as a Lido impersonation page (risk: critical, 75/100); it was first detected on 2026-10-23. Treat the site as unsafe.

Is lidosunover.app safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on lidosunover.app. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used lidosunover.app?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 11 captures

Observed page title
Lido Fi — Money clarity and FI goals
Automated brand references
Lido
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 35 days

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-10all-domainsblocklistcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar PDR IN(IN)
RegistrationCreated Aug 29, 2026 (54d · New) — Expires Aug 29, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 23, 2026
DOM Analysisanalyzed Oct 23, 2026score 75/1001 brand signal
Submitted URLhttp://lidosunover.app/
Favicon Hash
Case ID
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
188.114.96.3
Network ASN
AS13335
Organization
CloudFLARENET-EU
Observed location
London, GB
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • emma.ns.cloudflare.com
  • neil.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-08-29 15:54:21
Valid until
2026-11-27 16:52:51
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintdc2e2b79ea8f65f3b93c0c1d500c9a9806951ba623c08cf923e19e7230ab4e73
Certificate names · 2 SANs
  • lidosunover.app
  • *.lidosunover.app

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of lidosunover.app · checked Oct 23, 2026

97
Good
Performance
FCP
1.51s
First Contentful Paint
LCP
1.66s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
4.1s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://lidosunover.app/
Final URL: https://lidosunover.app/
Lido Fi — Money clarity and FI goals
Lido Fi is a private personal-finance companion for accounts, budgets, and financial-independence goals.
Response
HTTP 200
HTML body
1.1 KB
Compressed
573 B
Links
1 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 13
alt-svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a4ed1bcfb8817e59-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Fri, 23 Oct 2026 01:53:32 GMT
Last-Modified
Wed, 02 Sep 2026 18:44:40 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=2sL%2FEOgXLTCBXF8oin27GwuObKnD%2BGUTiyd7dqmKfl2NClVZUzypYCfjctqaGL3NjLQmB4Rp1Qe7XosY%2FZLAZKxewnNuBoMU2N9ZJjv5m%2F%2Fwlk4jW6FKCBTcHgytbCubVZ8%3
Server
cloudflare
Transfer-Encoding
chunked
Vary
accept-encoding

Values retained by the collector; long values may be shortened during collection.

Recorded activity

6 entries
  1. Abuse report sent

    PD-20261023-85C63D

    domain.manager@publicdomainregistry.com
  2. AlienVault OTX

    2 community references

    View source
  3. Google Safe Browsing

    No threat flag

    View source
  4. VirusTotal

    0/92 engine detections

    View source
  5. URLScan

    Page captured

    View source
  6. Added to PhishDestroy

    lidosunover.app

    View source

Lookalike domains

30 stored lookalike domains

ido.fi omission iido.fi homoglyph ildo.fi homoglyph kido.fi replacement ldio.fi transposition ldo.fi omission ledo.fi vowel-swap libo.fi homoglyph lico.fi replacement lid.fi omission lid0.fi homoglyph lida.fi vowel-swap
Show all (18)
liddo.fi repetition lidl.fi replacement lido-fi.com various lidoe.fi addition lidofi.com various lidoo.fi addition liido.fi repetition lilo.fi bitsquatting lio.fi omission liod.fi transposition liro.fi replacement lito.fi bitsquatting lldo.fi homoglyph llido.fi repetition ludo.fi replacement mido.fi bitsquatting nido.fi bitsquatting oido.fi replacement

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

lidosunover.app

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261023-85C63D Recipient: domain.manager@publicdomainregistry.com
PDF notice generated Notice text archived (348 chars)
Abuse notice text as sent to the provider
Registrar: PublicDomainRegistry (PDR Ltd.) (India)
Policy Violations: Explicit policy to immediately suspend domains used for phishing, 419 scams, identity fraud, malware distribution without prior notice
Applicable Laws: IT Act 2000 §§66C–66D (identity theft, cheating by personation), Indian Penal Code §420 / Bharatiya Nyaya Sanhita §318 (fraud)
Deep Analysis
Help & reporting

Were You Affected by This Site?

5 evidence signal groups linked 1 stored notification records Last known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Official reporting routes

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including lidosunover.app)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/lidosunover.app"
  title="PhishDestroy threat report for lidosunover.app"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>