VirusTotal
16 / 91 engine detections
レポートを開く“OnRe | The world’s on-chain reinsurance company”
Security analysis of snapshots-onre.finance covers observed phishing indicators, infrastructure evidence, current status, and defensive guidance.
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
16 / 91 engine detections
レポートを開くDBL_PHISH
4 community references
レポートを開くprovider verdict: clean
レポートを開く80/100
レポートを開く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 the domain snapshots-onre.finance, registered on July 24, 2026 through NICENIC INTERNATIONAL GROUP CO., LIMITED, indicates that it is actively being used for generic phishing. The domain resolves to the IPv4 address 62.60.226.88 and is served by the authoritative name servers coco.bunny.net and kiki.bunny.net. In threat intelligence feeds the domain appears on a single security blocklist and is explicitly listed as blocked by the PhishDestroy service. VirusTotal has processed the domain and two of the ninety‑one scanned security vendors have raised detections, confirming that at least a subset of scanning engines consider the host malicious.
The domain remains operational as of the report date, July 25, 2026, and no evidence of takedown or sink‑hole redirection has been observed. The available data does not include SSL certificate details, HTTP response codes, page title, or any observed landing‑page content, leaving the exact phishing vector and targeted brand undefined. Likewise, no information on associated infrastructure such as additional IPs, ASN, or hosting provider has been disclosed beyond the single resolved address. Consequently, the full scope of the campaign, including potential victim profiles and credential‑harvesting mechanisms, cannot be precisely determined at this time.
Defenders should add snapshots‑onre.finance to their deny‑list policies across perimeter and endpoint controls, monitor DNS queries for the associated name servers, and enforce network‑level blocking of the resolved IP address 62.60.226.88. Continuous re‑query of VirusTotal and other reputation services is recommended to capture any changes in detection counts. Organizations that employ email filtering should treat any messages containing links to this domain as malicious, and users should be instructed to avoid clicking such links. Ongoing observation of the domain’s activity on public blocklists will aid in assessing whether the threat persists or expands.
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.
coco.bunny.netkiki.bunny.netLocation describes the IP network.
e445037f75c807cb5d85ff82eb6e90efd2b04e3fca40cece861ffc8c4ba0f83ewww.snapshots-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.snapshots-onre.financeDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of snapshots-onre.finance · checked Jul 25, 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.
snapshots-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
16/91 engine detections
View source4 community references
View sourceNo threat flag
View sourcePage captured
View sourcesnapshots-onre.finance
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 ↗
snapshots-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.