On July 23, 2026, the domain pharaoh.finance was observed hosting a brand‑impersonation campaign targeting Revolut. The site presented the page title “Pharaoh Exchange: Revolutionizing Cryptocurrency Trading,” suggesting a cryptocurrency‑focused façade, but no further content was captured before the host was taken offline. DNS resolution points to the IPv4 address 66.63.187.97, which belongs to AS36352 (HostPapa) located in the United States. The authoritative name servers are jeff.ns.cloudflare.com and hope.ns.cloudflare.com, indicating the use of Cloudflare’s DNS service. HTTP traffic was terminated over TLS with a Let’s Encrypt certificate (R12), confirming a valid but freely issued certificate.
The web server identified by banner analysis is Nginx. The domain appears on a single security blocklist and is actively blocked by PhishDestroy. VirusTotal analysis recorded 13 detections out of 95 scanning engines, reinforcing the malicious classification. AlienVault OTX references the domain in one threat‑intelligence pulse, and Gridinsoft assigned a trust score of 0 / 100, reflecting a high confidence of abuse. Registration information lists Web Commerce Communications Limited dba WebNic.cc as the registrar; no additional registrant details were disclosed.
Because the site is currently offline, direct observation of the phishing page content, credential‑capture mechanisms, or additional infrastructure cannot be confirmed. Analysts should monitor the associated IP address and name‑server pair for re‑use, and incorporate the domain into URL filtering and DNS block policies targeting Revolut‑related impersonation. Continuous re‑scanning with multi‑engine services is recommended to capture any future changes in detection scores. Coordination with the hosting provider (HostPapa) and Cloudflare may facilitate takedown or mitigation if the domain resurfaces.
DOM Analysisanalyzed 2026年10月20日score 10/1001 brand signal
Submitted URLhttps://pharaoh.finance/
Favicon Hash
ICANN OVERSIGHT
認定と RAA の背景
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-19 22:32:07 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-19 22:32:07 UTClast content: 2026-10-19 10:32:11 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
使用技術 · 1 identified
N
Nginx
Web serversReverse proxies
High-performance HTTP server and reverse proxy, known for stability and low resource usage.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
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.
(MY)
