Skip to security report
Domain security and threat intelligence
publicsale.well3.website favicon

publicsale.well3.website

“WELL3”

Registrar
arin
Resolved IP
2606:4700:3034::ac43:c909
Threat verdict Critical
Availability Content unavailable Content was unavailable in the latest observation Observed
Source: HTTP probe
Stored blocklist matches: 1 Brand impersonation: Discord
Mar 28, 2024 Discord CDN
API
This domain has been flagged as malicious
Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
URLScan
URLScan
Observed status
Content unavailable
PhishDestroy
DestroyList
Listed

Source evidence

5 sources

VirusTotal

checked — no detections recorded

Report

OTX

no community references

Report

CF Radar

provider verdict: safe

Report

URLScan capture

stored report

Stored URLScan capture preview
Report

Google Safe Browsing

Checked; no threat flag recorded

Report

Evidence Summary

Critical
URLScan
Stored capture

The domain publicsale.well3.website, impersonating Discord, is currently down. This site is associated with an Ice Phishing crypto drainer.

No security vendor has flagged publicsale.well3.website as malicious on VirusTotal, suggesting it is a fresh domain not yet processed by AV feeds. It is listed on 2 public blocklists and not flagged by Google Safe Browsing.

The domain is associated with ARIN (US) as its regional internet registry, and no specific registrar data is available. It resolved to the IPv6 address 2606:4700:3034::ac43:c909 and was first

Detection-evasion analysis

Cloaking and traffic-distribution check

Not observed No 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='publicsale.well3.website', port=80): Max retries exceeded with url: / (Caused by NewConnec

Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Waiting

Stored Capture · 2 captures

Page Title
WELL3
Impersonates
Discord

Domain details

Domain
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) arin US(US)
Registration (base domain)well3.website · Expires Dec 31, 2037
Time to First Unavailability 764 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.
Technical detailsProvenance & timestamps
First DetectedMar 28, 2024
DOM Analysisanalyzed Apr 23, 2026score 25/1001 brand signal
Submitted URLhttps://publicsale.well3.website/
ICANN OVERSIGHT Registration: well3.website

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For the registrable domain well3.website 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.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
2606:4700:3034::ac43:c909
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 1

  • 1

Location describes the IP network.

viewdns.info · 2606:4700:3034::ac43:c909rapiddns.io

Latest Classified Outcome 2026-10-12 20:20:57 UTC

Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Unknown Probe Inconclusive 20% 2026-10-13 01:10:51 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-06-13 22:21:12 UTC current episode first observed: 2026-09-30 16:14:55 UTC observed RIP window: 2026-06-13 22:21:12 UTC → 2026-09-30 16:14:55 UTC · 2,609.90h midpoint estimate ≈ 2026-08-07 07:18:03 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.
Report This Domain Submit evidence & help protect others

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.
  1. Cloudflare Radar Scan 2026-03-07 18:23:49 UTC
    Cloudflare Radar scan registered: View Radar report.

Threat Response Pipeline

Discovery
Analysis
Monitoring

11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
publicsale.well3.website detected and queued for full analysis
Mar 28, 2024
URLScan.io Capture
Stored URLScan report with capture artifacts
Mar 6, 2026
Cloudflare Radar Report
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.
Blocklist Detection
Found in 1 blocklist: ScamSniffer
Oct 13, 2026
Drainer Identified
Ice Phishing wallet drainer — impersonating Discord
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Mar 6, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 13, 2026
Cloudflare Radar Scan
Scanned with Cloudflare Radar; network analysis completed.
Mar 7, 2026
DestroyList Published
Mar 28, 2024
Content Observed Unavailable
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
May 1, 2026
Time to First Unavailability
18341 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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

Public Blocklist Status

Community intelligence

2 community reports

CategoryPHISHING

Automated report created by SEAL

Evidence & External Reports

Third-Party Detection — ChainAbuse
2 reports filed for publicsale.well3.website · category: Phishing · source checked
Flagged by SEAL on Mar 28, 2024 — automated submission, not a user testimony. Source: ChainAbuse (TRM Labs).
Deep Analysis

Were You Affected by This Site?

3 evidence signal groups linked 0 reports recorded Content unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If a wallet, seed phrase, or account was exposed, report the incident immediately. Revoke approvals and move remaining assets to a new wallet created on a trusted device.

Europol
Find the official reporting channel for your EU country
National police directory
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Guaranteed crypto recovery is a fraud indicator. Learn more about recovery fraud →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing

Recommendations & Advice for Victims

An estimated $51 billion flowed to illicit crypto wallets in 2024 (source). If you interacted with publicsale.well3.website — act now.

What should I do immediately?
Urgent
  • Revoke token approvals — use revoke.cash to remove access granted to malicious smart contracts
  • Move remaining funds to a brand-new wallet. The compromised wallet is no longer safe
  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines

According to the FBI, the most important details are transaction data:

  • Cryptocurrency addresses — scammer's wallet (e.g., 0x5856...35985)
  • Amount & crypto type — exact amount (e.g., 1.02345 ETH, 0.5 BTC, 500 USDT)
  • Transaction ID (hash) — the unique blockchain transaction identifier
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including publicsale.well3.website)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?
  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Chainabuse — flag scam wallets across exchanges & platforms
  • Your crypto exchange — notify its fraud team immediately; it may be able to preserve records or restrict funds held on its platform
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do crypto scams typically work?
  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Malicious approvals — "connect wallet" prompts that grant unlimited token spending to attackers
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Fake ads & airdrops — Google/social media ads and "free token" offers leading to wallet drainers
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
  • Use a hardware wallet (Ledger, Trezor). Never store large amounts in browser wallets
  • Bookmark official sites — never click links from emails, DMs, or ads
  • Read every approval — verify permissions before signing. Reject unlimited approvals
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/publicsale.well3.website"
  title="PhishDestroy threat report for publicsale.well3.website"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>