Skip to security report
Redirect recorded ouyi.supportzhgwexpouy.net Details
ouyi.support favicon
Domain security and threat intelligence

ouyi.support

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

PhishDestroy first recorded ouyi.support on 2026-04-20. Stored VirusTotal result: 13/92 engines flagged. Malicious: 12. Suspicious: 1. Analysis time (as stored): 2026-10-18 10:04 UTC. Retrieved (as stored): 2026-11-07 17:46 UTC.

Page title: “Earn rewards when you get started on OKX | My referral code: 51669578 | OKX Europe”

More about the sources
Recorded security signals

Stored VirusTotal result: 13/92 engines flagged. Malicious: 12. Suspicious: 1. Analysis time (as stored): 2026-10-18 10:04 UTC. Retrieved (as stored): 2026-11-07 17:46 UTC. Use caution — do not enter credentials or personal information.

VirusTotal detections: 13/92
Registrar
United StatesDynadot
Resolved IP
United States54.215.31.113AWS EC2 (us-west-1)
Registered
2025-08-22
First seen by PhishDestroy
2026-04-20
OTX
community references
Page captures
open gallery
Domain age
registered 2025-08-22 according to RDAP · source data differ
OTX: 4 refs 2026-04-20

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

Analysis

Domain summary

PhishDestroy first recorded ouyi.support on 2026-04-20. Stored VirusTotal result: 13/92 engines flagged. Malicious: 12. Suspicious: 1. Analysis time (as stored): 2026-10-18 10:04 UTC. Retrieved (as stored): 2026-11-07 17:46 UTC. Risk: critical (evidence score 95/100). Registrar: Dynadot. Hosting: Amazon.com, Inc. Do not enter credentials or connect a wallet.

Critical
VirusTotal
13 / 92
Scam type (automated label)
Brand Impersonation
Hosting
United States54.215.31.113AWS EC2 (us-west-1)
Registrar
United StatesDynadot
Registered
2025-08-22
OTX
4 community refs
Page captures
2

PhishDestroy analysis, earlier unreviewed version

PhishDestroy identifies ouyi.support as a live crypto drainer page designed to trick visitors into connecting crypto wallets and signing malicious transactions. The site mimics a legitimate brand interface to lure users into approving unauthorized token transfers that drain funds within seconds. Anyone who connects a wallet or enters seed phrases on this page risks losing all assets in connected accounts.

This domain was flagged after registering on August 22, 2025, through Dynadot Inc. It resolves to IP 54.215.31.113 and uses a Let’s Encrypt SSL certificate to appear trustworthy. VirusTotal currently shows 3 out of 95 security engines detecting the threat, which is common for newly activated crypto drainers that evade initial scans. The combination of a fresh registration date and low detection rate makes this site particularly dangerous for unsuspecting users.

If you visited ouyi.support, immediately disconnect your wallet from the site, revoke any suspicious permissions in your wallet settings, and transfer remaining funds to a new wallet. Run a malware scan on your device and consider rotating all passwords used on crypto platforms. Report the domain to PhishDestroy for further analysis to help protect others.

Source evidenceVirusTotal 13 / 92 · OTX 4 references 6 sources

VirusTotal

13 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 12 fields
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

Source
VirusTotal
Numerator
16
Denominator
91
Vendors
alphaMountain.ai, BitDefender, Chong Lua Dao, ESET, Emsisoft, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Kaspersky, Lionic, Netcraft, SOCRadar, Sophos, VIPRE, Webroot
Checked at
2026-08-27 05:04:23

OTX

4 community references

Open report

PhishDestroy DOM

10 / 100 · heuristic score · 4 brand references · 1 classification

Content heuristic only; not the final score

Open report
Technical metadata

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
ouyi.support Safety Check — Crypto Drainer Detected
AI description
PhishDestroy flags ouyi.support as a crypto drainer impersonating a brand. Domain registered on Aug 22, 2025, via Dynadot, with 0/95 VirusTotal detections.
AI summary
PhishDestroy identifies ouyi.support as a live crypto drainer page designed to trick visitors into connecting crypto wallets and signing malicious transactions. The site mimics a legitimate brand interface to lure users into approving unauthorized token transfers that drain funds within seconds. Anyone who connects a wallet or enters seed phrases on this page risks losing all assets in connected accounts. This domain was flagged after registering on August 22, 2025, through Dynadot Inc. It resolves to IP 54.215.31.113 and uses a Let’s Encrypt SSL certificate to appear trustworthy. VirusTotal currently shows 3 out of 95 security engines detecting the threat, which is common for newly activated crypto drainers that evade initial scans. The combination of a fresh registration date and low detection rate makes this site particularly dangerous for unsuspecting users. If you visited ouyi.support, immediately disconnect your wallet from the site, revoke any suspicious permissions in your wallet settings, and transfer remaining funds to a new wallet. Run a malware scan on your device and consider rotating all passwords used on crypto platforms. Report the domain to PhishDestroy for further analysis to help protect others.
AI generated by
mistral
AI generated at
2026-04-20T11:58:46Z
Revision
e23d4d0f7aca7e1519600dead15847c4123bc6e1b9a629fb9098057fe0cd1232
Mode
stored
Interpretation
Earlier stored analysis, not reviewed; 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

Questions about ouyi.support

Is ouyi.support legit?

PhishDestroy rates ouyi.support as critical risk (evidence score 95/100) from the recorded evidence; it was first recorded on 2026-04-20. Stored VirusTotal result: 13/92 engines flagged. Malicious: 12. Suspicious: 1. Analysis time (as stored): 2026-10-18 10:04 UTC. Retrieved (as stored): 2026-11-07 17:46 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is ouyi.support safe to connect a wallet?

Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on ouyi.support. A confirmed blockchain transaction cannot be reversed.

What should I do if I used ouyi.support?

  • 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
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • 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 1
PhishDestroy PhishDestroy list View source

Page captures (2)

All capture links and hashes (2)
Observed page title
Earn rewards when you get started on OKX | My referral code: 51669578 | OKX Europe
Automated brand references
Argent Mastercard OKX Visa
TLS Certificate
Issued by Let's Encrypt · stored validity ends in 89 days
ouyi.support: caution — 16/91 VirusTotal engines. PhishDestroy risk score 95/100 (critical).
Social preview card ouyi.support: caution — 16/91 VirusTotal engines. PhishDestroy risk score 95/100 (critical). v cb6943bc16af

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Okx report ↗
IP Reputation United States54.215.31.113 47/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worse 60 reports PhishingOpen ProxyWeb SpamPort ScanHackingBrute-ForceBad Web BotExploited HostWeb App Attack checked 2026-11-21 last reported
OTX tags blocklistcryptodrainerfraudphishdestroyphishingscam
Registrar Dynadot US(US)
Abuse contactabuse@dynadot.com
Hosting abuse contact abuse@dynadot.com Amazon.com, Inc. · AS16509
RegistrationCreated 2025-08-22 — Expires 2026-08-22
Elapsed Since First Report 215 days
What we count Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First Detected2026-04-20
DOM Analysisanalyzed 2026-11-21score 10/1004 brand signals
Submitted URLhttp://ouyi.support/
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.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States54.215.31.113
Network ASN
AS16509
Organization
AWS EC2 (us-west-1)
Observed location
United StatesSan Jose, US
Server header
TencentEdgeOne

Nameservers 1

  • ns2.dyna-ns.net

Mail routing 1 MX record

  • park-mx.above.compriority 10

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt
Valid from
2026-04-19 20:01:17
Valid until
2026-07-18 20:01:16
Hostname match
No
Validity
Stored certificate expired
Collection time
2026-04-20 14:00 UTC
Collection source
PhishDestroy collector
Certificate fingerprint4f13742d756ab3f21ef9ba94ecfb7c1c951614acd56a2e22629b310d5088b98b
Certificate names · 2 SANs
  • *.zhgwexpouy.net
  • zhgwexpouy.net

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

Latest Classified Outcome 2026-11-21 18:03 UTC

The domain no longer resolves in DNS.

Technical details
Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN
RDAP registration
Observed timeline last reachable: 2026-11-21 11:13 UTC current episode first observed: 2026-11-21 18:03 UTC observed RIP window: 2026-11-21 11:13 UTC → 2026-11-21 18:03 UTC · 6.83h midpoint estimate ≈ 2026-11-21 14:38 UTC · precision medium · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 9 identified
Open complete records

VirusTotal Analysis

13 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 18 detections
ESET
VIPRE
G-Data
Lionic
Sophos
CyRadar
Webroot
Fortinet
Kaspersky
BitDefender
Chong Lua Dao
alphaMountain.ai
Forcepoint ThreatSeeker
PageSpeed (mobile): 44

Google PageSpeed Insights — mobile performance audit of ouyi.support ·

44
Poor
Performance
FCP
3.67 s
First Contentful Paint
LCP
20.99 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
642 ms
Total Blocking Time
SI
8.35 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
6.83
Estimate basis
Bounded by observations
Estimate precision
Medium

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

All stored data124
Open complete records

Captured network requests

Network requests: 224 SHA-256 hashes: 194 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-29 04:39 UTC.

Open this scan on URLScan 019daa87-925e-708a-ab69-1fc4af847e72 ↗

Check for cloaking

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

No cloaking flag in this check

dns_nxdomain: no HTTP response; DNS NXDOMAIN recorded 2026-11-21 18:03:27.048700

ouyi.support
Saved result
Keitaro TDS
Stored observation history27
Open complete records
Separate monitor HTTP observation

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

Observed · UTC
Recorded HTTP status
No response code recorded
Original source timestamp
2026-04-21 05:00:12
All retained availability observations116
Open complete records

Threat Response Pipeline

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

Recorded events: 15. 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
  • Threat Ingested
    ouyi.support detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · OTX Community References · Automated brand label: OKX · Forensic Evidence Collected · Technical Analysis Recorded · Site Came Back Online · Content Observed Unavailable · Site Came Back Online · Content Observed Unavailable recorded
Publication & AvailabilityDestroyList Published · Time to First Unavailability recorded
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Time to First Unavailability
    Hours from detection to the first unavailable observation: 5161

Recorded activity

4 entries

Lifecycle

  1. Domain registered
  2. Added to PhishDestroy+240 d 17 h
  3. First abuse report sent+2 h 0 min
  4. VirusTotal analysis with detections+180 d 20 h

Reported 240 d 19 h after registration

  1. AlienVault OTX

    4 community references

    +33 d 19 h
  2. VirusTotal

    13/92 engine detections

    +180 d 22 h
  3. Added to PhishDestroy

    ouyi.support

    +1 h 2 min
  4. URLScan

    Malicious

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.

Stored checks and requests

Content check

Status
Dead
Reason
No response
Went dead
2026-06-06 17:36 UTC
Last status change
2026-06-06 17:36 UTC
Last checked
2026-06-06 17:36 UTC
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

Lookalike domains

89 stored lookalike domains

Names that imitate the brand, found by dnstwist. A similar name alone does not prove the same owner.

0kx.com Lookalike letters Variant of okx.com A 47.243.74.33NS ns21.domaincontrol.com 0okx.com Inserted character Variant of okx.com A 172.65.190.172NS expire1.gname-dns.com 9kx.com Replaced character Variant of okx.com NS ns1.dyna-ns.net 9okx.com Inserted character Variant of okx.com NS a.share-dns.com akx.com Vowel swap Variant of okx.com A 38.55.21.252MX alt1.aspmx.l.google.comNS ns1gmz.name.com ekx.com Vowel swap Variant of okx.com A 88.208.252.141MX mailserver.livemail.co.ukNS ns1.livedns.co.uk gkx.com Bit flip Variant of okx.com A 35.173.228.115 ikx.com Replaced character Variant of okx.com A 54.159.98.68NS ns13.domaincontrol.com iokx.com Inserted character Variant of okx.com A 212.16.186.45MX ALT1.ASPMX.L.GOOGLE.comNS ns1.stablehost.com kkx.com Bit flip Variant of okx.com A 139.162.174.209 kokx.com Inserted character Variant of okx.com MX mx.backup.mailprotect.beNS ns1.european-server.eu kox.com Swapped characters Variant of okx.com A 92.205.130.133MX mail.kox.comNS ns01.v-dns.de

Showing 12 of 89

Show 77 more
kx.com Missing character Variant of okx.com A 3.212.210.244MX kx-com.mail.protection.outlook.comNS ns1-04.azure-dns.com lkx.com Replaced character Variant of okx.com A 64.190.63.222MX localhostNS ns1.sedoparking.com lokx.com Inserted character Variant of okx.com A 172.234.24.211MX mx.plingest.comNS dns101.registrar-servers.com mkx.com Bit flip Variant of okx.com NS dns1.registrar-servers.com nkx.com Bit flip Variant of okx.com A 38.181.56.100 o0kx.com Inserted character Variant of okx.com A 111.92.241.196NS ns45.domaincontrol.com ocx.com Bit flip Variant of okx.com A 23.213.161.199NS pdns82.ultradns.biz oicx.com Lookalike letters Variant of okx.com A 13.248.169.48NS ns1.namefind.com oikx.com Inserted character Variant of okx.com A 13.248.169.48NS ns1.afternic.com oix.com Bit flip Variant of okx.com A 52.20.84.62NS ns1.atom.com ojkx.com Inserted character Variant of okx.com A 13.248.169.48NS ns1.afternic.com ojx.com Bit flip Variant of okx.com A 52.20.84.62NS ns1.atom.com ok-x.com Added hyphen Variant of okx.com A 49.235.78.38MX mxbiz1.qq.comNS f1g1ns1.dnspod.net ok.com Missing character Variant of okx.com A 47.237.132.5MX ok-com.mail.protection.outlook.comNS ns3.dnsv5.com ok8.com Bit flip Variant of okx.com A 188.114.96.3NS addilyn.ns.cloudflare.com okc.com Replaced character Variant of okx.com A 139.162.174.209 okd.com Replaced character Variant of okx.com A 15.156.13.223MX d406989.a.ess.ca.barracudanetworks.comNS ns1.netfirms.com okh.com Bit flip Variant of okx.com A 15.197.148.33NS ns55.domaincontrol.com okix.com Inserted character Variant of okx.com A 64.98.145.30MX 10mx.hover.com.cust.hostedemail.comNS dns1.name-services.com okjx.com Inserted character Variant of okx.com NS f1g1ns1.dnspod.net okkx.com Inserted character Variant of okx.com A 13.248.169.48NS ns1.afternic.com oklx.com Inserted character Variant of okx.com A 13.248.213.45NS ns31.domaincontrol.com okmx.com Inserted character Variant of okx.com A 52.20.84.62NS ns1.atom.com okox.com Inserted character Variant of okx.com A 13.248.169.48NS ns1.afternic.com okp.com Bit flip Variant of okx.com A 54.215.31.113NS ns1.dyna-ns.net oks.com Replaced character Variant of okx.com A 15.197.148.33NS ns63.domaincontrol.com okw.com Replaced character Variant of okx.com A 185.86.158.152MX okw-com.mail.protection.outlook.comNS ns0.claranet.de okx0.com Added character Variant of okx.com NS dns29.hichina.com okx4.com Added character Variant of okx.com NS dns21.hichina.com okx5.com Added character Variant of okx.com MX mxn.mxhichina.comNS dns19.hichina.com okxcom.com Variant Variant of okx.com A 54.215.31.113NS ns1.dyna-ns.net okxj.com Added character Variant of okx.com NS ns1.myhostadmin.net okxr.com Added character Variant of okx.com MX mx.ym.163.comNS f1g1ns1.dnspod.net oky.com Bit flip Variant of okx.com A 13.248.169.48NS ns1.afternic.com okz.com Bit flip Variant of okx.com A 35.173.228.115 olcx.com Lookalike letters Variant of okx.com A 205.145.129.20MX mail2.olcx.netNS dns4.olcx.com olex.com Lookalike letters Variant of okx.com A 162.0.209.215MX mx1-hosting.jellyfish.systemsNS dns1.namecheaphosting.com olkx.com Inserted character Variant of okx.com A 13.248.169.48NS ns1.afternic.com olx.com Replaced character Variant of okx.com A 13.35.58.30MX alt1.aspmx.l.google.comNS ns-1474.awsdns-56.org omkx.com Inserted character Variant of okx.com A 52.20.84.62NS ns1.atom.com omx.com Replaced character Variant of okx.com NS pdns1.ultradns.net oox.com Bit flip Variant of okx.com A 45.77.200.164NS ns1.sawsells.com opkx.com Inserted character Variant of okx.com A 13.248.169.48NS ns3.afternic.com ox.com Missing character Variant of okx.com A 0.0.0.0MX cisco-esa01-smtp-cc.ox.comNS ns0.dnsmadeeasy.com oxk.com Swapped characters Variant of okx.com A 139.162.174.209 pkx.com Replaced character Variant of okx.com A 208.98.40.203 ukx.com Vowel swap Variant of okx.com A 86.105.245.69NS ns1.eftydns.com xn--j1ahw.com Cyrillic letters Variant of okx.com A 192.64.119.174MX mx1.privateemail.comNS dns1.registrar-servers.com xn--kx-4ja.com Lookalike letters Variant of okx.com A 2.57.91.91MX mx1.hostinger.comNS ns1.dns-parking.com okx1.com Added character Variant of okx.com A 172.65.185.109NS sp1.gname-dns.com okx2.com Added character Variant of okx.com A 208.98.43.141 okx3.com Added character Variant of okx.com A 120.24.169.173NS dns31.hichina.com okx6.com Added character Variant of okx.com A 47.243.74.33NS a.share-dns.com okx8.com Added character Variant of okx.com A 15.197.225.128NS ns05.domaincontrol.com okx9.com Added character Variant of okx.com A 192.69.93.47 okxa.com Added character Variant of okx.com A 124.115.16.115MX 125.76.225.15NS ns13.xincache.com okxb.com Added character Variant of okx.com A 54.215.31.113NS ns1.dyna-ns.net okxc.com Added character Variant of okx.com A 47.243.117.145 okxd.com Added character Variant of okx.com A 74.48.129.110NS 1.namestar.com okxf.com Added character Variant of okx.com A 103.216.216.134NS ns1.ename.net okxg.com Added character Variant of okx.com A 47.243.117.145 okxh.com Added character Variant of okx.com A 104.21.10.31NS lilith.ns.cloudflare.com okxi.com Added character Variant of okx.com A 13.248.169.48NS ns3.afternic.com okxk.com Added character Variant of okx.com A 13.248.169.48NS ns1.afternic.com okxl.com Added character Variant of okx.com A 112.84.131.61MX mx.ym.163.comNS ns1.qeodns.com okxm.com Added character Variant of okx.com A 104.247.81.99NS ns1.parkingcrew.net okxn.com Added character Variant of okx.com A 154.84.62.126NS a.share-dns.com okxo.com Added character Variant of okx.com A 87.106.141.106MX mailstore1.secureserver.netNS ns43.domaincontrol.com okxp.com Added character Variant of okx.com A 218.22.210.86NS dns.bizcn.com okxq.com Added character Variant of okx.com A 13.248.169.48NS ns1.afternic.com okxs.com Added character Variant of okx.com A 172.65.185.109NS sp1.gname-dns.com okxt.com Added character Variant of okx.com A 74.48.129.110NS 1.namestar.com okxv.com Added character Variant of okx.com A 74.48.129.110NS 1.namestar.com okxw.com Added character Variant of okx.com A 47.243.117.145 okxx.com Added character Variant of okx.com A 122.10.113.188NS carla.ns.cloudflare.com okxy.com Added character Variant of okx.com A 208.98.43.141 okxz.com Added character Variant of okx.com A 13.248.169.48NS ns1.afternic.com

Community reports

Reported by 1 community member, first seen 2026-04-20

Stored reports
1
Unique reported URLs
1
Accepted1

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

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. Secure your accounts and funds first, then report. 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.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

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.

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.

  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed
  • 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
  • Downloaded a file — do not open it and scan the device with security software

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 ouyi.support)
  • 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.

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

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

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

Embed This Report

Share this threat intelligence on your website or blog

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