VirusTotal
12 / 91 engine detections
打开报告“Pharaoh Exchange”
The sent-report ledger records the first outgoing report at .
The recorded recipient is compliance@tucows.com.
The latest stored availability evidence still shows the domain reachable; 3 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.
钓鱼: pharoah.exchange — 可达 · 访问受限 (HTTP 403). 证据摘要: VirusTotal 12/91 (alphaMountain.ai, BitDefender, ESET, Forcepoint ThreatSeeker, Fortinet); Spamhaus…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
12 / 91 engine detections
打开报告DBL_PHISH
6 community references
打开报告provider verdict: clean
打开报告14 已检查 — 未发现拦截
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
pharoah.exchange has been identified as an active generic phishing domain and poses a high risk to users. The site leverages the page title "Pharaoh Exchange" and currently remains operational. There are no direct indicators of impersonation of a specific financial platform based on the available intelligence, but the generic nature of the phishing tactics represents broad targeting potential.
Technical analysis reveals that this domain is flagged by 3 of 95 security vendors according to VirusTotal. pharoah.exchange was registered on June 10, 2026 through Tucows Domains Inc. The domain resolves to IP address 104.26.2.251 and employs an SSL certificate issued by Google Trust Services. The limited detection rate suggests either recent deployment or use of evasion techniques to bypass automated security filters.
Given the ongoing active status and concrete detection by multiple vendors, users and organizations should block any communication with pharoah.exchange at the network perimeter. Security teams are advised to update threat intelligence feeds and monitor for any interactions with this domain, as further indicators or campaign escalations may emerge.
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.
Edge-IP 声誉不属于此域。
javier.ns.cloudflare.comsunny.ns.cloudflare.comLocation describes the IP network.
e3d668ab878683b743cdebd445df6f1ceab2d4b43724bfd9148ab264b1c72182Saved 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 pharoah.exchange · checked Jul 1, 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.
cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
pharoah.exchange
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
未知→blocked
cloudflare_antiphishing · Cloudflare · phishing_interstitial
可访问→不可用
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
6 community references
View source12/91 engine detections
View sourcePage captured
View sourceNo threat flag
View sourcePD-20260701-6D60A7
pharoah.exchange
View source1 条社区报告
类别PHISHING
Typosquatting attack Malicious phishing domain: https://pharoah.exchange/ Impersonating https://pharaoh.exchange/ and https://www.phar.gg Actively scamming users. An example of user funds being stolen is linked.
“Typosquatting attack Malicious phishing domain: https://pharoah.exchange/ Impersonating https://pharaoh.exchange/ and https://www.phar.gg Actively scamming users. An example of user funds being stolen is linked.”
PD-20260701-6D60A7 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 ↗
pharoah.exchange)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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
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.