VirusTotal
4 / 92 engine detections
レポートを開く“BingNC”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@ceranetworks.com.
The latest stored availability evidence still shows the domain reachable; 23 days 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.
MetaMaskなりすまし: bingnc.com — 未検証. 証拠の概要: VirusTotal 4/92 (alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar); URLQuery 2 det.; 2 external…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
4 / 92 engine detections
レポートを開く2 det.
レポートを開く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
bingnc.com presents itself under the name "BingNC", a crypto-flavoured brand that PhishDestroy classifies as an impersonation phishing page built to pass as a trusted service. Its presence on the MetaMask and SEAL blocklists points to cryptocurrency users and wallet holders as the intended audience. PhishDestroy first saw the domain on 2026-09-27. On 2026-10-19 the server was still responding, but the page content could not be loaded.
Impersonation sites like this borrow a familiar-looking name and interface, here "BingNC", so visitors believe they are dealing with a legitimate platform. Once trust is established, the victim is steered into entering login credentials, recovery details or personal information, or into depositing or sending crypto to the operators. Anything typed in or transferred goes straight to the scammers, and blockchain transfers cannot be reversed.
Four of 92 VirusTotal engines flagged the domain as of 2026-10-10: alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. That is a modest count, but the more telling signal comes from the crypto-specific side. MetaMask and SEAL, both focused on protecting wallet users, list the domain alongside PhishDestroy. The domain also appears in four AlienVault OTX threat pulses, so other researchers have tracked it independently.
The domain was registered on 2023-06-23 through Gname.com Pte. Ltd., more than three years before PhishDestroy detected it. That suggests it was held in reserve or reused rather than spun up for a single campaign. It resolves to a US-hosted server. Its TLS certificate is issued to "Internet Widgits Pty Ltd", the default placeholder of a self-generated certificate, not one from a recognised certificate authority, so a careful browser user would see a warning.
Do not return to the site or trust any service calling itself BingNC. If you entered a password there, change it wherever you reused it and turn on app-based 2FA. If you shared a seed phrase, move remaining funds to a new wallet immediately. If you connected a wallet, revoke any approvals granted during that session. Defenders should block the domain at DNS and proxy level and watch logs for earlier visits.
Last checked
a.share-dns.coma5.share-dns.comb.share-dns.netb5.share-dns.netLocation describes the IP network.
16512c1b365f659c18b9117ad5419ef6aff5a5caf5c0365bb946b264d44c89afSaved 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.
ht.bingnc.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of bingnc.com · checked Sep 27, 2026
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.
不明→live_content
content_served
不明→live_content
content_served
0→2
No threat flag
View source4/92 engine detections
View source4 community references
View sourcePD-20260927-3F8176
Page captured
View sourcebingnc.com
View source保存された類似ドメイン:79 件
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
bingnc.com
PD-20260927-3F8176 Recipient: abuse@ceranetworks.com Registrar: Gname.com Pte. Ltd. (Singapore) Policy Violations: Illegal Activities section forbids phishing, fraud, fake sites, malware distribution; registrar investigates and may suspend or delete domain Applicable Laws: Computer Misuse Act 1993 §§3+, Penal Code §§415–420 (cheating), Online Criminal Harms Act (OCHA)
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
bingnc.com)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.