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

folio-ai.org

In short

folio-ai.org is a phishing page detected by PhishDestroy on 2026-10-25.

“FOLIO — AI Platform for Smarter Idle Cash”

Review the evidence
Registrar
United StatesDynadot
Resolved IP
Netherlands158.94.210.119Omegatech LTD
Registered
Oct 21, 2026
First observed
Oct 26, 2026
PhishDestroy assessment Critical
100/100
Evidence score
First observed Oct 25, 2026 23:33 UTC · PhishDestroy
Risk signals
VirusTotal detections: 15/92 Spamhaus DBL: spam domain Young domain: 6 days old
VirusTotal
15 / 92
engine detections ·
OTX
5
community references
URLScan
Malicious
engine verdict · score 99
Page captures
8
open gallery
Domain age
6 days
Reports sent
1
view timeline
OTX: 5 refs Oct 26, 2026 1 Report Sent
X Telegram API
ABUSE NOTICE · 24H+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@dynadot.com. The latest stored availability evidence still shows the domain reachable; 2 days has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
2 days
Reports sent
1
Latest case ID
PD-20261025-165DD4
Current status
Observed active at latest stored check

Analysis

Domain summary

folio-ai.org is a phishing page detected by PhishDestroy on 2026-10-25. Risk: critical (100/100). Registrar: Dynadot. Hosting: Omegatech LTD. PhishDestroy sent 1 abuse report. VirusTotal: 15/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

Critical
VirusTotal
15 / 92
Hosting
Netherlands158.94.210.119Omegatech LTD
Registrar
United StatesDynadot
Registered
Oct 21, 2026
OTX
5 community refs
Page captures
8
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy added folio-ai.org to its internal blocklist on 2026-10-26 following a trusted auto‑rule assessment. The recorded page title reads “FOLIO — AI Platform for Smarter Idle Cash” and an HTTP 200 response was observed on the same date.

How the scam works

The detections indicate the site could be used for phishing or fraudulent financial services, a pattern where attackers present a legitimate‑sounding platform to lure users into revealing credentials or funds. No specific malicious behavior was observed on the page, so the exact mechanism remains unconfirmed.

Evidence

VirusTotal reported 15 detections from 92 engines on 2026-10-27, labeling the domain as phishing, spam or malicious. Google Safe Browsing checked the URL on 2026-10-27 and did not flag it. URLScan recorded a malicious engine score of 99 on 2026-10-26, though its overall verdict was non‑malicious. Cloudflare Radar marked the domain as malicious malware on 2026-10-26. Spamhaus DBL listed the domain as spam on 2026-10-26. OTX recorded five pulses referencing the domain on 2026-10-27. PhishDestroy’s internal blocklist flagged the domain as true on 2026-10-27.

Infrastructure

The domain was registered on 2026-10-21 through Dynadot Inc. The recorded IP was 158.94.210.119, listed under OMEGATECH‑AS Omegatech LTD in the Netherlands. TLS was provided by Let’s Encrypt, valid from 2026-10-24 to 2027-01-22, and the site used Cloudflare name servers millie.ns.cloudflare.com and will.ns.cloudflare.com. Open ports observed during scanning included 22, 80 and 443.

What to do

Visitors should avoid entering any personal or financial information on folio-ai.org and, if they have already done so, change affected passwords and monitor accounts for unauthorized activity. Defenders should block the exact domain, review logs for connections to the recorded IP, and apply standard web‑filtering policies to prevent future access.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportURLQuery reportStored capture screenshotCloudflare Radar screenshot (2026-10-26T00:05:46Z)URLQuery screenshotURLScan screenshot (2026-10-22T03:30:27Z)URLScan capture reportURLScan screenshot (2026-10-22T10:20:31Z)URLScan capture reportURLScan screenshot (2026-10-23T10:14:46Z)URLScan capture reportURLScan screenshot (2026-10-25T23:36:14Z)URLScan capture reportVirusTotal reportGoogle Safe Browsing statusArchived copyReport phishing to GoogleSite owner? Request a review
Source evidenceVirusTotal 15 / 92 · OTX 5 references 9 sources

VirusTotal

15 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
46
Malicious
12
Suspicious
3
Undetected
31

Vendor labels

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

Reputation score

0

Categories

Sophos
phishing and fraud
alphaMountain.ai
Phishing, Newly Registered (alphaMountain.ai)
Forcepoint ThreatSeeker
phishing and other frauds

Registrar

Dynadot Inc

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    NS
    Value
    ns1.dyna-ns.net
  • TTL, seconds
    300
    Type
    A
    Value
    158.94.210.119
  • TTL, seconds
    300
    Type
    NS
    Value
    ns2.dyna-ns.net
  • TTL, seconds
    300
    Type
    SOA
    Responsible mailbox
    hostmaster.folio-ai.org
    Value
    ns1.dyna-ns.net

DNS records observed

JARM fingerprint

40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319

Certificate

Subject alternative names
  • *.folio-ai.org
  • folio-ai.org
Issuer
Let's Encrypt / YE1
Serial
550bfb61f75f9293ef3d7fe06e4afe75a07
SHA-256
3d02fbd7addc4f9901f20a386551c4b4312aa6bfbfd2246bbbcd05be80f7a40b
Subject
folio-ai.org
Valid until
Valid from

Registration record

Registrar
Dynadot Inc
Registrar IANA ID
472
Registrar URL
http://www.dynadot.com
Registered
Updated
Expires
Status
  • addPeriod
  • clientTransferProhibited
Nameservers
  • millie.ns.cloudflare.com
  • will.ns.cloudflare.com
DNSSEC
unsigned

Registry data (RDAP)

Status
  • transfer prohibited
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 46,
    "malicious": 12,
    "suspicious": 3,
    "undetected": 31
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "phishing",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Fortinet": "spam",
    "SOCRadar": "phishing",
    "URLQuery": "malicious",
    "Kaspersky": "phishing",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "Sophos": "phishing and fraud",
    "alphaMountain.ai": "Phishing, Newly Registered (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "phishing and other frauds"
}
Registrar
Dynadot Inc
Created
2026-10-21T07:06:30Z
Expires
2027-10-21T07:06:30Z
Updated
2026-10-21T07:06:48Z
First seen
2026-10-21T13:18:15Z
DNS records
[
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns1.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "158.94.210.119"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns2.dyna-ns.net"
    },
    {
        "ttl": 300,
        "type": "SOA",
        "rname": "hostmaster.folio-ai.org",
        "value": "ns1.dyna-ns.net"
    }
]
Dns at
2026-10-26T07:17:27Z
Jarm
40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319
Certificate
{
    "san": [
        "*.folio-ai.org",
        "folio-ai.org"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "550bfb61f75f9293ef3d7fe06e4afe75a07",
    "sha256": "3d02fbd7addc4f9901f20a386551c4b4312aa6bfbfd2246bbbcd05be80f7a40b",
    "subject": "folio-ai.org",
    "valid_to": "2027-01-22T08:41:14Z",
    "valid_from": "2026-10-24T08:41:15Z"
}
Registration record
{
    "registrar": "Dynadot Inc",
    "registrar_iana_id": "472",
    "registrar_url": "http://www.dynadot.com",
    "created": "2026-10-21T07:06:30Z",
    "updated": "2026-10-21T07:06:48Z",
    "expires": "2027-10-21T07:06:30Z",
    "status": [
        "addPeriod",
        "clientTransferProhibited"
    ],
    "nameservers": [
        "millie.ns.cloudflare.com",
        "will.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "transfer prohibited"
    ],
    "events": {
        "expiration": "2027-10-21T07:06:30Z",
        "last changed": "2026-10-21T07:06:49Z",
        "registration": "2026-10-21T07:06:30Z",
        "registrar expiration": "2027-10-21T07:06:30Z",
        "last update of RDAP database": "2026-10-21T10:14:12Z"
    }
}
Separate source record · 12 malicious + 3 suspicious / 92 · 2026-10-26 07:17:04 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:17:04Z
fetched_at
2026-10-27T01:29:10Z
stats
{"timeout":0,"harmless":46,"malicious":12,"suspicious":3,"undetected":31}

Cloudflare Radar

Malicious

Open report
Cloudflare RadarOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Report ID

37328a62-948c-471d-a045-5b38b6239d3e

Final URL

https://folio-ai.org/

HTTP response

200

Navigation history

  • URL
    https://folio-ai.org/
    Status
    200

DOM structure hash

8e41957d69606952a13551fcba34da4458d42ff2b6fefbe08fbf162700fde504

Document hash

1fa09775f782e1906551d35533ab8a1710504dcbe5c313c5b0a976e6061fbe7a

Domain risk categories

  • Malware
  • Security threats
  • Newly Seen Domains
  • Security Risks
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    folio-ai.org
    Type
    A
    Value
    158.94.210.119

DNSSEC valid

No

IP address

158.94.210.119

Verdict

Tags
  • malware
Malicious
Yes
Categories
  • malware

Registration record

Registrar
Dynadot Inc
Registered
Updated
Expires
Nameservers
  • millie.ns.cloudflare.com
  • will.ns.cloudflare.com
Original source fields · JSON
Uuid
37328a62-948c-471d-a045-5b38b6239d3e
Final url
https://folio-ai.org/
Status
200
History
[
    {
        "url": "https://folio-ai.org/",
        "status": 200
    }
]
DOM structure hash
8e41957d69606952a13551fcba34da4458d42ff2b6fefbe08fbf162700fde504
Document hash
1fa09775f782e1906551d35533ab8a1710504dcbe5c313c5b0a976e6061fbe7a
Domain risks
[
    "Malware",
    "Security threats",
    "Newly Seen Domains",
    "Security Risks",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "folio-ai.org",
        "type": "A",
        "value": "158.94.210.119"
    }
]
Dnssec valid
false
Ip
158.94.210.119
Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-10-21T07:06:30Z",
    "updated": "2026-10-21T07:06:48Z",
    "expires": "2027-10-21T07:06:30Z",
    "nameservers": [
        "millie.ns.cloudflare.com",
        "will.ns.cloudflare.com"
    ]
}

Spamhaus DBL

spam domain

URLScan

Malicious · engine verdict · score 99

SHA-256 fd50fca9f2e4ecdb431cf2bf9e2c5369fed5fa2aafc99ca3ade524095092cfc8

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a17567-dac3-7479-b032-e2a607b7d7ed

Final URL

https://folio-ai.org/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://folio-ai.org/
    From
    http://folio-ai.org/
    Status
    307

IP address

158.94.210.119

Contacted IP addresses

  • 158.94.210.119

Autonomous systems (ASN)

  • 202412

Server countries

  • NL

Document hash

e1fb8ba11b688d751da8ce8b93f195b3f18ee0fe342adbb46bf1042a459e2fbb

Script hashes

  • 8aa5f8f647356dcd4fc5dbbe0efd5bc0e8da74026bc61e24636e2e1f5749b0ce

JavaScript globals

  • __dclq
  • __dclOrig
  • __dclFlush
  • __smsCheckBeforeSubmit
  • __isSmsEnabled
  • __isSmsVerified
  • intlTelInput

Cookies

  • connect.sid

TLS session and certificate

Subject alternative names
  • *.folio-ai.org
  • folio-ai.org
Cipher
AES_128_GCM
Issuer
YE1
Subject
folio-ai.org
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

4

Registered domain age, days

4

Certificate age, days

1

Certificate validity, days

89

Page requests

7

Provider verdicts

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

HTTP headers

Content-type
text/html; charset=utf-8
X-content-type-options
nosniff
Referrer-policy
same-origin
Original source fields · JSON
Uuid
01a17567-dac3-7479-b032-e2a607b7d7ed
Final url
https://folio-ai.org/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://folio-ai.org/",
        "from": "http://folio-ai.org/",
        "status": 307
    }
]
Ip
158.94.210.119
Contacted IP addresses
[
    "158.94.210.119"
]
Asns
[
    "202412"
]
Countries
[
    "NL"
]
Document hash
e1fb8ba11b688d751da8ce8b93f195b3f18ee0fe342adbb46bf1042a459e2fbb
Script hashes
[
    "8aa5f8f647356dcd4fc5dbbe0efd5bc0e8da74026bc61e24636e2e1f5749b0ce"
]
Globals
[
    "__dclq",
    "__dclOrig",
    "__dclFlush",
    "__smsCheckBeforeSubmit",
    "__isSmsEnabled",
    "__isSmsVerified",
    "intlTelInput"
]
Cookies
[
    "connect.sid"
]
Tls
{
    "san": [
        "*.folio-ai.org",
        "folio-ai.org"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "folio-ai.org",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-22T08:41:14Z",
    "valid_from": "2026-10-24T08:41:15Z"
}
Domain age days
4
Apex age days
4
Tls age days
1
Tls valid days
89
Requests
7
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "text/html; charset=utf-8",
    "x-content-type-options": "nosniff",
    "referrer-policy": "same-origin"
}
Separate monitor record · 2026-10-26 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a17567-dac3-7479-b032-e2a607b7d7ed
score
0
malicious
false
result_at
2026-10-26T04:30:15Z
enriched_at
2026-10-26T09:12:37Z
source_timestamps
{"urlscan_result_at":"2026-10-26 05:30:15","urlscan_enriched_at":"2026-10-26 10:12:37"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

5 community references

Open report

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

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

Open report
Separate monitor score · 10 / 100 · 2026-10-26T03:20:13Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
10
analyzed_at
2026-10-26T03:20:13Z
source_timestamp
2026-10-26 04:20:13
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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
folio-ai.org — Suspicious Domain
ai_description
PhishDestroy flags folio-ai.org as suspicious after security detections, though the page title is benign and a HTTP 200 response was recorded on 2026-10-26.
ai_generated_at
2026-10-27T01:31:05Z
ai_generated_by
threat-v3-groq
interpretation
Narrative generation metadata, separate from provider 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: 26 fields

Mail configuration

SPF lookups
0

CAA records

Domain
folio-ai.org

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
21468

Crawler rules

User agents
  • *
Present
Yes
Sitemap URLs
  • https://folio-ai.org/sitemap.xml

Sitemap

Present
Yes
URL count
5

Page title and metadata

Page title
FOLIO — AI Platform for Smarter Idle Cash
Indexing directives
index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1
Description
Discover with FOLIO a predictive AI platform that turns idle liquidity into allocated capital — with no lock-up periods and instant withdrawals. Put your cash position to work with better information.
Canonical URL
https://folio-ai.org/

Trackers

Requests
38
Observed services
  • Name
    Cloudflare
    Company
    Cloudflare
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    jsDelivr
    Company
    jsDelivr
    Category
    Hosting
    Requests
    4

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
561
TLS
81
Waiting
126
Connection
67
Download
129
Response time, ms
964

TLS connection

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

Ports

Open ports
  • 22
  • 80
  • 443

Carbon estimate

Bytes
73726
CO₂, grams
0.0027
Cleaner than, %
29

DNS servers

Nameservers
  • IP address
    162.159.24.5
    Host
    ns2.dyna-ns.net
  • IP address
    162.159.27.158
    Host
    ns1.dyna-ns.net
DNS zone
folio-ai.org

Cookies

Cookies
  • Name
    cf-c
    HTTP-only
    Yes
    SameSite
    Lax
  • Name
    __cf_clicked
  • Name
    ph_phc_t6w4wzJE2sbz4ro8LmZZTssm5go3KD6mP7QsqcDQRSp6_posthog
    Secure
    Yes
    SameSite
    Lax

Location

IP address
158.94.210.119
ASN
202412
Organization
Omegatech LTD
City
Amsterdam
Country
NL

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
folio-ai.org

DNS records

A
  • 158.94.210.119
NS
  • ns2.dyna-ns.net
  • ns1.dyna-ns.net
SOA
Primary nameserver
ns1.dyna-ns.net
Hostmaster
hostmaster.folio-ai.org
Serial
2026102403
Refresh, seconds
16384
Retry, seconds
2048
Expiry, seconds
1209600
Minimum TTL, seconds
300

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
same-origin
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
nosniff
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
158.94.210.119
IP version
4

Redirects

Redirect chain
  • https://folio-ai.org

Page links

Internal links
9

Registration record

Registrar
Dynadot Inc
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
  • addPeriod https://icann.org/epp
Nameservers
  • ns1.dyna-ns.net
  • ns2.dyna-ns.net

HTTP headers

Response headers
Content-type
text/html; charset=utf-8
X-content-type-options
nosniff
Referrer-policy
same-origin
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "folio-ai.org"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-25T23:34:12Z",
    "first": "2026-10-25T23:34:12Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 21468
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true,
    "sitemaps": [
        "https://folio-ai.org/sitemap.xml"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 5
}
Page title and metadata
{
    "title": "FOLIO — AI Platform for Smarter Idle Cash",
    "robots": "index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1",
    "description": "Discover with FOLIO a predictive AI platform that turns idle liquidity into allocated capital — with no lock-up periods and instant withdrawals. Put your cash position to work with better information.",
    "canonicalUrl": "https://folio-ai.org/"
}
Trackers
{
    "requests": 38,
    "trackers": [
        {
            "name": "Cloudflare",
            "company": "Cloudflare",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "jsDelivr",
            "company": "jsDelivr",
            "category": "Hosting",
            "requests": 4
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 561,
        "tls": 81,
        "wait": 126,
        "connect": 67,
        "download": 129
    },
    "response_ms": 964
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_128_GCM_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        22,
        80,
        443
    ]
}
Carbon
{
    "bytes": 73726,
    "co2_grams": 0.0027,
    "cleaner_than": 29
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.24.5",
            "host": "ns2.dyna-ns.net"
        },
        {
            "ip": "162.159.27.158",
            "host": "ns1.dyna-ns.net"
        }
    ],
    "zone": "folio-ai.org"
}
Cookies
{
    "cookies": [
        {
            "name": "cf-c",
            "http_only": true,
            "same_site": "Lax"
        },
        {
            "name": "__cf_clicked"
        },
        {
            "name": "ph_phc_t6w4wzJE2sbz4ro8LmZZTssm5go3KD6mP7QsqcDQRSp6_posthog",
            "secure": true,
            "same_site": "Lax"
        }
    ]
}
Location
{
    "ip": "158.94.210.119",
    "asn": "202412",
    "org": "Omegatech LTD",
    "city": "Amsterdam",
    "country": "NL"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "folio-ai.org"
}
DNS records
{
    "A": [
        "158.94.210.119"
    ],
    "NS": [
        "ns2.dyna-ns.net",
        "ns1.dyna-ns.net"
    ],
    "SOA": "{\"nsname\": \"ns1.dyna-ns.net\", \"hostmaster\": \"hostmaster.folio-ai.org\", \"serial\": 2026102403, \"refresh\": 16384, \"retry\": 2048, \"expire\": 1209600, \"minttl\": 300}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": "same-origin",
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": "nosniff",
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "158.94.210.119",
    "family": 4
}
Redirects
{
    "chain": [
        "https://folio-ai.org"
    ]
}
Page links
{
    "internal_count": 9
}
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-10-21T07:06:30Z",
    "updated": "2026-10-24T09:16:29Z",
    "expires": "2027-10-21T07:06:30Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp",
        "addPeriod https://icann.org/epp"
    ],
    "nameservers": [
        "ns1.dyna-ns.net",
        "ns2.dyna-ns.net"
    ]
}
HTTP headers
{
    "headers": {
        "content-type": "text/html; charset=utf-8",
        "x-content-type-options": "nosniff",
        "referrer-policy": "same-origin"
    }
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Security Risks Security threats Malware Malware
View full Cloudflare Radar report

Questions about folio-ai.org

Is folio-ai.org legit?

No. PhishDestroy classifies folio-ai.org as a phishing page (risk: critical, 100/100); it was first detected on 2026-10-25. VirusTotal: 15/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is folio-ai.org safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on folio-ai.org. 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 folio-ai.org?

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 matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 8 captures

Primary capture 1 / 8
SourcePrimary capture
Recorded
StateStored capture
Position1 / 8
Open capture Wayback Download
All capture links and hashes (8)
folio-ai.org: caution — Flagged by Spamhaus DBL, 15/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card folio-ai.org: caution — Flagged by Spamhaus DBL, 15/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v 1eb939ae3d40

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 99 report ↗
IP Reputation Netherlands158.94.210.119 abuse score 10/100 18 reports PhishingOpen ProxyBad Web Bot checked Oct 26, 2026 last reported
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Dynadot US(US)
Abuse contactabuse@dynadot.com, abuse@omegatech.sc
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for folio-ai.org →
Hosting abuse contact abuse@omegatech.sc Omegatech LTD · AS202412
RegistrationCreated Oct 21, 2026 (6d · Brand New!) — Expires Oct 21, 2027
WHOIS statusclientTransferProhibitedaddPeriod
Technical detailsProvenance & timestamps
First DetectedOct 26, 2026
DOM Analysisanalyzed Oct 26, 2026score 100/1002 brand signals
Submitted URLhttp://folio-ai.org/
Favicon Hash
Case ID
Observed page title
FOLIO — AI Platform for Smarter Idle Cash
Automated brand references
Across Near
TLS Certificate
Issued by YE1 · stored validity ends in 86 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Netherlands158.94.210.119
Network ASN
AS202412
AS name
OMEGATECH-AS Omegatech LTD, SC
Organization
Omegatech LTD
Observed location
NetherlandsAmsterdam, NL

Nameservers 2

  • ns1.dyna-ns.net
  • ns2.dyna-ns.net

SOA

  • nsname: ns1.dyna-ns.net
  • hostmaster: hostmaster.folio-ai.org
  • serial: 2026102403
  • refresh: 16384
  • retry: 2048
  • expire: 1209600
  • minttl: 300

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
YE1
Valid from
2026-10-24 08:41:15
Valid until
2027-01-22 08:41:14
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint3d02fbd7addc4f9901f20a386551c4b4312aa6bfbfd2246bbbcd05be80f7a40b
Certificate names · 2 SANs
  • *.folio-ai.org
  • folio-ai.org

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

viewdns.info · 158.94.210.119rapiddns.io
Threat Intel Cross-Reference · source references
ScamAdviser Public lookup
A public ScamAdviser lookup is available. Review its current score and warnings at the source; the existence of a lookup page is not itself a malicious verdict.
View on ScamAdviser
Fetched directly from the site by PhishDestroy · cached up to 24 h
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

15 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 15 detections
alphaMountain.ai
BitDefender
CRDF
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
SOCRadar
Sophos
URLQuery
VIPRE

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of folio-ai.org · checked Oct 26, 2026

99
Good
Performance
FCP
0.93 s
First Contentful Paint
LCP
1.65 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
2.9 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 200
Requested URL: http://folio-ai.org/
Final URL: https://folio-ai.org/
Response
HTTP 200
HTML body
809 B
Compressed
415 B
Links
0 internal · 0 external
Selected response headers
Cache-Control: no-cache, no-store, must-revalidate
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
X-Powered-By: Express
Security headers present
X-Content-Type-OptionsReferrer-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 11
Alt-Svc
h3=":443"; ma=2592000
Cache-Control
no-cache, no-store, must-revalidate
Content-Encoding
gzip
Content-Length
424
Content-Type
text/html; charset=utf-8
Date
Sun, 25 Oct 2026 23:34:17 GMT
Referrer-Policy
same-origin
Vary
Accept-Encoding
Via
1.1 Caddy
X-Content-Type-Options
nosniff
X-Powered-By
Express

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.

Stored observation history3

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

  1. Availability monitor · Recorded state

    live_content

    content_served

  2. VirusTotal · Detection count

    1→15

    Engines added
    BitDefender · CRDF · DNS8 · ESET · Forcepoint ThreatSeeker · Fortinet · G-Data · Gridinsoft · Kaspersky · Lionic · Sophos · URLQuery · VIPRE · alphaMountain.ai
    Engines removed
    None recorded
    Recorded vendor total
    15
  3. Domain monitor · First collection record

    Reachable

All retained availability observations8

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_http_probeunknown
    Observation source
    current_http_probe
    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-27 12:38:27.000000
    Evidence SHA-256
    005d12dbcdb1e0da591236dade6035ac69789b2e4b86ba32a8757044a04ef094
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-27 12:38:27
    Evidence reason
    timeout
  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-27 12:38:27.000000
    Evidence SHA-256
    005d12dbcdb1e0da591236dade6035ac69789b2e4b86ba32a8757044a04ef094
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-27 12:38:27
    Evidence reason
    timeout
  3. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 04:32:04.000000
    Evidence SHA-256
    721b3efdc43209750cccb7e00c8f94fd22be02c35a74cb6acf9ba24831866456
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 04:32:04
    Evidence reason
    alive_content
  4. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 04:32:04.000000
    Evidence SHA-256
    721b3efdc43209750cccb7e00c8f94fd22be02c35a74cb6acf9ba24831866456
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 04:32:04
    Evidence reason
    alive_content
  5. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 12:32:14.000000
    Evidence SHA-256
    4d81d511f813295827c55a1dc4854db7f2019eb0a38916a177314637c51605f4
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 12:32:14
    Evidence reason
    alive_content
  6. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 12:32:14.000000
    Evidence SHA-256
    4d81d511f813295827c55a1dc4854db7f2019eb0a38916a177314637c51605f4
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 12:32:14
    Evidence reason
    alive_content
  7. 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-26 00:33:12.000000
    Evidence SHA-256
    c4f9f1f8023aa95c3fe941bd7c37fad8d1284d995d557fbdbff4f4f2e17839bc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 00:33:12
    Evidence reason
  8. 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-26 00:33:12.000000
    Evidence SHA-256
    c4f9f1f8023aa95c3fe941bd7c37fad8d1284d995d557fbdbff4f4f2e17839bc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 00:33:12
    Evidence reason

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Notifications · recorded
  4. Monitoring · recorded

Recorded events: 14. 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
    folio-ai.org detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · OTX Community References · Cloudflare Radar: Malicious · Forensic Evidence Collected · Technical Analysis Recorded · VirusTotal detections +14 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: 99
  • 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: 15/92
  • OTX Community References
    Community publication references on AlienVault OTX: 5. References are not vendor verdicts and are excluded from the evidence score.
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as Security Risks, Security threats, malware
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, URLQuery, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
  • VirusTotal detections +14
    New detections: +14 (1 → 15): BitDefender, CRDF, DNS8, ESET +10
Notification RecordsSent Report Recorded Recorded: 1 of 1
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: Dynadot Inc. Abuse contacts: 1.
    • abuse@dynadot.com
Publication & AvailabilityDestroyList Published Recorded: 1 of 1

Recorded activity

6 entries
  1. AlienVault OTX

    5 community references

    View source
  2. VirusTotal

    15/92 engine detections

    View source
  3. Abuse report sent

    PD-20261025-165DD4 · Receipt 83289

    abuse@dynadot.com
  4. Wayback Machine

    Page archived

    View source
  5. Added to PhishDestroy

    folio-ai.org

    View source
  6. URLScan

    Page captured

    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.

folio-ai.org

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 15 det. ChainPatrol URLQuery Report stored SSL Labs Stored certificate dates valid CF Radar Malicious OTX 5 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261025-165DD4 Recipient: abuse@dynadot.com
PDF notice generated Notice text archived (291 characters)
Abuse notice text as sent to the provider 
Registrar: Dynadot LLC / Dynadot Inc (United States)
Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains
Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
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?

6 evidence signal groups linked 1 stored notification records Unverified
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.

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

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

Even if funds were frozen, they cannot be recovered without an official police report or court order. Submitting a complaint is the only path to potential recovery.

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.

  • 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 folio-ai.org)
  • 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/folio-ai.org"
  title="PhishDestroy threat report for folio-ai.org"
  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>