On 12 July 2026, the domain sceptre.finance was observed hosting a brand‑impersonation site that advertises “Sceptre Liquid Staking | Stake on Flare and Partisia”. The domain resolves to the Cloudflare edge address 172.67.141.27, which is associated with ASN 13335 (Cloudflare, Inc.) and is geolocated to the United States. Registration details show the domain is provisioned through Cloudflare, Inc. and uses the Cloudflare nameservers courtney.ns.cloudflare.com and tony.ns.cloudflare.com. HTTP requests return a 403 status code, and the site does not present a valid SSL certificate. Threat intelligence indicates the domain appears in a single AlienVault OTX pulse and is listed on two security blocklists (ScamSniffer and PhishDestroy). VirusTotal analysis recorded detections by 2 of 95 scanned vendors, and Gridinsoft assigned a trust score of 0 / 100, reinforcing the malicious assessment. The reported scam type is a crypto‑related scam, although the exact malicious payload or credential‑harvesting mechanism has not been publicly disclosed. Current uncertainties include the absence of a publicly available page capture, which prevents verification of any credential‑collection forms or malicious scripts, and the lack of additional infrastructure indicators beyond the Cloudflare front‑end. Defenders should block the domain at network perimeters, update DNS filtering policies to include the two identified blocklists, and monitor for connections to the IP address 172.67.141.27. Continuous re‑evaluation is advised should further detections appear in additional sandboxes or threat feeds.
DOM Analysisanalyzed 2026年3月24日score 15/1006 brand signals
IoC Extractionscanned 2026年7月29日0 wallet · 1 Telegram IoC
Submitted URLhttps://sceptre.finance/
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.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-21 01:11:13 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-07-19 22:23:00 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-07-19 22:23:00 UTC → 2026-09-30 16:14:55 UTC · 1,745.87hmidpoint estimate ≈ 2026-08-25 07:18:57 UTC · precision very low · basis bounded
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.
Last analyzed Previous stored snapshot: 2 detections
alphaMountain.ai
Chong Lua Dao
CRDF
Gridinsoft
Registration & observation details8
Availability observations
Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
1745.87
Estimate basis
Bounded by observations
Estimate precision
very_low
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='sceptre.finance', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
sceptre.finance
Stored observation history12
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
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.
(US)
