VirusTotal
11 / 89 engine detections
レポートを開く
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@omegatech.sc.
The latest stored availability evidence still shows the domain reachable; 2 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.
フィッシング: dropmefile.online — 未検証. 証拠の概要: VirusTotal 11/89 (alphaMountain.ai, Bfore.Ai PreCrime, BitDefender, Chong Lua Dao, CRDF); URLQuery 1 alert…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
11 / 89 engine detections
レポートを開く1 threat-system alert
レポートを開く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.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | dropmefile.online |
malicious | Sinkholed |
PhishDestroy threat report
The domain dropmefile.online is currently under investigation for involvement in generic phishing operations. As of July 31, 2026, it remains active and is listed on a security blocklist maintained by PhishDestroy. While the domain has not been flagged by 91 major security vendors during a recent VirusTotal scan, the absence of detections does not confirm the domain is benign. Blocklist inclusion indicates that at least one threat intelligence provider has identified suspicious or malicious behavior associated with this domain.
Technical analysis reveals that dropmefile.online was registered via NAMECHEAP INC and became active on March 4, 2026. The domain resolves to IP address 158.94.211.169 and utilizes nameservers a.dnspod.com, b.dnspod.com, and c.dnspod.com. The current infrastructure details suggest hosting is active, but there is no additional information available regarding SSL configuration, content, or specific phishing tactics used. The exact content of the website or any associated brand targeting has not yet been analyzed.
Given its active status and appearance on a reputable blocklist, defenders should treat connections to dropmefile.online as potentially risky. Network and endpoint policies should be updated to block access to this domain pending further analysis. Security teams are advised to monitor for evidence of credential harvesting, data exfiltration, or end-user access events related to this indicator. Continued monitoring of threat intelligence platforms for additional context or escalated detections is recommended as the domain remains under investigation.
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.
a.dnspod.comb.dnspod.comc.dnspod.comLocation describes the IP network.
b6f107bb454b821145c69209d9c617c0fe38bd2b5ce06b8d86eacc01e4d55d11Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of dropmefile.online · checked Jul 31, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
https://dropmefile.online/Content-Type: text/html; charset=utf-8Cache-Control: no-storeContent-Encoding: gzipclearno-storegzip667313text/html; charset=utf-8Fri, 31 Jul 2026 17:55:16 GMTAccept-EncodingcaptchaValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→dns_inactive
dns_nxdomain
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
不明→live_content
content_served
到達可能
4 community references
View source11/89 engine detections
View sourcePD-20260731-A91E4D
No threat flag
View sourcePage captured
View sourcedropmefile.online
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
dropmefile.online
PD-20260731-A91E4D Recipient: abuse@omegatech.sc Registrar: Namecheap Inc (United States) Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
dropmefile.online)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.