VirusTotal
12 / 92 engine detections
レポートを開く“OnRe | The world’s on-chain reinsurance company”
フィッシング: rewards-onre.finance — コンテンツが利用できません. 証拠の概要: VirusTotal 12/92 (alphaMountain.ai, BitDefender, CRDF, CyRadar, Forcepoint ThreatSeeker); Spamhaus…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
12 / 92 engine detections
レポートを開く15/100
レポートを開くDBL_PHISH
4 community references
レポートを開くprovider verdict: clean
レポートを開くNo threat flag
レポートを開くNo malicious flag
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
Analysis of rewards-onre.finance indicates a recently established phishing domain targeting users with fraudulent reward schemes. The domain was registered on July 21, 2026, through NICENIC INTERNATIONAL GROUP CO., LIMITED, and remains active as of July 24, 2026. Infrastructure checks reveal the domain resolves to the IP address 62.60.226.88, though no nameservers are currently assigned, which may suggest an incomplete or evasive setup.
The domain appears on one security blocklist and is blocked by PhishDestroy, while VirusTotal reports flagging by 2 of 91 security vendors, confirming its malicious classification. No further details regarding the specific brand impersonated, phishing kit used, or exact content of the site are available at this time. The absence of nameservers and minimal detection coverage may indicate early-stage deployment or attempts to evade automated detection systems.
Defenders are advised to treat this domain as high-risk and implement blocking measures at the DNS or network level. Additional monitoring of the resolving IP 62.60.226.88 may reveal related malicious infrastructure, though no associated ASN or hosting provider details are currently available. Given the domain's recent registration and active status, further investigation into its hosting environment and potential ties to other phishing campaigns is recommended.
Last checked
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.
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.
Location describes the IP network.
76ac0f833c1afa55e13d275ac74da91fef0ddc4f27ded26baf68507c9d1fbadcwww.rewards-onre.financeSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.rewards-onre.financeDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of rewards-onre.finance · checked Jul 24, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
rewards-onre.finance
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
到達可能→利用不可
不明→protected
http_access_restricted · access_restriction
不明→protected
http_access_restricted · access_restriction
不明→protected
http_access_restricted · access_restriction
不明→protected
http_access_restricted · access_restriction
不明→protected
http_access_restricted · access_restriction
不明→protected
http_access_restricted · access_restriction
不明→protected
http_access_restricted · access_restriction
不明→protected
http_access_restricted · access_restriction
protected
http_access_restricted · access_restriction
12/92 engine detections
View source4 community references
View sourceNo threat flag
View sourcerewards-onre.finance
View sourcePage captured
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
rewards-onre.finance)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
保存されたブロックリスト、WHOIS、DNS、および公開スキャン証拠を使用した脅威分析
今すぐスキャン不審なドメインを当社の脅威データベースに報告してください — コミュニティを守りましょう
レポート最近のフィッシングレポートと観察された可用性の変化
監視リアルタイムの脅威を監視するか、誤検知だと思われる場合はこのリストに異議を申し立ててください
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.