Skip to security report
Domain security report
dexachainprotocolapp.support favicon

dexachainprotocolapp.support

“NexaChain - Decentralized Protocol (Educational Demo)”

Threat verdict
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 3/91 Spamhaus DBL: DBL_SPAM Stored blocklist matches: 3 URLQuery threat systems: 1 alert Scam type: Tech Support Scam
OTX: 23 refs Jan 27, 2026 1 Report Sent
API
Registrar
NameSilo
Resolved IP
50.30.32.108
3 sources
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 3. Public blocklists reporting a match: 3. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is bashirtijjani550@gmail.com. The latest stored availability evidence still shows the domain reachable; 8 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.

Elapsed since first report
8 months
Reports sent
1
Latest case ID
PD-20260127-7344D4
Current status
HTTP 302 at latest stored check

Additional indicators at a glance

Spamhaus DBL
DBL_SPAM
VirusTotal
VirusTotal
3 det.
URLQuery
URLQuery
1 threat alert
OTX references
URLScan
URLScan
TLS Certificate
Within stored validity dates
Let's Encrypt · Hostname coverage not recorded
Observed status
Last known active 302
PhishDestroy
DestroyList
Listed
Reports Sent
1

Source evidence

9 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

3 / 91

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

URLQuery

1 threat-system alert

Report
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

Public blocklists

3 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Spamhaus DBL

DBL_SPAM

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

23 community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: suspicious

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

stored report

View stored capture ↗
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Analysis completed

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Network Security Intelligence Registrar context
Registrar context NameSilo
Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
Review source investigation
Threat Detection Systems 1 alert
Detection System Indicator Verdict Alert
Quad9 DNS dexachainprotocolapp.support malicious Sinkholed

Evidence Summary

Critical
VirusTotal
3/91
OTX
23 community refs
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

The domain dexachainprotocolapp.support is assessed as having an elevated risk level and is categorized as a generic phishing threat. This domain poses a significant risk of credential theft and financial fraud through deceptive web content.

Analysis indicates that the domain is flagged by 6 out of 95 security vendors on VirusTotal, suggesting a moderate level of consensus regarding its malicious nature. The domain is registered through NameSilo, LLC and resolves to the IP address 50.30.32.108. It was created on February 21, 2026, which is a relatively recent registration, often indicative of a newly set up phishing operation. The site's title, 'NexaChain - Decentralized Protocol (Educational Demo)', may be an attempt to appear legitimate and attract users interested in blockchain technology. Additionally, the domain appears on four security blocklists, including Codeesura, Polkadot, PhishDestroy, and Enkrypt, and has a Gridinsoft trust score of 0/100, the lowest possible rating. The use of an SSL certificate from Let's Encrypt does not guarantee security, as phishing sites can also obtain valid certificates.

To mitigate the risks associated with this domain, users should avoid clicking on any links or entering personal information on the site. Network administrators are advised to block access to 50.30.32.108 and the domain itself to prevent potential exposure. Regularly updating security software and educating users about the signs of phishing attacks can further enhance protection against similar threats.

Data coverage & collection

22 · datasets with records / 9 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
3 / 91 · engine detections
URLScan analysis
Automated verdict retained
URLQuery
1 · recorded detections / alerts
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
23 · community references
External blocklists
3 · external matches
Cloudflare Radar
suspiciousCollection time not recorded
Spamhaus DBL
DBL_SPAM
Domain registration
NameSilo, LLCCollection time not recorded
Network & DNS
50.30.32.108 · 1 · nameserversCollection time not recorded
TLS certificate
Let's Encrypt
Page captures
3 · retained captures
Page analysis
0 · automated brand labels
Observed indicators
1 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
99/100 · mobile performance
Response records
1 · outgoing report records
Availability history
30 · stored state changes
Source observation history
2 · stored source events
Community reports
Aggregate report counts and dates
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 9

These checks have no retained result. This does not mean they passed or that a scan is running.

  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • HTML archives
  • Site configuration files
  • Recorded subdomains
  • Lookalike relationships
  • Chainabuse records
Download the dated observations and supporting metadata.
Extracted from stored page analysis

Observed indicators

1 wallet · 0 Telegram

Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.

ETH
0x742d35Cc6634C0532925a3bCD48886945F266E8DFormat validated · Domain analysis

IoC extraction recorded 2026-07-29 02:38:18 UTC

Blocklist records

3 · external source matches

Public Blocklist Status

Domain, network & archive

NameSilo, LLC · 50.30.32.108 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 0 reports checked Oct 14, 2026
OTX tags 2026-02activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
RegistrationExpires Jan 19, 2027
HTTP Status302 Found (Temporary)
Technical detailsProvenance & timestamps
First DetectedJan 27, 2026
DOM Analysisanalyzed Jul 9, 2026score 88/100
IoC Extractionscanned Jul 29, 20261 wallet · 0 Telegram IoC
Submitted URLhttp://dexachainprotocolapp.support/
Favicon Hash
Case ID
ICANN OVERSIGHT

Accreditation and RAA context

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.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
50.30.32.108
Network ASN
AS30083
Organization
velia.net
Observed location
St. Louis, US
Server header
ESF
Nameservers 1
  • dns3.afeeshost.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt
Valid from
2026-05-21 20:33:32
Valid until
2026-08-19 20:33:31
Hostname coverage
Hostname coverage not recorded
Validity
Stored certificate expired
Collection time
2026-10-09 19:02:23 UTC
Collection source
PhishDestroy collector
Certificate fingerprintac27b9fc2c1a80a424af882ead8629ff93d3ef0290110103ebba9222a0b9b20d

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-17 22:17:25 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-17 22:17:25 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-17 22:17:25 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.
Technologies · 1 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

3 / 91 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 4 detections
alphaMountain.ai
Fortinet
Gridinsoft

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of dexachainprotocolapp.support · checked Jun 27, 2026

99
Good
Performance
FCP
1.71s
First Contentful Paint
LCP
1.71s
Largest Contentful Paint
CLS
0.01
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.11s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking suspected: scanner and visitor titles differ

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: redirect: raw=redirect_302; http=302; via=https_proxy; location=https://dexachainprotocolapp.support/cgi-sys/suspendedpage.cgi

Title shown to the security scanner302 Found
Title shown to a browser visitorNexaChain - Decentralized Protocol (Educational Demo)
Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
Saved result
Keitaro TDS

Timeline & response

1 · outbound report records

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. VirusTotal Detections Update 2026-06-26 23:59:09 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 4 to 6. Added scanner alerts: CRDF, Chong Lua Dao, CyRadar, alphaMountain.ai. Resolved alerts: Fortinet, Seclookup.
  2. VirusTotal Detections Update 2026-03-11 02:42:37 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 4 to 6. Added scanner alerts: CyRadar, alphaMountain.ai.
Stored observation history32

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  2. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  4. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

Earlier observations 27
  1. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  3. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  5. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  6. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  7. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  8. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  9. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  10. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  11. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  12. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  13. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  14. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  15. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  16. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  17. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  18. Availability monitor · Recorded state

    redirected→Unknown

    stale_current_evidence

  19. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  20. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  21. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  22. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  23. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  24. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  25. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

  26. VirusTotal · Detection count

    4→6

  27. VirusTotal · Detection count

    4→6

Threat Response Pipeline

Discovery
Analysis
Notifications
Monitoring

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

Threat Ingested
dexachainprotocolapp.support detected and queued for full analysis
Jan 27, 2026
Spamhaus DBL
Spamhaus DBL recorded DBL_SPAM
Oct 13, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Mar 26, 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.
Web Archive
Preserved in Wayback Machine — historical evidence archived
Mar 14, 2026
VirusTotal
3/91 recorded on VirusTotal
Sep 29, 2026
Blocklist Detection
Found in 3 blocklists: Polkadot, Enkrypt, Codeesura
Oct 18, 2026
OTX Community References
23 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Sep 28, 2026
Registrar Context: NameSilo
Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Mar 26, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 18, 2026
VT Detection +2
+2 new detections (4 → 6): CRDF, Chong Lua Dao, CyRadar, alphaMountain.ai
Jun 27, 2026
VT Detection +2
+2 new detections (4 → 6): CyRadar, alphaMountain.ai
Mar 11, 2026
Sent Report Recorded
Stored outgoing record associated with registrar NameSilo, LLC, 1 abuse contact
bashirtijjani550@gmail.com
Jan 27, 2026
DestroyList Published
Jan 27, 2026
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this 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.

Related infrastructure

Shared hosting, registrar records and related domains

Community records

Retained community reports and observations

Community reports

Reported by 1 community member, first seen Jan 27, 2026

Stored reports
1
Unique reported URLs
1
Accepted1

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260127-7344D4 Recipient: bashirtijjani550@gmail.com
PDF notice generated Notice text archived (1,210 chars)
Abuse notice text as sent to the provider
Policy Violations:
Acceptable Use Policy (AUP): The domain dexachainprotocolapp.support is engaged in phishing activities, which directly contravenes your AUP prohibiting illegal activities and fraud.
Terms of Service (TOS): The use of this domain for deceptive practices constitutes a violation of your TOS, which reserves the right to suspend or terminate services for such infractions.
Applicable Laws (Unknown):
Computer Fraud and Abuse Act (CFAA): This U.S. law prohibits unauthorized access to computers and networks, which is relevant as phishing schemes often involve unauthorized data access.
Wire Fraud Statute (18 U.S.C. § 1343): This law criminalizes schemes to defraud individuals or entities using electronic communications, applicable to the fraudulent activities associated with this domain.
Anti-Phishing Consumer Protection Act: This legislation aims to combat phishing by imposing penalties on those who engage in deceptive practices online.
Regulatory Note: Failure to take immediate action against this domain may expose your organization to legal liability and regulatory scrutiny. Compliance with your AUP and TOS is essential to mitigate risks associated with hosting malicious content.
Deep Analysis

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

6 evidence signal groups linked 1 stored notification records Last known active
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.

Official reporting routes
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 →
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
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • 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

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.
  • 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 dexachainprotocolapp.support)
  • 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)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • 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 phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • 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
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

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
Read the evidence in context

About This Report: dexachainprotocolapp.support

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “NexaChain - Decentralized Protocol (Educational Demo)”.

VirusTotal detections for dexachainprotocolapp.support: 3 (2026-09-29 02:16:29 UTC).

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/dexachainprotocolapp.support"
  title="PhishDestroy threat report for dexachainprotocolapp.support"
  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>