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
lottiefiles.help favicon

lottiefiles.help

In short

PhishDestroy records that the captured lottiefiles.help page rendered blank, with no visible content or interaction available.

Review the evidence
Registrar
United StatesNameSilo
Resolved IP
United Kingdom188.114.96.3CloudFLARENET-EU · CDN
Registered
Jan 30, 2026
First observed
Oct 31, 2026
PhishDestroy assessment Critical
95/100
Evidence score
Availability Server error The latest stored response was inconclusive Observed HTTP probe
Risk signals
VirusTotal detections: 17/92 Spamhaus DBL: spam domain
VirusTotal
17 / 92
engine detections ·
OTX
1
community references
URLScan
Malicious
engine verdict · score 92
Cloudflare Radar
Phishing
Page captures
10
open gallery
Domain age
273 days
registered 2026-01-30 according to WHOIS
OTX: 1 ref Oct 31, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy records that the captured lottiefiles.help page rendered blank, with no visible content or interaction available.

Critical
Status
Server error
VirusTotal
17 / 92
Hosting
United Kingdom188.114.96.3CloudFLARENET-EU · CDN
Registrar
United StatesNameSilo
Registered
Jan 30, 2026
OTX
1 community ref
Page captures
10
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured lottiefiles.help page rendered as a blank white screen with no visible text, logo, form, or control of any kind. Because the capture is empty, there is no main interaction to describe and no way to confirm what the page would have shown had it loaded. The screenshot's blank state conflicts with any assumption that the domain serves a functioning interface.

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

Source evidenceVirusTotal 17 / 92 · OTX 1 references 8 sources

VirusTotal

17 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
44
Malicious
14
Suspicious
3
Undetected
31

Vendor labels

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

Reputation score

0

Categories

Sophos
phishing and fraud
alphaMountain.ai
Phishing (alphaMountain.ai)

Created

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    MX
    Value
    route1.mx.cloudflare.net
    Priority
    88
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.204.73
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.74.166
  • TTL, seconds
    300
    Type
    MX
    Value
    route2.mx.cloudflare.net
    Priority
    78
  • TTL, seconds
    300
    Type
    MX
    Value
    route3.mx.cloudflare.net
    Priority
    41
  • TTL, seconds
    21600
    Type
    NS
    Value
    kenia.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3032::6815:4aa6
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    alberto.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    TXT
    Value
    v=spf1 include:_spf.mx.cloudflare.net ~all
  • TTL, seconds
    21600
    Type
    NS
    Value
    alberto.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3035::ac43:cc49

DNS records observed

JARM fingerprint

00000000000000000042d43d00041da8040ca1d7d1b3e955a3535eb361ef06

Certificate

Subject alternative names
  • lottiefiles.help
  • *.lottiefiles.help
Issuer
Google Trust Services / WE1
Serial
3811884d9c9ed28f0efd02fb12e1f177
SHA-256
0c632de34809c5cc96d6081af94197bb27598a543c7b23698e441d886b39d68a
Subject
lottiefiles.help
Valid until
Valid from

Registry data (RDAP)

Status
  • client transfer prohibited
Registry events
Last changed
Registration
Registrar expiration
Last RDAP database update
Registrar
NameSilo, LLC
Registrar IANA ID
1479
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 44,
    "malicious": 14,
    "suspicious": 3,
    "undetected": 31
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "Sophos": "phishing and fraud",
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Created
2026-01-30T00:00:00Z
Updated
2026-01-30T00:00:00Z
First seen
2026-01-31T04:36:17Z
DNS records
[
    {
        "ttl": 300,
        "type": "MX",
        "value": "route1.mx.cloudflare.net",
        "priority": 88
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.204.73"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.74.166"
    },
    {
        "ttl": 300,
        "type": "MX",
        "value": "route2.mx.cloudflare.net",
        "priority": 78
    },
    {
        "ttl": 300,
        "type": "MX",
        "value": "route3.mx.cloudflare.net",
        "priority": 41
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "kenia.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3032::6815:4aa6"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "alberto.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "TXT",
        "value": "v=spf1 include:_spf.mx.cloudflare.net ~all"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "alberto.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3035::ac43:cc49"
    }
]
Dns at
2026-10-26T07:06:29Z
Jarm
00000000000000000042d43d00041da8040ca1d7d1b3e955a3535eb361ef06
Certificate
{
    "san": [
        "lottiefiles.help",
        "*.lottiefiles.help"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "3811884d9c9ed28f0efd02fb12e1f177",
    "sha256": "0c632de34809c5cc96d6081af94197bb27598a543c7b23698e441d886b39d68a",
    "subject": "lottiefiles.help",
    "valid_to": "2026-12-24T16:49:17Z",
    "valid_from": "2026-09-25T15:50:49Z"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "last changed": "2026-01-31T08:04:27Z",
        "registration": "2026-01-30T00:00:00Z",
        "registrar expiration": "2027-01-30T00:00:00Z",
        "last update of RDAP database": "2026-01-31T17:57:33Z"
    },
    "registrar": "NameSilo, LLC",
    "registrar_iana_id": "1479"
}
Separate source record · 14 malicious + 3 suspicious / 92 · 2026-10-26 07:00:17 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-26T07:00:17Z
fetched_at
2026-10-31T11:10:21Z
stats
{"timeout":0,"harmless":44,"malicious":14,"suspicious":3,"undetected":31}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Report ID

018895d0-769a-439e-8960-58b02bbd01f3

Final URL

https://lottiefiles.help/

HTTP response

200

Navigation history

  • URL
    https://lottiefiles.help/
    Status
    200

DOM structure hash

2bfae74f6225af3cbdc3dad23b0b26b7b1da2ce7e290a3aa343a5812ba7ec96c

Document hash

f7486b7dacf7cca67036df94c8eef8dea58fdb5049a04443ab3a84dd5e4add68

Phishing classifier result

  • phishing

Domain risk categories

  • Malware
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    lottiefiles.help
    Type
    A
    Value
    104.21.74.166
  • Name
    lottiefiles.help
    Type
    A
    Value
    172.67.204.73
  • Name
    lottiefiles.help
    Type
    AAAA
    Value
    2606:4700:3035::ac43:cc49
  • Name
    lottiefiles.help
    Type
    AAAA
    Value
    2606:4700:3032::6815:4aa6

DNSSEC valid

No

IP address

127.0.1.31

127.0.1.31 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Verdict

Tags
  • malware
Malicious
Yes
Categories
  • malware

Registration record

Registrar
NameSilo, LLC
Registered
Updated
Expires
Nameservers
  • kenia.ns.cloudflare.com
  • alberto.ns.cloudflare.com
Original source fields · JSON
Uuid
018895d0-769a-439e-8960-58b02bbd01f3
Final url
https://lottiefiles.help/
Status
200
History
[
    {
        "url": "https://lottiefiles.help/",
        "status": 200
    }
]
DOM structure hash
2bfae74f6225af3cbdc3dad23b0b26b7b1da2ce7e290a3aa343a5812ba7ec96c
Document hash
f7486b7dacf7cca67036df94c8eef8dea58fdb5049a04443ab3a84dd5e4add68
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "lottiefiles.help",
        "type": "A",
        "value": "104.21.74.166"
    },
    {
        "name": "lottiefiles.help",
        "type": "A",
        "value": "172.67.204.73"
    },
    {
        "name": "lottiefiles.help",
        "type": "AAAA",
        "value": "2606:4700:3035::ac43:cc49"
    },
    {
        "name": "lottiefiles.help",
        "type": "AAAA",
        "value": "2606:4700:3032::6815:4aa6"
    }
]
Dnssec valid
false
Ip
127.0.1.31

127.0.1.31 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "NameSilo, LLC",
    "created": "2026-01-30T23:56:24Z",
    "updated": "2026-02-11T11:05:18Z",
    "expires": "2027-01-30T23:59:59Z",
    "nameservers": [
        "kenia.ns.cloudflare.com",
        "alberto.ns.cloudflare.com"
    ]
}

Spamhaus DBL

spam domain

URLScan

Malicious · engine verdict · score 92

SHA-256 58d3da7ce4456e2b9df0244c830b5c99570e2de549b24e6ebed548d49d359661

Open report
URLScanOriginal source recordObserved: 22 fields

Observed: · Retrieved:

Report ID

01a191ad-9441-7338-9598-a1c46f4bb04c

Final URL

https://lottiefiles.help/

HTTP response

403

Redirect type

https-only

Redirects

  • To
    https://lottiefiles.help/
    From
    http://lottiefiles.help/
    Status
    307

IP address

172.67.204.73

Contacted domains

  • static.cloudflareinsights.com

Contacted IP addresses

  • 104.16.79.73
  • 172.67.204.73

Autonomous systems (ASN)

  • 13335

Linked domains

  • www.cloudflare.com

Document hash

58d3da7ce4456e2b9df0244c830b5c99570e2de549b24e6ebed548d49d359661

Script hashes

  • acf5c8737f0a49d83a020b9a1679bf3cbc93ec54159ea1cd7df1be7c1a7d1094

JavaScript globals

  • _cf_translation
  • __cfBeacon

Cookies

  • cf_clearance

TLS session and certificate

Subject alternative names
  • lottiefiles.help
  • *.lottiefiles.help
Cipher
AES_128_GCM
Issuer
WE1
Subject
lottiefiles.help
Protocol
QUIC
Valid until
Valid from

Domain age, days

273

Registered domain age, days

273

Certificate age, days

35

Certificate validity, days

90

Page requests

10

Provider verdicts

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

HTTP headers

Server
cloudflare
Content-type
text/html; charset=UTF-8
X-frame-options
SAMEORIGIN
X-content-type-options
nosniff
Referrer-policy
same-origin
Original source fields · JSON
Uuid
01a191ad-9441-7338-9598-a1c46f4bb04c
Final url
https://lottiefiles.help/
Status
403
Redirected
https-only
Redirects
[
    {
        "to": "https://lottiefiles.help/",
        "from": "http://lottiefiles.help/",
        "status": 307
    }
]
Ip
172.67.204.73
Contacted domains
[
    "static.cloudflareinsights.com"
]
Contacted IP addresses
[
    "104.16.79.73",
    "172.67.204.73"
]
Asns
[
    "13335"
]
Linked domains
[
    "www.cloudflare.com"
]
Document hash
58d3da7ce4456e2b9df0244c830b5c99570e2de549b24e6ebed548d49d359661
Script hashes
[
    "acf5c8737f0a49d83a020b9a1679bf3cbc93ec54159ea1cd7df1be7c1a7d1094"
]
Globals
[
    "_cf_translation",
    "__cfBeacon"
]
Cookies
[
    "cf_clearance"
]
Tls
{
    "san": [
        "lottiefiles.help",
        "*.lottiefiles.help"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "lottiefiles.help",
    "protocol": "QUIC",
    "valid_to": "2026-12-24T16:49:17Z",
    "valid_from": "2026-09-25T15:50:49Z"
}
Domain age days
273
Apex age days
273
Tls age days
35
Tls valid days
90
Requests
10
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 92,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=UTF-8",
    "x-frame-options": "SAMEORIGIN",
    "x-content-type-options": "nosniff",
    "referrer-policy": "same-origin"
}

OTX

1 community reference

Open report

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
lottiefiles.help — Blank Capture of the Domain Page
ai_description
PhishDestroy records that the captured lottiefiles.help page rendered blank, with no visible content or interaction available.
ai_summary
The captured lottiefiles.help page rendered as a blank white screen with no visible text, logo, form, or control of any kind. Because the capture is empty, there is no main interaction to describe and no way to confirm what the page would have shown had it loaded. The screenshot's blank state conflicts with any assumption that the domain serves a functioning interface. The stored VirusTotal domain result reports 17 detections out of 92 engines. CRDF reported "malicious"; DNS8 reported "suspicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-31 12:13:05
revision
24d86e0db52dca97bbee46cf78ce306f7fae8a3fe44f296a06ae3035c7d1878b
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: 16 fields

Mail configuration

MX records
  • route2.mx.cloudflare.net
  • route1.mx.cloudflare.net
  • route3.mx.cloudflare.net
SPF record
v=spf1 include:_spf.mx.cloudflare.net ~all
DANE
Yes
SPF lookups
1

CAA records

Domain
lottiefiles.help

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
2
Archived days
3
Snapshots per day
0.01
Average page size, bytes
1135

Trackers

Requests
5

TLS connection

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

Ports

Open ports
  • 80
  • 443
  • 8080

DNS servers

Nameservers
  • IP address
    108.162.195.18
    Host
    alberto.ns.cloudflare.com
  • IP address
    172.64.34.93
    Host
    kenia.ns.cloudflare.com
DNS zone
lottiefiles.help

Location

IP address
2a06:98c1:3120::3
ASN
13335
Organization
CloudFLARENET-EU
City
London
Country
GB

TLS certificate

Issuer
Google Trust Services / WE1
Subject
lottiefiles.help

DNS records

A
  • 188.114.96.3
  • 188.114.97.3
MX
  • Mail server
    route1.mx.cloudflare.net
    Priority
    88
  • Mail server
    route3.mx.cloudflare.net
    Priority
    41
  • Mail server
    route2.mx.cloudflare.net
    Priority
    78
NS
  • kenia.ns.cloudflare.com
  • alberto.ns.cloudflare.com
SOA
Primary nameserver
alberto.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2416522864
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
TXT
  • v=spf1 include:_spf.mx.cloudflare.net ~all
AAAA
  • 2a06:98c1:3120::3
  • 2a06:98c1:3121::3

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2a06:98c1:3120::3
IP version
6

Registration record

Registrar
NameSilo, LLC
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • kenia.ns.cloudflare.com
  • alberto.ns.cloudflare.com

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html; charset=UTF-8
Content-security-policy
default-src 'none'; script-src 'nonce-ZMu7YuIORAM5FmOrLW4Eqz' '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://challenge
X-frame-options
SAMEORIGIN
X-content-type-options
nosniff
Referrer-policy
same-origin
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=*
Cross-origin-opener-policy
same-origin
Cross-origin-resource-policy
same-origin
Cross-origin-embedder-policy
require-corp
Original source fields · JSON
Mail configuration
{
    "mx": [
        "route2.mx.cloudflare.net",
        "route1.mx.cloudflare.net",
        "route3.mx.cloudflare.net"
    ],
    "spf": "v=spf1 include:_spf.mx.cloudflare.net ~all",
    "dane": true,
    "spf_lookups": 1
}
Caa records
{
    "domain": "lottiefiles.help"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-31T10:56:51Z",
    "first": "2026-01-31T21:33:01Z",
    "changes": 2,
    "days_archived": 3,
    "scans_per_day": 0.01,
    "avg_page_bytes": 1135
}
Trackers
{
    "requests": 5
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "108.162.195.18",
            "host": "alberto.ns.cloudflare.com"
        },
        {
            "ip": "172.64.34.93",
            "host": "kenia.ns.cloudflare.com"
        }
    ],
    "zone": "lottiefiles.help"
}
Location
{
    "ip": "2a06:98c1:3120::3",
    "asn": "13335",
    "org": "CloudFLARENET-EU",
    "city": "London",
    "country": "GB"
}
Ssl
{
    "issuer": "Google Trust Services / WE1",
    "subject": "lottiefiles.help"
}
DNS records
{
    "A": [
        "188.114.96.3",
        "188.114.97.3"
    ],
    "MX": [
        "{\"exchange\": \"route1.mx.cloudflare.net\", \"priority\": 88}",
        "{\"exchange\": \"route3.mx.cloudflare.net\", \"priority\": 41}",
        "{\"exchange\": \"route2.mx.cloudflare.net\", \"priority\": 78}"
    ],
    "NS": [
        "kenia.ns.cloudflare.com",
        "alberto.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"alberto.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2416522864, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "TXT": [
        "v=spf1 include:_spf.mx.cloudflare.net ~all"
    ],
    "AAAA": [
        "2a06:98c1:3120::3",
        "2a06:98c1:3121::3"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2a06:98c1:3120::3",
    "family": 6
}
Registration record
{
    "registrar": "NameSilo, LLC",
    "created": "2026-01-30T23:56:24Z",
    "updated": "2026-02-11T11:05:18Z",
    "expires": "2027-01-30T23:59:59Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "kenia.ns.cloudflare.com",
        "alberto.ns.cloudflare.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html; charset=UTF-8",
        "content-security-policy": "default-src 'none'; script-src 'nonce-ZMu7YuIORAM5FmOrLW4Eqz' '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://challenge",
        "x-frame-options": "SAMEORIGIN",
        "x-content-type-options": "nosniff",
        "referrer-policy": "same-origin",
        "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=*",
        "cross-origin-opener-policy": "same-origin",
        "cross-origin-resource-policy": "same-origin",
        "cross-origin-embedder-policy": "require-corp"
    }
}
Network Security Intelligence Registrar context
Registrar context NameSilo
Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
Review source investigation
CF Cloudflare Radar Verdict Malicious
Malware Security threats Malware
View full Cloudflare Radar report

Questions about lottiefiles.help

Is lottiefiles.help legit?

PhishDestroy records that the captured lottiefiles.help page rendered blank, with no visible content or interaction available.

Is lottiefiles.help safe to connect a wallet?

This report does not record which wallet requests lottiefiles.help 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 lottiefiles.help?

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 · 10 captures

Cloudflare Radar 1 / 10 Used in the analysis Source file SHA-256: e474a175f992442a69e502e42d7748076f7b37bd4715cf7c03ed2b7ff55231c3 SHA-256 of the prepared copy given to the model: cbd7964afd4f4fe91d257f62cb637efc6d375d5ecf52307768f6bc30d044a66e
SourceCloudflare Radar
Recorded
StateStored capture
HTTP status200
Final URLhttps://lottiefiles.help/
Position1 / 10
Open capture Source Report Wayback Download
All capture links and hashes (10)
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 53 days

Domain details

Domain
IP Context United Kingdom188.114.96.3 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar NameSilo US(US) PhishDestroy Investigation
Abuse contactabuse@namesilo.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for lottiefiles.help →
RegistrationCreated Jan 30, 2026 (273d) — Expires Jan 30, 2027
Registrant countryUnited States VirusTotal WHOIS
Registrant9837b53fdafbca6d0166f69248f6f568s@privacyguardian.org VirusTotal WHOIS
WHOIS statusclientTransferProhibited
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://lottiefiles.help/
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
United Kingdom188.114.96.3
Network ASN
AS13335
Organization
CloudFLARENET-EU
Observed location
United KingdomLondon, GB
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • alberto.ns.cloudflare.com
  • kenia.ns.cloudflare.com

SOA

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

Mail routing 3 MX records

  • route1.mx.cloudflare.netpriority 88
  • route2.mx.cloudflare.netpriority 78
  • route3.mx.cloudflare.netpriority 41

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-09-25 15:50:49
Valid until
2026-12-24 16:49:17
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint0c632de34809c5cc96d6081af94197bb27598a543c7b23698e441d886b39d68a
Certificate names · 2 SANs
  • lottiefiles.help
  • *.lottiefiles.help

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

viewdns.info · 188.114.96.3rapiddns.io
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

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

Archived Evidence

Wayback Machine Snapshot
View Archive
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://lottiefiles.help/
Final URL: https://lottiefiles.help/
Response
HTTP 200
HTML body
1.8 KB
Compressed
1.0 KB
Links
1 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html
Server: cloudflare
CF-Cache-Status: DYNAMIC
Security headers present
X-Frame-OptionsX-Content-Type-OptionsX-XSS-ProtectionReferrer-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 17
alt-svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a5320ca40922aadc-YYZ
Connection
keep-alive
Content-Type
text/html
Date
Sat, 31 Oct 2026 10:41:48 GMT
expect-ct
max-age=86400, enforce
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Referrer-Policy
same-origin
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=GL1FBOhRw7Wu8jQ%2FkN6ugvt%2BWUReyBPe0esHcxs2lxGRweJJ5Ct%2FTAkLN%2BuQeulNW1fsVwgkt6tTvEY4aVWOBgkE9CikxYK8YOBYZ8heNo8HxdiaWJ01OXXRCcS85In2Yig2"}]
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Speculation-Rules
"/cdn-cgi/speculation"
Transfer-Encoding
chunked
X-Content-Type-Options
nosniff
X-Frame-Options
SAMEORIGIN
X-XSS-Protection
1; mode=block

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: 10 SHA-256 hashes: 10 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 11:21 UTC.

Open this scan on URLScan 01a191ad-9441-7338-9598-a1c46f4bb04c ↗

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
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:18:41.000000
    Evidence SHA-256
    0ed4dc0ee4d100430579983eaf3d18c59ef608509809caef3e7d2e0bc556ac83
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 12:18:41
    Evidence reason
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:18:41.000000
    Evidence SHA-256
    0ed4dc0ee4d100430579983eaf3d18c59ef608509809caef3e7d2e0bc556ac83
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 12:18:41
    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 12:14:50.766235
    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 · recorded

Recorded events: 13. 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
    lottiefiles.help detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · OTX Community References · Registrar Context: NameSilo · Cloudflare Radar: Malicious · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 11 of 11
  • Spamhaus DBL
    Spamhaus DBL recorded: spam domain
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 92
  • 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.
  • Registrar Context: NameSilo
    Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as malware, Security threats
  • 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 Recorded: 1 of 1

Recorded activity

6 entries
  1. URLScan

    Page captured

    View source
  2. AlienVault OTX

    1 community references

    View source
  3. Cloudflare Radar

    Phishing

    View source
  4. Wayback Machine

    Page archived

    View source
  5. Added to PhishDestroy

    lottiefiles.help

    View source
  6. 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

Check for cloaking

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

lottiefiles.help

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 17 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Malicious 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 Server error
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 lottiefiles.help)
  • 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/lottiefiles.help"
  title="PhishDestroy threat report for lottiefiles.help"
  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>