VirusTotal
5 / 91 engine detections
レポートを開く“Home - Safepal”
SafePalなりすまし: safepal.business — コンテンツが利用できません. 証拠の概要: VirusTotal 5/91 (alphaMountain.ai, CRDF, Fortinet, Gridinsoft, SOCRadar); URLQuery 1 alert; Spamhaus…
元のフォレンジック記録を保持するため、下の PhishDestroy AI 詳細分析は英語のままです。
5 / 91 engine detections
レポートを開く1 threat-system alert
レポートを開くDBL_PHISH
1 community reference
レポートを開く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 |
|---|---|---|---|
| Hagezi Threat Feed | safepal.business |
malicious | Sinkholed |
PhishDestroy threat report
The domain safepal.business was registered on 31 May 2026 through Tucows Domains Inc. and is currently marked as active. Its authoritative nameservers are ns1.metaquotes.business and ns2.metaquotes.business, which resolve the domain to the IPv4 address 91.92.241.159. Multiple security products have flagged the domain: PhishDestroy, MetaMask, and SEAL list it as blocked, and three of ninety‑one VirusTotal scanners have returned a positive detection.
The domain also appears on three external blocklists, reinforcing its reputation as a malicious resource. No public SSL certificate information, HTTP status code, or page title has been published in the available intelligence, leaving the exact content of the hosted site unverified. The lack of visible site metadata means that the specific phishing campaign tactics cannot be confirmed, but the combination of recent registration, dedicated meta‑quotes nameservers, and consistent blocklist presence aligns with typical infrastructure used for credential‑stealing operations.
Defenders should add safepal.business to DNS and proxy block policies, monitor traffic to 91.92.241.159 for anomalous connections, and consider sharing the indicator with threat‑intel platforms. Ongoing observation of the domain’s resolution and any future VirusTotal or sandbox analyses will be required to refine the risk posture.
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.
ns1.metaquotes.businessns2.metaquotes.businessLocation describes the IP network.
918c7e837c9394528d25374f12c531037849ff9de3a9ff9201526ec54112c172Saved 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 safepal.business · checked Jul 26, 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.
不明→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
到達可能→利用不可
到達可能
5/91 engine detections
View sourcePD-20260726-233AD9
1 community references
View sourceNo threat flag
View sourcesafepal.business
View sourcePage captured
View sourceコミュニティ報告:1 件
カテゴリPHISHING
safepal.business compliance@tucows.com domainabuse@tucows.com abuse@v-sys.org abuse@identity.digital security@safepal.io support@safepal.io reportphishing@apwg.org report@openphish.com https://identity.digital/policies/report-abuse https://safepalsupport.zendesk.com/hc/en-us/requ
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
safepal.business
“safepal.business compliance@tucows.com domainabuse@tucows.com abuse@v-sys.org abuse@identity.digital security@safepal.io support@safepal.io reportphishing@apwg.org report@openphish.com https://identity.digital/policies/report-abuse https://safepalsupport.zendesk.com/hc/en-us/requests/new https://safebrowsing.google.com/safebrowsing/report_phish/ https://www.microsoft.com/en-us/wdsi/support/report-unsafe-site-guest https://msrc.microsoft.com/report/abuse?ThreatType=URL&IncidentType=Phishing https”
PD-20260726-233AD9 Recipient: compliance@tucows.com Registrar: Tucows Domains Inc (Canada) Policy Violations: Participates in DNS Abuse Framework; explicitly recognizes phishing, malware, botnets, pharming, spam-as-vector as abuse requiring registrar action Applicable Laws: Criminal Code §342.1 (unauthorized access), §380 (fraud)
アカウント資格情報、個人情報、支払い情報を入力した場合、またはこのドメインからファイルをダウンロードした場合は、すぐに対処してください。インシデントを報告し、自分自身を守るのに役立つリソースを以下に示します。
サイバー犯罪の公式連絡先 または 苦情草稿を作成する → を取得するには、国を選択してください。
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 ↗
safepal.business)たとえすべての詳細がわかっていなくても―― とにかく報告を提出する. 不完全な情報であっても、捜査には役立つ。
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.