This domain, rode.finance, is flagged as a high-risk generic phishing threat and remains active as of July 12, 2026. Registered on April 17, 2026, through HOSTINGER operations, UAB, the domain resolves to IP address 216.198.79.1. The page title is 'RODE | Predict. Convict. Earn.' Analysis of the infrastructure reveals the use of Vercel hosting and HSTS for transport security, with an SSL certificate issued by Let's Encrypt. Threat intelligence sources indicate broad recognition of malicious activity: VirusTotal reports 3 out of 95 security vendors flagging the domain, and AlienVault OTX lists it in 23 threat intelligence pulses. The domain appears on two security blocklists and is blocked by PhishDestroy and BLP-Malware. The Gridinsoft trust score is 0 out of 100, confirming high suspicion. While the exact phishing scheme—whether credential harvesting, financial fraud, or another type—has not been publicly detailed, the combination of recent registration, low trust score, multi-source threat detection, and active status strongly suggests ongoing malicious operation. Defenders should block the domain at network and email gateways, monitor for any associated subdomains or related IPs, and review logs for connections to 216.198.79.1. Users encountering this domain should avoid interaction and report it to their security team.
DOM Analysisanalyzed 2026年10月9日score 96/1002 brand signals
Submitted URLhttp://rode.finance/
Favicon Hash
ICANN OVERSIGHT
认证和 RAA 背景
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-13 22:30:00 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 22:30:00 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.
技术 · 2 identified
V
Vercel
PaaSCDN
Cloud platform for frontend deployment, optimized for Next.js.
H
HSTS
安全
HTTP Strict Transport Security — forces browsers to use HTTPS connections only.
Google PageSpeed Insights — mobile performance audit of rode.finance· checked Jul 13, 2026
59
Needs Work
Performance
FCP
1.99s
First Contentful Paint
LCP
8.35s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
550ms
Total Blocking Time
SI
3.69s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
VirusTotal Detections Update2026-07-12 22:44:00 UTC
VirusTotal scanner detections updated from 0 to 3. Added scanner alerts: CRDF, Gridinsoft, SOCRadar.
威胁响应 Pipeline
发现
Analysis
Monitoring
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
(LT)
