The domain origindefi.agency is identified as a crypto scam, specifically targeting users interested in decentralized finance (DeFi) platforms. Detected by PhishDestroy on the same day it was created, May 28, 2026, it quickly garnered attention with two out of 95 vendors on VirusTotal marking it as malicious. The domain is also listed on three public blocklists, including those maintained by PhishDestroy, MetaMask, and SEAL.
Registered through HOSTINGER operations, UAB, and hosted on an IP address associated with Hostinger International Limited in the UK, origindefi.agency lacks a valid SSL certificate, which is a common trait among phishing sites. The platform risk score of 73 out of 100 indicates a significant threat level. Despite its offline status, the domain's initial rapid detection highlights the effectiveness of early identification systems in mitigating potential damage.
The absence of an SSL certificate combined with the immediate detection by PhishDestroy underscores the domain's intent to deceive users without standard security measures. The swift action of blocklisting by multiple entities further demonstrates the collaborative effort in the cybersecurity community to protect users from such threats. While the site is currently offline, the incident serves as a reminder of the persistent risks associated with crypto scams and the importance of staying informed about emerging threats.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='origindefi.agency', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
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.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:10:41 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-06-25 22:02:15 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-25 22:02:15 UTC → 2026-09-30 16:14:55 UTC · 2,322.21hmidpoint estimate ≈ 2026-08-13 07:08:35 UTC · precision very low · 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.
技术 · 4 identified
P
PHP
Programming languages
PHP is a general-purpose scripting language used for web development.
Google PageSpeed Insights — mobile performance audit of origindefi.agency· checked May 28, 2026
96
Good
Performance
FCP
1.83s
First Contentful Paint
LCP
1.83s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
4.05s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
13 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.
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.
