Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 17. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
lidaa.shop favicon

lidaa.shop

In short

PhishDestroy describes lidaa.shop, a German-language page presenting a LIDL-branded clearance sale tied to store closures.

“500 Internal Server Error”

Review the evidence
Registrar
United StatesDynadot
Resolved IP
Canada104.16.210.68Cloudflare, Inc. · CDN
Registered
May 22, 2026
First observed
Oct 31, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 17/92 Spamhaus DBL: phishing domain
VirusTotal
17 / 92
engine detections ·
OTX
1
community references
URLScan
Malicious
engine verdict · score 82
Page captures
6
open gallery
Domain age
162 days
registered 2026-05-22 according to WHOIS
OTX: 1 ref Oct 31, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy describes lidaa.shop, a German-language page presenting a LIDL-branded clearance sale tied to store closures.

Critical
Status
Last known active
VirusTotal
17 / 92
Hosting
Canada104.16.210.68Cloudflare, Inc. · CDN
Registrar
United StatesDynadot
Registered
May 22, 2026
OTX
1 community ref
Page captures
6
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured lidaa.shop page is a German-language storefront landing page carrying LIDL branding in its logo and hero image of a LIDL Food Market store. It presents a clearance-sale headline about a Wohnungsauflosung (apartment liquidation) with limited-time savings, followed by explanatory copy claiming the discounts stem from closing roughly 30 branches and clearing stock. The main interaction is a search bar prompting "wonach suchst du?" alongside category links for tools, household goods, outdoor-sport, travel, and electronics.

The stored VirusTotal domain result reports 17 detections out of 92 engines. DNS8 reported "suspicious"; ESET reported "suspicious".

Source evidenceVirusTotal 17 / 92 · OTX 1 references 8 sources

VirusTotal

17 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 8 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
43
Malicious
12
Suspicious
5
Undetected
32

Vendor labels

DNS8
suspicious
ESET
suspicious
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Fortinet
spam
SOCRadar
phishing
Kaspersky
phishing
LevelBlue
suspicious
Seclookup
malicious
Gridinsoft
suspicious
BitDefender
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    104.16.210.68
  • TTL, seconds
    21600
    Type
    NS
    Value
    rudy.ns.cloudflare.com
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    anastasia.ns.cloudflare.com
  • TTL, seconds
    21600
    Type
    NS
    Value
    anastasia.ns.cloudflare.com

DNS records observed

JARM fingerprint

27d40d40d00040d00042d43d00041df04c41293ba84f6efe3a613b22f983e6

Certificate

Subject alternative names
  • lidaa.shop
Issuer
Google Trust Services / WE1
Serial
d33248e227c69ad713d5e8c071ba939a
SHA-256
64a18a0758ed95171b020266c7aeba1fe2ef5450d689558aab219a4c36cf88f2
Subject
lidaa.shop
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 43,
    "malicious": 12,
    "suspicious": 5,
    "undetected": 32
}
Vendor labels
{
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "spam",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "LevelBlue": "suspicious",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
First seen
2026-05-23T07:04:24Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "104.16.210.68"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "rudy.ns.cloudflare.com"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "anastasia.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "anastasia.ns.cloudflare.com"
    }
]
Dns at
2026-10-24T18:24:10Z
Jarm
27d40d40d00040d00042d43d00041df04c41293ba84f6efe3a613b22f983e6
Certificate
{
    "san": [
        "lidaa.shop"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "d33248e227c69ad713d5e8c071ba939a",
    "sha256": "64a18a0758ed95171b020266c7aeba1fe2ef5450d689558aab219a4c36cf88f2",
    "subject": "lidaa.shop",
    "valid_to": "2026-12-17T09:01:53Z",
    "valid_from": "2026-09-18T08:01:58Z"
}
Separate source record · 12 malicious + 5 suspicious / 92 · 2026-10-24 18:18:44 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-24T18:18:44Z
fetched_at
2026-10-31T00:28:19Z
stats
{"timeout":0,"harmless":43,"malicious":12,"suspicious":5,"undetected":32}

Spamhaus DBL

phishing domain

URLScan

Malicious · engine verdict · score 82

SHA-256 d078c8948d7f4c9c40bd89b1b4c1a44941a49c98d27df4e0ede12f5971521312

Open report
URLScanOriginal source recordObserved: 18 fields

Observed: · Retrieved:

Report ID

01a18f5f-dc9b-7531-a5f1-096a31d824d3

Final URL

https://lidaa.shop/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://lidaa.shop/
    From
    http://lidaa.shop/
    Status
    307

IP address

104.16.210.68

Contacted IP addresses

  • 104.16.210.68

Autonomous systems (ASN)

  • 13335

Document hash

6c5d74593398868b7285edba64f53c5db909a6fd2cf4052b5a617609d3b62b5d

Cookies

  • __cf_bm

TLS session and certificate

Subject alternative names
  • lidaa.shop
Cipher
AES_128_GCM
Issuer
WE1
Subject
lidaa.shop
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

160

Registered domain age, days

160

Certificate age, days

42

Certificate validity, days

90

Page requests

2

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
82
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
cloudflare
Content-type
text/html; charset=utf-8
Original source fields · JSON
Uuid
01a18f5f-dc9b-7531-a5f1-096a31d824d3
Final url
https://lidaa.shop/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://lidaa.shop/",
        "from": "http://lidaa.shop/",
        "status": 307
    }
]
Ip
104.16.210.68
Contacted IP addresses
[
    "104.16.210.68"
]
Asns
[
    "13335"
]
Document hash
6c5d74593398868b7285edba64f53c5db909a6fd2cf4052b5a617609d3b62b5d
Cookies
[
    "__cf_bm"
]
Tls
{
    "san": [
        "lidaa.shop"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "lidaa.shop",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-17T09:01:53Z",
    "valid_from": "2026-09-18T08:01:58Z"
}
Domain age days
160
Apex age days
160
Tls age days
42
Tls valid days
90
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 82,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8"
}
Separate monitor record · date not recorded

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
019e6377-ccde-7419-88c6-d53b33c8c634
score
null
malicious
null
result_at
null
enriched_at
2026-10-31T09:10:32Z
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":"2026-10-31 10:10:32"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

1 community reference

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 3 fields

Observed: · Retrieved:

Report ID

8ada2eb4-9674-49bc-8847-e65c2bd47830

Final URL

https://lidaa.shop/

Document hash

9bd5992bfa5bb77c2cda05f3e9434a65adbe6ac7ceba0f5bfd53582ae1255b40
Original source fields · JSON
Uuid
8ada2eb4-9674-49bc-8847-e65c2bd47830
Final url
https://lidaa.shop/
Document hash
9bd5992bfa5bb77c2cda05f3e9434a65adbe6ac7ceba0f5bfd53582ae1255b40

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

0 / 100 · heuristic score · 0 brand references · 0 classifications

Open report

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
lidaa.shop German LIDL-branded clearance sale landing page
ai_description
PhishDestroy describes lidaa.shop, a German-language page presenting a LIDL-branded clearance sale tied to store closures.
ai_summary
The captured lidaa.shop page is a German-language storefront landing page carrying LIDL branding in its logo and hero image of a LIDL Food Market store. It presents a clearance-sale headline about a Wohnungsauflosung (apartment liquidation) with limited-time savings, followed by explanatory copy claiming the discounts stem from closing roughly 30 branches and clearing stock. The main interaction is a search bar prompting "wonach suchst du?" alongside category links for tools, household goods, outdoor-sport, travel, and electronics. The stored VirusTotal domain result reports 17 detections out of 92 engines. DNS8 reported "suspicious"; ESET reported "suspicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-31 01:43:25
revision
9e310fc06e41fdac6773649655afe44324cb5b9cf69782c4d69fd9715c6a3aee
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

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

Collected source details

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

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 24 fields

Mail configuration

SPF lookups
0

CAA records

Domain
lidaa.shop

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
1
Archived days
2
Snapshots per day
0.07
Average page size, bytes
68820

Page title and metadata

Page title
500 Internal Server Error
Indexing directives
noindex, nofollow

Trackers

Requests
59
Observed services
  • Name
    Facebook
    Company
    Meta
    Country
    US
    Category
    Advertising
    Requests
    6
  • Name
    Google Translate
    Company
    Google
    Country
    US
    Category
    Customer Interaction
    Requests
    1
  • Name
    Amazon CloudFront
    Company
    Amazon
    Country
    US
    Category
    Hosting
    Requests
    6
  • Name
    Google APIs
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    5
  • Name
    Facebook Connect
    Company
    Meta
    Country
    US
    Category
    Site Analytics
    Requests
    6

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
12
TLS
41
Waiting
191
Connection
7
Download
0
Response time, ms
251

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
219
CO₂, grams
0
Cleaner than, %
95

DNS servers

Nameservers
  • IP address
    173.245.59.229
    Host
    rudy.ns.cloudflare.com
  • IP address
    172.64.34.227
    Host
    anastasia.ns.cloudflare.com
DNS zone
lidaa.shop

Cookies

Cookies
  • Name
    _fbp
  • Name
    _ageibg_vid
  • Name
    _ageibg_cvid
  • Name
    _ageibg_vs
  • Name
    utm_source
  • Name
    utm_medium
  • Name
    order_utm_history
  • Name
    landing_page
  • Name
    _ageibg_ka
  • Name
    first_http_referer
  • Name
    first_visit_time
  • Name
    currency_code
    Session cookie
    Yes
  • Name
    PHPSESSID
    Session cookie
    Yes
  • Name
    __cf_bm
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    None
  • Name
    _BZECZDD_ua
    Secure
    Yes
    SameSite
    None
  • Name
    _BZECZDD_pu
    Secure
    Yes
    SameSite
    None
  • Name
    _BZECZDD_tz
    Secure
    Yes
    SameSite
    None
  • Name
    _BZECZDD_ss
    Secure
    Yes
    SameSite
    None
  • Name
    _BZECZDD_lang
    Secure
    Yes
    SameSite
    None
  • Name
    _BZECZDD_vs
    Secure
    Yes
    SameSite
    None

Location

IP address
104.16.210.68
ASN
13335
Organization
Cloudflare, Inc.
City
Toronto
Country
CA

TLS certificate

Issuer
Google Trust Services / WE1
Subject
lidaa.shop

DNS records

A
  • 104.16.210.68
NS
  • anastasia.ns.cloudflare.com
  • rudy.ns.cloudflare.com
SOA
Primary nameserver
anastasia.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2415357905
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
104.16.210.68
IP version
4

Redirects

Redirect chain
  • https://lidaa.shop

Subdomains

Count
1
Subdomains
  • www.lidaa.shop

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html; charset=utf-8
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "lidaa.shop"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-31T00:34:42Z",
    "first": "2026-10-17T06:23:30Z",
    "changes": 1,
    "days_archived": 2,
    "scans_per_day": 0.07,
    "avg_page_bytes": 68820
}
Page title and metadata
{
    "title": "500 Internal Server Error",
    "robots": "noindex, nofollow"
}
Trackers
{
    "requests": 59,
    "trackers": [
        {
            "name": "Facebook",
            "company": "Meta",
            "country": "US",
            "category": "Advertising",
            "requests": 6
        },
        {
            "name": "Google Translate",
            "company": "Google",
            "country": "US",
            "category": "Customer Interaction",
            "requests": 1
        },
        {
            "name": "Amazon CloudFront",
            "company": "Amazon",
            "country": "US",
            "category": "Hosting",
            "requests": 6
        },
        {
            "name": "Google APIs",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 5
        },
        {
            "name": "Facebook Connect",
            "company": "Meta",
            "country": "US",
            "category": "Site Analytics",
            "requests": 6
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 12,
        "tls": 41,
        "wait": 191,
        "connect": 7,
        "download": 0
    },
    "response_ms": 251
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 219,
    "co2_grams": 0,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "173.245.59.229",
            "host": "rudy.ns.cloudflare.com"
        },
        {
            "ip": "172.64.34.227",
            "host": "anastasia.ns.cloudflare.com"
        }
    ],
    "zone": "lidaa.shop"
}
Cookies
{
    "cookies": [
        {
            "name": "_fbp"
        },
        {
            "name": "_ageibg_vid"
        },
        {
            "name": "_ageibg_cvid"
        },
        {
            "name": "_ageibg_vs"
        },
        {
            "name": "utm_source"
        },
        {
            "name": "utm_medium"
        },
        {
            "name": "order_utm_history"
        },
        {
            "name": "landing_page"
        },
        {
            "name": "_ageibg_ka"
        },
        {
            "name": "first_http_referer"
        },
        {
            "name": "first_visit_time"
        },
        {
            "name": "currency_code",
            "session": true
        },
        {
            "name": "PHPSESSID",
            "session": true
        },
        {
            "name": "__cf_bm",
            "secure": true,
            "http_only": true,
            "same_site": "None"
        },
        {
            "name": "_BZECZDD_ua",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BZECZDD_pu",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BZECZDD_tz",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BZECZDD_ss",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BZECZDD_lang",
            "secure": true,
            "same_site": "None"
        },
        {
            "name": "_BZECZDD_vs",
            "secure": true,
            "same_site": "None"
        }
    ]
}
Location
{
    "ip": "104.16.210.68",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "Toronto",
    "country": "CA"
}
Ssl
{
    "issuer": "Google Trust Services / WE1",
    "subject": "lidaa.shop"
}
DNS records
{
    "A": [
        "104.16.210.68"
    ],
    "NS": [
        "anastasia.ns.cloudflare.com",
        "rudy.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"anastasia.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2415357905, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}"
}
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": "104.16.210.68",
    "family": 4
}
Redirects
{
    "chain": [
        "https://lidaa.shop"
    ]
}
Subdomains
{
    "count": 1,
    "subdomains": [
        "www.lidaa.shop"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html; charset=utf-8"
    }
}

Questions about lidaa.shop

Is lidaa.shop legit?

PhishDestroy describes lidaa.shop, a German-language page presenting a LIDL-branded clearance sale tied to store closures.

Is lidaa.shop safe to connect a wallet?

This report does not record which wallet requests lidaa.shop makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used lidaa.shop?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 6 captures

URLScan · 2026-10-31 1 / 6 Used in the analysis Source file SHA-256: 190921cd8c448117be609b684ba81fe1fae27039d762b33b7f71a969482616ff SHA-256 of the prepared copy given to the model: d8ef814b627f1983d7d019810d770e92d0f9cc8451f5cd5445cded5fac50c972
SourceURLScan · 2026-10-31
Recorded
StateStored capture
Final URLhttps://lidaa.shop/
Position1 / 6
Open capture Source Report Wayback Download
All capture links and hashes (6)
Observed page title
500 Internal Server Error
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 46 days

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 82 report ↗
IP Context Canada104.16.210.68 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar Dynadot US(US)
Abuse contact["abuse@dynadot.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for lidaa.shop →
RegistrationCreated May 22, 2026 (162d) — Expires May 22, 2027
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 31, 2026
DOM Analysisanalyzed Oct 31, 2026score 0/100
Submitted URLhttp://lidaa.shop/
Favicon Hash
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.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada104.16.210.68
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
Cloudflare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • anastasia.ns.cloudflare.com
  • rudy.ns.cloudflare.com

SOA

  • nsname: anastasia.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2415357905
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-09-18 08:01:58
Valid until
2026-12-17 09:01:53
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint64a18a0758ed95171b020266c7aeba1fe2ef5450d689558aab219a4c36cf88f2
Certificate names · 1 SAN
  • lidaa.shop

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

viewdns.info · 104.16.210.68rapiddns.io
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.lidaa.shopDomain record
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

17 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
BitDefender
CyRadar
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
Seclookup
SOCRadar
Sophos
VIPRE
Webroot

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of lidaa.shop · checked Oct 31, 2026

97
Good
Performance
FCP
2.04 s
First Contentful Paint
LCP
2.04 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
12 ms
Total Blocking Time
SI
2.93 s
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 403
Requested URL: http://lidaa.shop/
Just a moment...
Response
HTTP 403
HTML body
5.5 KB
Compressed
3.2 KB
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=UTF-8
CF-Mitigated: challenge
Server: cloudflare
Content-Encoding: gzip
Security headers present
Content-Security-PolicyX-Frame-OptionsX-Content-Type-OptionsReferrer-PolicyPermissions-PolicyCross-Origin-Opener-PolicyCross-Origin-Resource-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 22
Accept-Ch
Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model,
alt-svc
h3=":443"; ma=86400
Cf-Mitigated
challenge
CF-RAY
a52e87f4aefd4219-EWR
Connection
close
Content-Encoding
gzip
Content-Security-Policy
default-src 'none'; script-src 'nonce-l8wKxHxyvKWBklAddfmH2t' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blo
Content-Type
text/html; charset=UTF-8
Critical-Ch
Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model,
Cross-Origin-Embedder-Policy
require-corp
Cross-Origin-Opener-Policy
same-origin
Cross-Origin-Resource-Policy
same-origin
Date
Sat, 31 Oct 2026 00:26:56 GMT
Origin-Agent-Cluster
?1
Permissions-Policy
accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=(),xr-spatial-tracking=*
Referrer-Policy
same-origin
Server
cloudflare
Server-Timing
chlray;desc="a52e87f4aefd4219"
Transfer-Encoding
chunked
Vary
accept-encoding
X-Content-Type-Options
nosniff
X-Frame-Options
SAMEORIGIN

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

Archived
Registration & observation details1

Availability observations

Last reachable observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Captured network requests

Network requests: 2 SHA-256 hashes: 2 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-31 00:39 UTC.

Open this scan on URLScan 01a18f5f-dc9b-7531-a5f1-096a31d824d3 ↗

Check for cloaking

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

Page titles differ

Our scanner could not complete this check.

Browser
500 Internal Server Error
Crawler
Discount Shop
lidaa.shop
Stored observation history1

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Domain monitor · First collection record

    Reachable

All retained availability observations3

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 01:35:07.000000
    Evidence SHA-256
    b7a909ca559e46199bcff90e7fac4dc497e8c03b92488189a3deec2004ae91f0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 01:35:07
    Evidence reason
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 01:35:07.000000
    Evidence SHA-256
    b7a909ca559e46199bcff90e7fac4dc497e8c03b92488189a3deec2004ae91f0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 01:35:07
    Evidence reason
  3. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 01:30:06.774818
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

Recorded events: 11. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    lidaa.shop detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 9 of 9
  • Spamhaus DBL
    Spamhaus DBL recorded: phishing domain
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 82
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 17/92
  • OTX Community References
    Community publication references on AlienVault OTX: 1. References are not vendor verdicts and are excluded from the evidence score.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

5 entries
  1. URLScan

    Page captured

    View source
  2. Wayback Machine

    Page archived

    View source
  3. AlienVault OTX

    1 community references

    View source
  4. Added to PhishDestroy

    lidaa.shop

    View source
  5. VirusTotal

    17/92 engine detections

    View source
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 17 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report OTX 1 ref WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

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

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

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.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

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 lidaa.shop)
  • 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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

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

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 →
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.

Request a correction or appeal How PhishDestroy works
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/lidaa.shop"
  title="PhishDestroy threat report for lidaa.shop"
  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>