VirusTotal
0 / 92 engine detections
レポートを開く“Trust”
ブロックリスト掲載ドメイン: valtqor.com — 未検証. 証拠の概要: VirusTotal 0/92; URLScan capture; 2 external blocklist matches (MetaMask, SEAL); PhishDestroy score 66/100. レジストラ…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
0 / 92 engine detections
レポートを開くno community references
レポートを開くScan report
レポートを開くNo threat flag
レポートを開くPage capture
レポートを開くResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
PhishDestroy has added valtqor.com to its internal blocklist as a suspicious domain. The recorded page title is “Trust”. The domain was first seen by PhishDestroy on 2026-10-20.
The current listing does not confirm any particular malicious technique. Suspicious domains may be used for phishing, fraud, or other abuse, but no specific behavior was observed on this site. The title “Trust” alone does not prove legitimacy or deception.
VirusTotal scanned the domain on 2026-10-20 and reported 0 detections out of 92 engines. Google Safe Browsing checked on the same date and did not flag the site. External blocklists MetaMask and SEAL listed the domain, giving a count of 2 external hits on 2026-10-20. PhishDestroy’s internal blocklist also marks the domain as suspicious as of 2026-10-20. OTX showed 0 pulses on 2026-10-20.
The domain was registered on 2026-10-04 through NameSilo, LLC. The recorded IP address for the site is 172.86.82.148. No further network or hosting details are available.
If you entered any credentials on valtqor.com, change those passwords and monitor the associated accounts for unexpected activity. Security teams should add a rule to block traffic to the exact domain valtqor.com. Continue to monitor the domain for any change in behavior.
Last checked
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://valtqor.com/https://valtqor.com/Server: nginx/1.24.0 (Ubuntu)Content-Type: text/htmlContent-Encoding: gzipkeep-alivegziptext/htmlTue, 20 Oct 2026 19:46:20 GMTW/"6ad63265-23e"Mon, 19 Oct 2026 15:08:21 GMTnginx/1.24.0 (Ubuntu)chunkedValues retained by the collector; long values may be shortened during collection.
No threat flag
View source0/92 engine detections
View sourcevaltqor.com
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
valtqor.com
Listed 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 ↗
valtqor.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.