Security engines reporting a detection: 3. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
This investigation documents the infrastructure associated with claim.succisinct.foundation, observed as a crypto drainer campaign. The site presented the page title “Claim Your Rewards | Succinct Foundation,” indicating an attempt to lure victims with a reward claim narrative. The domain was registered on August 20, 2025 through Web Commerce Communications Limited and currently shows no SSL certificate, suggesting the site was served over HTTP when active. DNS resolution points to the Cloudflare edge address 172.67.158.31, belonging to AS13335 Cloudflare, Inc., located in the United States. The domain is hosted on Cloudflare’s network, which provides anonymity for the underlying origin server and complicates direct takedown efforts.
Security telemetry marks the domain as offline at the time of analysis, and it appears on two independent blocklists, PhishDestroy and ScamSniffer. The Gridinsoft trust score is 0 out of 100, reinforcing its malicious classification. VirusTotal scans recorded detections by 2 of 95 antivirus engines, confirming that at least a subset of security products recognize the domain as malicious. The nameservers nora.ns.cloudflare.com and yew.ns.cloudflare.com are standard Cloudflare delegations, offering no additional attribution.
Evidence does not disclose the specific payload or wallet addresses used in the drainer operation, and the page content beyond the title has not been captured. Consequently, the full scope of the campaign, including victim targeting and financial loss, remains uncertain. Defenders should block the domain and its associated IP address at perimeter and endpoint layers, monitor for new subdomains under the same registrar, and consider the Cloudflare IP range as a potential vector for related activity. Continuous re‑scanning of the domain on VirusTotal and inclusion in internal threat‑intel feeds are recommended to capture any future re‑activation.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not observedNo cloaking was observed in the stored scan
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='claim.succisinct.foundation', port=80): Max retries exceeded with url: / (Caused by NewCon
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Registration (base domain)succisinct.foundation · Created Aug 20, 2025 —Expires Aug 20, 2026
Time to First Unavailability208 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
For the registrable domain succisinct.foundation behind this subdomain, 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 inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:32:39 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-15 22:17:52 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-15 22:17:52 UTC → 2026-09-30 16:14:55 UTC · 353.95hmidpoint estimate ≈ 2026-09-23 07:16:23 UTC · precision 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
Gridinsoft
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
claim.succisinct.foundation detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 30, 2026
Time to First Unavailability
4988 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
3 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · claim.succisinct.foundation
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
(MY)
