Skip to security report
yokofinance.com — PhishDestroy
VirusTotal: result unavailable for this observation. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
yokofinance.com favicon

yokofinance.com

In short

PhishDestroy stores a record for yokofinance.com. Source observations are dated separately; missing checks do not establish safety.

“Bot Verification”

Registrar
United StatesDynadot
Resolved IP
United States198.251.81.49FranTech Solutions
Registered
Oct 31, 2026
First observed
Nov 5, 2026
PhishDestroy assessment Medium
25/100
Evidence score
First observed Nov 5, 2026 03:23 UTC · PhishDestroy
Stored PhishDestroy threat listing Young domain: 5 days old
URLScan
engine verdict · score 99
Page captures
open gallery
Domain age
registered 2026-10-31 according to WHOIS
Reports sent
view timeline
Nov 5, 2026 1 Report Sent
X Telegram API

Analysis

Medium
Hosting
United States198.251.81.49FranTech Solutions
Registrar
United StatesDynadot
Registered
Oct 31, 2026
Page captures
1

Recorded source summary

PhishDestroy stores a record for yokofinance.com. Source observations are dated separately; missing checks do not establish safety.

A reviewed analysis is not available for this text revision. Consult the dated source records below.

Source evidence 4 sources

URLScan

Malicious · engine verdict · score 99

SHA-256 d550d7f5ad7ab2c7df66e9f4893206760ef9ef35cd67ffe83d3bafa7766c16e7

Open report
URLScanOriginal source recordObserved: 26 fields

Observed: · Retrieved:

Report ID

01a1a9b9-f6ff-74cb-9f8b-81da3ca134a5

Final URL

https://yokofinance.com/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://yokofinance.com/
    From
    http://yokofinance.com/
    Status
    307

IP address

198.251.81.49

Reverse DNS (PTR)

d2mail49.my-control-panel.com

Contacted domains

  • widget-v3.smartsuppcdn.com
  • embed.tawk.to
  • ka-f.fontawesome.com
  • va.tawk.to
  • static.getbutton.io
  • cdnjs.cloudflare.com
  • websocket-visitors.smartsupp.com
  • bootstrap.smartsuppchat.com
  • www.smartsuppchat.com
  • cdn.gtranslate.net
  • kit.fontawesome.com
  • use.fontawesome.com
  • iqfinanceoption.ltd

Contacted IP addresses

  • 195.181.170.19
  • 2a02:6ea0:c700::101
  • 18.185.13.80
  • 2606:4700:20::681a:fdd
  • 2a02:6ea0:c77a::47
  • 172.66.161.212
  • 172.67.139.119
  • 2606:4700:20::ac43:44cc
  • 104.17.24.14
  • 2606:4700:4404::6812:2844
  • 2606:4700:3033::ac43:8ef5
  • 198.251.81.49

Autonomous systems (ASN)

  • 60068
  • 16509
  • 13335
  • 53667

Server countries

  • DE
  • US

Linked domains

  • www.youtube.com
  • t.me
  • www.e-services.cr.gov.hk
  • getbutton.io

Social media links

  • https://www.youtube.com
  • https://t.me

Document hash

d550d7f5ad7ab2c7df66e9f4893206760ef9ef35cd67ffe83d3bafa7766c16e7

Script hashes

  • 01553ed625606e998897ded26835c783d7b506705316d85f58f9d70d58c1a143
  • a944a4f6523730a2b8fc2f2b9cb721a3e213f072ded914b6e1d119fbf6dc9b19
  • 14299655cd4cc668ea9c08dcfc8a85561004e4fe8d4f9934e1cd827f0250aa38
  • 335996388701cdad34eafee059fa9ee1cfb7dd3bc424df039d5ed61868d76d20
  • 679a9d345a9c8fe68d19d5d77aa39009a4d6e5263e0efa4ada370200d4e61101
  • 493c46ee8249d8f7298654566b61ab4cabfaec7e38435e145f6cdbe8d818d041
  • 829eeb290ba5f75eced40d1e3dc778a02f86fa201606f1d116e80e2fd8ef3c0d
  • b4d88c72b6fd217f52352b579c2fcc158e65f1a11d3853309b668468b1c1d221
  • f95839d3309b9d77efc97a35eee16da10658f0f3253e841507085fce3871b446
  • f52635cb7d42762134881672b20409732c1b4e3e82bce3ad1640ee155fe78807

JavaScript globals

  • FontAwesomeKitConfig
  • $
  • jQuery
  • yii
  • Swiper
  • ClipboardJS
  • Highcharts
  • modalOpenEvent
  • modalCloseEvent
  • modalInitEvent
  • modalBeforeOpenEvent
  • modalBeforeCloseEvent
  • openMod
  • modalEvent
  • openOtherModal
  • openModal
  • openModalsScroll
  • openModalOnly
  • closeModal
  • closeModalsScroll
  • closeModalOnly
  • THREE
  • regeneratorRuntime
  • __THREE__
  • _gsScope
  • _gsQueue
  • GreenSockGlobals
  • com
  • _gsDefine
  • Ease
  • Power4
  • Strong
  • Quint
  • Power3
  • Quart
  • Power2
  • Cubic
  • Power1
  • Quad
  • Power0

Cookies

  • PHPSESSID
  • twk_idm_key
  • TawkConnectionTime

Browser storage keys

  • exist_test

TLS session and certificate

Subject alternative names
  • *.yokofinance.com
  • yokofinance.com
Cipher
AES_128_GCM
Issuer
YE1
Subject
*.yokofinance.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

2

Registered domain age, days

2

Certificate age, days

4

Certificate validity, days

89

Page requests

119

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-2aab354
Score
99
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
LiteSpeed
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Uuid
01a1a9b9-f6ff-74cb-9f8b-81da3ca134a5
Final url
https://yokofinance.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://yokofinance.com/",
        "from": "http://yokofinance.com/",
        "status": 307
    }
]
Ip
198.251.81.49
Ptr
d2mail49.my-control-panel.com
Contacted domains
[
    "widget-v3.smartsuppcdn.com",
    "embed.tawk.to",
    "ka-f.fontawesome.com",
    "va.tawk.to",
    "static.getbutton.io",
    "cdnjs.cloudflare.com",
    "websocket-visitors.smartsupp.com",
    "bootstrap.smartsuppchat.com",
    "www.smartsuppchat.com",
    "cdn.gtranslate.net",
    "kit.fontawesome.com",
    "use.fontawesome.com",
    "iqfinanceoption.ltd"
]
Contacted IP addresses
[
    "195.181.170.19",
    "2a02:6ea0:c700::101",
    "18.185.13.80",
    "2606:4700:20::681a:fdd",
    "2a02:6ea0:c77a::47",
    "172.66.161.212",
    "172.67.139.119",
    "2606:4700:20::ac43:44cc",
    "104.17.24.14",
    "2606:4700:4404::6812:2844",
    "2606:4700:3033::ac43:8ef5",
    "198.251.81.49"
]
Asns
[
    "60068",
    "16509",
    "13335",
    "53667"
]
Countries
[
    "DE",
    "US"
]
Linked domains
[
    "www.youtube.com",
    "t.me",
    "www.e-services.cr.gov.hk",
    "getbutton.io"
]
Social
[
    "https://www.youtube.com",
    "https://t.me"
]
Document hash
d550d7f5ad7ab2c7df66e9f4893206760ef9ef35cd67ffe83d3bafa7766c16e7
Script hashes
[
    "01553ed625606e998897ded26835c783d7b506705316d85f58f9d70d58c1a143",
    "a944a4f6523730a2b8fc2f2b9cb721a3e213f072ded914b6e1d119fbf6dc9b19",
    "14299655cd4cc668ea9c08dcfc8a85561004e4fe8d4f9934e1cd827f0250aa38",
    "335996388701cdad34eafee059fa9ee1cfb7dd3bc424df039d5ed61868d76d20",
    "679a9d345a9c8fe68d19d5d77aa39009a4d6e5263e0efa4ada370200d4e61101",
    "493c46ee8249d8f7298654566b61ab4cabfaec7e38435e145f6cdbe8d818d041",
    "829eeb290ba5f75eced40d1e3dc778a02f86fa201606f1d116e80e2fd8ef3c0d",
    "b4d88c72b6fd217f52352b579c2fcc158e65f1a11d3853309b668468b1c1d221",
    "f95839d3309b9d77efc97a35eee16da10658f0f3253e841507085fce3871b446",
    "f52635cb7d42762134881672b20409732c1b4e3e82bce3ad1640ee155fe78807"
]
Globals
[
    "FontAwesomeKitConfig",
    "$",
    "jQuery",
    "yii",
    "Swiper",
    "ClipboardJS",
    "Highcharts",
    "modalOpenEvent",
    "modalCloseEvent",
    "modalInitEvent",
    "modalBeforeOpenEvent",
    "modalBeforeCloseEvent",
    "openMod",
    "modalEvent",
    "openOtherModal",
    "openModal",
    "openModalsScroll",
    "openModalOnly",
    "closeModal",
    "closeModalsScroll",
    "closeModalOnly",
    "THREE",
    "regeneratorRuntime",
    "__THREE__",
    "_gsScope",
    "_gsQueue",
    "GreenSockGlobals",
    "com",
    "_gsDefine",
    "Ease",
    "Power4",
    "Strong",
    "Quint",
    "Power3",
    "Quart",
    "Power2",
    "Cubic",
    "Power1",
    "Quad",
    "Power0"
]
Cookies
[
    "PHPSESSID",
    "twk_idm_key",
    "TawkConnectionTime"
]
Storage keys
[
    "exist_test"
]
Tls
{
    "san": [
        "*.yokofinance.com",
        "yokofinance.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "*.yokofinance.com",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-30T00:04:26Z",
    "valid_from": "2026-11-01T00:04:27Z"
}
Domain age days
2
Apex age days
2
Tls age days
4
Tls valid days
89
Requests
119
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-2aab354"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "LiteSpeed",
    "content-type": "text/html; charset=UTF-8"
}

Spamhaus DBL

Check recorded; verdict not retained

Open report

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: 12 fields

Mail configuration

MX records
  • mail.yokofinance.com
SPF record
v=spf1 a mx ip4:198.251.81.49 ip4:198.251.83.49 ip4:198.251.83.217 ~all
SPF lookups
2

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

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

TLS connection

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

Ports

Open ports
  • 21
  • 25
  • 53
  • 80
  • 110
  • 143
  • 443
  • 587
  • 993
  • 995

DNS servers

Nameservers
  • IP address
    199.195.252.13
    Host
    ns103.my-control-panel.com
  • IP address
    198.251.83.217
    Host
    ns104.my-control-panel.com
DNS zone
yokofinance.com

Location

IP address
198.251.81.49
ASN
53667
Organization
FranTech Solutions
City
New York City
Country
US

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
*.yokofinance.com

DNS records

A
  • 198.251.81.49
MX
  • Mail server
    mail.yokofinance.com
    Priority
    10
NS
  • ns104.my-control-panel.com
  • ns103.my-control-panel.com
SOA
Primary nameserver
ns103.my-control-panel.com
Hostmaster
hostmaster.yokofinance.com
Serial
2026110105
Refresh, seconds
3600
Retry, seconds
3600
Expiry, seconds
1209600
Minimum TTL, seconds
1800
TXT
  • v=spf1 a mx ip4:198.251.81.49 ip4:198.251.83.49 ip4:198.251.83.217 ~all

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

IP lookup

IP address
198.251.81.49
IP version
4

Registration record

Registrar
Dynadot Inc
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • ns103.my-control-panel.com
  • ns104.my-control-panel.com
Original source fields · JSON
Mail configuration
{
    "mx": [
        "mail.yokofinance.com"
    ],
    "spf": "v=spf1 a mx ip4:198.251.81.49 ip4:198.251.83.49 ip4:198.251.83.217  ~all",
    "spf_lookups": 2
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-11-05T03:24:26Z",
    "first": "2026-11-05T03:24:26Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 1764
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        21,
        25,
        53,
        80,
        110,
        143,
        443,
        587,
        993,
        995
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "199.195.252.13",
            "host": "ns103.my-control-panel.com"
        },
        {
            "ip": "198.251.83.217",
            "host": "ns104.my-control-panel.com"
        }
    ],
    "zone": "yokofinance.com"
}
Location
{
    "ip": "198.251.81.49",
    "asn": "53667",
    "org": "FranTech Solutions",
    "city": "New York City",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "*.yokofinance.com"
}
DNS records
{
    "A": [
        "198.251.81.49"
    ],
    "MX": [
        "{\"exchange\": \"mail.yokofinance.com\", \"priority\": 10}"
    ],
    "NS": [
        "ns104.my-control-panel.com",
        "ns103.my-control-panel.com"
    ],
    "SOA": "{\"nsname\": \"ns103.my-control-panel.com\", \"hostmaster\": \"hostmaster.yokofinance.com\", \"serial\": 2026110105, \"refresh\": 3600, \"retry\": 3600, \"expire\": 1209600, \"minttl\": 1800}",
    "TXT": [
        "v=spf1 a mx ip4:198.251.81.49 ip4:198.251.83.49 ip4:198.251.83.217  ~all"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "198.251.81.49",
    "family": 4
}
Registration record
{
    "registrar": "Dynadot Inc",
    "created": "2026-10-31T11:41:45Z",
    "updated": "2026-10-31T11:44:23Z",
    "expires": "2027-10-31T11:41:45Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "ns103.my-control-panel.com",
        "ns104.my-control-panel.com"
    ]
}

Explore

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

Last checked

Stored Capture · 1 capture

All capture links and hashes (1)

Domain details

Domain
Registrar Dynadot US(US)
RegistrationCreated Oct 31, 2026 (5d · Brand New!) — Expires Oct 31, 2027
Technical detailsProvenance & timestamps
First DetectedNov 5, 2026
Submitted URLhttp://yokofinance.com/
Favicon Hash
Case ID
Observed page title
Bot Verification
TLS Certificate
Issued by YE1 · stored validity ends in 85 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States198.251.81.49
Network ASN
AS53667
Organization
FranTech Solutions
Observed location
United StatesStaten Island, US
Server header
LiteSpeed

Nameservers 2

  • ns103.my-control-panel.com
  • ns104.my-control-panel.com

SOA

  • nsname: ns103.my-control-panel.com
  • hostmaster: hostmaster.yokofinance.com
  • serial: 2026110105
  • refresh: 3600
  • retry: 3600
  • expire: 1209600
  • minttl: 1800

Mail routing 1 MX record

  • mail.yokofinance.com

Location describes the IP network.

TLS certificate

Issuer
YE1
Valid from
2026-11-01 00:04:27
Valid until
2027-01-30 00:04:26
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate names · 2 SANs
  • *.yokofinance.com
  • yokofinance.com

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

Report This Domain Submit evidence & help protect others

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://yokofinance.com/
Final URL: https://yokofinance.com/
Bot Verification
Response
HTTP 200
HTML body
1.8 KB
Compressed
824 B
Links
0 internal · 0 external
Selected response headers
Content-Type: text/html
Content-Encoding: gzip
Server: LiteSpeed
Cache-Control: no-cache,no-store,private
Security headers present
X-Frame-Options
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 10
alt-svc
h3=":443"; ma=2592000, h3-29=":443"; ma=2592000
Cache-Control
no-cache,no-store,private
Connection
close
Content-Encoding
gzip
Content-Length
1103
Content-Type
text/html
Date
Thu, 05 Nov 2026 03:24:19 GMT
Server
LiteSpeed
Vary
Accept-Encoding
X-Frame-Options
SAMEORIGIN

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

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: 119 SHA-256 hashes: 115 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-11-05 03:25 UTC.

Open this scan on URLScan 01a1a9b9-f6ff-74cb-9f8b-81da3ca134a5 ↗

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

Separate monitor HTTP observation

Source: domain_monitor. This stored snapshot does not establish current availability.

Observed · UTC
Recorded HTTP status
200
Probe value as recorded
200
Original source timestamp
2026-11-04 22:28:08
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. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-11-05 11:21:21.318386
    Evidence SHA-256
    547991b570db3c8269bee0185b7fa12df05c0b418f4b7a797fb4d0bb740e4f46
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-05 11:21:21.318386
    Evidence reason
  2. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-11-05 04:23:41.000000
    Evidence SHA-256
    18ce7b85514bcd827d89f569572c982e961c442301e1dbe8e0116d33a424d03a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-05 04:23:41
    Evidence reason
  3. 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-11-05 04:23:41.000000
    Evidence SHA-256
    18ce7b85514bcd827d89f569572c982e961c442301e1dbe8e0116d33a424d03a
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-05 04:23:41
    Evidence reason

Threat Response Pipeline

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

Recorded events: 8. 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
    yokofinance.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · Forensic Evidence Collected Recorded: 5 of 5
  • 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
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, URLQuery, stored screenshot
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

4 entries
  1. Abuse report sent

    PD-3313C3218D2294CC29EF · Receipt 84446

    abuse@dynadot.com
  2. Wayback Machine

    Page archived

    View source
  3. Added to PhishDestroy

    yokofinance.com

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

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

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

yokofinance.com

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-3313C3218D2294CC29EF Recipient: abuse@dynadot.com
Page title stored with report: Bot Verification
PDF notice generated
Deep Analysis
Help & reporting

Were You Affected by This Site?

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

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.

Official reporting routes

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.

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 yokofinance.com)
  • Communications — emails, texts, phone numbers, usernames the scammer used

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

Where should I report the scam?

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

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

How do phishing scams typically work?

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

How can I protect myself in the future?

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

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

Stay Informed, Stay Safe

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

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.

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

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

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/yokofinance.com"
  title="PhishDestroy threat report for yokofinance.com"
  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>