Skip to security report
Redirect recorded ruji.networkverify-connect-outputmint4k3dyjzvzp8emzwuxbbcjevwskk6r.one Details
ruji.network favicon
Domain security and threat intelligence

ruji.network

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 ruji.network on 2026-06-18. Stored VirusTotal result: 12/92 engines flagged. Malicious: 10. Suspicious: 2. Analysis time (as stored): 2026-10-02 06:37 UTC. Retrieved (as stored): 2026-10-30 04:00 UTC.

Page title: “Web3 Connect Demo”

More about the sources
Recorded security signals

Stored VirusTotal result: 12/92 engines flagged. Malicious: 10. Suspicious: 2. Analysis time (as stored): 2026-10-02 06:37 UTC. Retrieved (as stored): 2026-10-30 04:00 UTC. Use caution — do not enter credentials or personal information.

VirusTotal detections: 12/92 Spamhaus DBL: phishing domain
Registrar
United StatesDynadot
Resolved IP
United States172.67.208.109Amazon.com, Inc. · CDN
Registered
2026-06-09
First seen by PhishDestroy
2026-06-18
OTX
community references
Page captures
open gallery
Domain age
registered 2026-06-09 according to RDAP
Reports sent
view timeline
OTX: 16 refs 2026-06-18 1 Report Sent CDN

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.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
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
Write a police report

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

ABUSE NOTICE · 7D+ 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; 5 months 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
5 months
Reports sent
1
Latest case ID
PD-20260618-EDF1B5
Current status
HTTP 301 at latest stored check

Analysis

Domain summary

PhishDestroy first recorded ruji.network on 2026-06-18. Stored VirusTotal result: 12/92 engines flagged. Malicious: 10. Suspicious: 2. Analysis time (as stored): 2026-10-02 06:37 UTC. Retrieved (as stored): 2026-10-30 04:00 UTC. Risk: critical (evidence score 98/100). Registrar: Dynadot. Status: Last known active. Hosting: CLOUDFLARENET - Cloudflare, Inc., US. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
12 / 92
Scam type (automated label)
Generic Phishing
Hosting
United States172.67.208.109Amazon.com, Inc. · CDN
Registrar
United StatesDynadot
Registered
2026-06-09
OTX
16 community refs
Page captures
6

PhishDestroy analysis, earlier unreviewed version

The domain ruji.network, now offline, is identified as a phishing threat by 5 out of 91 VirusTotal vendors. Hosted on Amazon's infrastructure, it employs a Let's Encrypt SSL certificate, a common tactic to lend legitimacy to phishing sites. PhishDestroy has flagged this domain on its public blocklist, highlighting its malicious nature.

Registered with Dynadot Inc, ruji.network was created on June 9, 2026, and detected by PhishDestroy on June 18, 2026. The domain's quick takedown indicates effective intervention, yet its initial operation period underscores the need for rapid detection systems. The platform risk score of 68 out of 100 suggests a significant threat level, while the abuse score of 21 out of 100 reflects moderate malicious activity.

Despite being offline, ruji.network's presence in the threat landscape emphasizes the importance of early detection. The domain's use of Let's Encrypt SSL and Amazon hosting showcases how legitimate services can be manipulated for phishing purposes. This incident serves as a reminder of the evolving tactics employed by cybercriminals to bypass traditional security measures.

Source evidenceVirusTotal 12 / 92 · OTX 16 references 7 sources

VirusTotal

12 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 10 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
11
Denominator
91
Vendors
alphaMountain.ai, BitDefender, CRDF, CyRadar, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Lionic, Sophos, Webroot
Checked at
2026-09-28 04:32:35

Spamhaus DBL

phishing domain

OTX

16 community references

Open report

URLScan

Page capture

Open report
URLScanOriginal source recordObserved: 23 fields
Separate monitor record

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

UUID
019edbb6-825a-702e-b0d8-7d5c9daaafb0
Enriched at
2026-06-25T08:18:39Z
Source timestamps
Urlscan enriched at: 2026-06-25 10:18:39

PhishDestroy DOM

98 / 100 · heuristic score · 0 brand references · 1 classification

Content heuristic only; not the final score

Open report
Page code check by a separate monitor · 0 / 100 · 2026-06-18 18:20 UTC

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

Heuristic score
0
Analyzed at
2026-06-18T18:20:04Z
Source timestamp
2026-06-18 20:20:04
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
ruji.network - Phishing Domain Exploiting Let's Encrypt
AI description
ruji.network is a phishing domain flagged by 5/91 vendors, hosted on Amazon infrastructure. It uses Let's Encrypt SSL.
AI summary
The domain ruji.network, now offline, is identified as a phishing threat by 5 out of 91 VirusTotal vendors. Hosted on Amazon's infrastructure, it employs a Let's Encrypt SSL certificate, a common tactic to lend legitimacy to phishing sites. PhishDestroy has flagged this domain on its public blocklist, highlighting its malicious nature. Registered with Dynadot Inc, ruji.network was created on June 9, 2026, and detected by PhishDestroy on June 18, 2026. The domain's quick takedown indicates effective intervention, yet its initial operation period underscores the need for rapid detection systems. The platform risk score of 68 out of 100 suggests a significant threat level, while the abuse score of 21 out of 100 reflects moderate malicious activity. Despite being offline, ruji.network's presence in the threat landscape emphasizes the importance of early detection. The domain's use of Let's Encrypt SSL and Amazon hosting showcases how legitimate services can be manipulated for phishing purposes. This incident serves as a reminder of the evolving tactics employed by cybercriminals to bypass traditional security measures.
AI generated by
openai-gpt4o
AI generated at
2026-06-22T21:06:10Z
Revision
c079754b2662972cc703b69da4920e3fe35e3055315bb0c2bf8a95f78f0de44d
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
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Dga domains

Questions about ruji.network

Is ruji.network legit?

PhishDestroy rates ruji.network as critical risk (evidence score 98/100) from the recorded evidence; it was first recorded on 2026-06-18. Stored VirusTotal result: 12/92 engines flagged. Malicious: 10. Suspicious: 2. Analysis time (as stored): 2026-10-02 06:37 UTC. Retrieved (as stored): 2026-10-30 04:00 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is ruji.network safe to connect a wallet?

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

What should I do if I used ruji.network?

  • 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 (6)

All capture links and hashes (6)
Observed page title
Web3 Connect Demo
TLS Certificate
Issued by Let's Encrypt / YR2
ruji.network: caution — Flagged by Spamhaus DBL, 11/91 VirusTotal engines. PhishDestroy risk score 98/100 (critical).
Social preview card ruji.network: caution — Flagged by Spamhaus DBL, 11/91 VirusTotal engines. PhishDestroy risk score 98/100 (critical). v 318781c7a483

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 100 report ↗
IP Context United States172.67.208.109 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-06activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Dynadot US(US)
Abuse contactabuse@dynadot.com
RegistrationCreated 2026-06-09 (166d) — Expires 2027-06-09
HTTP Status301 Moved Permanently
Technical detailsProvenance & timestamps
First Detected2026-06-18
DOM Analysisanalyzed 2026-06-18score 98/100
Submitted URLhttp://ruji.network/
Favicon Hash
Case ID
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

Shared CDN edge
Resolved IP
United States172.67.208.109
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
Organization
AS16509 Amazon.com, Inc.
Observed location
United StatesSan Jose, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

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

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-08-17 15:55:18
Valid until
2026-11-15 15:55:17
Hostname match
No
Validity
Stored certificate expired
Collection time
2026-10-10 07:03 UTC
Collection source
PhishDestroy collector
Certificate fingerprint2afec7926151cb0a666bdf5f040ad5c7012ba9640434894643b1ba100c9d9418
Certificate names · 2 SANs
  • verify-connect-outputmint4k3dyjzvzp8emzwuxbbcjevwskk6r.one
  • *.verify-connect-outputmint4k3dyjzvzp8emzwuxbbcjevwskk6r.one

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-22 11:18 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting DNS: Resolved
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-11-22 11:18 UTC
RDAP registration
Observed timeline last reachable: 2026-11-22 11:18 UTC
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 · 2 identified
Open complete records

VirusTotal Analysis

12 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 13 detections
CRDF
G-Data
Lionic
Sophos
CyRadar
Webroot
Fortinet
Gridinsoft
BitDefender
Chong Lua Dao
alphaMountain.ai
Forcepoint ThreatSeeker
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

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

All stored data107
Open complete records

Captured network requests

Network requests: 19 SHA-256 hashes: 15 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 03:54 UTC.

Open this scan on URLScan 019edbb6-825a-702e-b0d8-7d5c9daaafb0 ↗

Check for cloaking

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

Cloaking could not be checked

Our scanner could not complete this check.

ruji.network
Saved result
Cloaked / Filtered
Stored observation history24
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-06-19 04:02:12
All retained availability observations235
Open complete records

Threat Response Pipeline

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

Recorded events: 12. 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
    ruji.network detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · OTX Community References · Cloudflare Radar: Malicious · Forensic Evidence Collected · Technical Analysis Recorded recorded
Notification RecordsSent Report Recorded recorded
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: Dynadot LLC. Abuse contacts: 1.
    • abuse@dynadot.com
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

5 entries

Lifecycle

  1. Domain registered
  2. Added to PhishDestroy+9 d 8 h
  3. First abuse report sent+5 min
  4. VirusTotal analysis with detections+105 d 13 h

Reported 9 d 8 h after registration

  1. AlienVault OTX

    16 community references

    +31 d 6 h
  2. VirusTotal

    12/92 engine detections

    +98 d 22 h
  3. URLScan

    Page captured

    +6 d 15 h
  4. Abuse report sent

    PD-20260618-EDF1B5 · Receipt 45953

    abuse@dynadot.com
    +5 min
  5. Added to PhishDestroy

    ruji.network

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

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260618-EDF1B5 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
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.

  • 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
  • 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

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 ruji.network)
  • 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/ruji.network"
  title="PhishDestroy threat report for ruji.network"
  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>