Skip to security report
Analytics Dashboard
Domain security report
app.veda.exchange favicon

app.veda.exchange

“Veda | Earn”

Threat verdict
CriticalDomain Appeal
Assessment sources

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

Availability Reachable · access restricted Reachable response; page content was not verified Observed · HTTP probe
Risk signals
VirusTotal detections: 16/89 Spamhaus DBL: DBL_PHISH Last known active
Sep 2, 2026 CDN
API
Registrar
Tucows
Resolved IP
104.21.11.134
Registered
Oct 25, 2025
2 sources
The capture source is temporarily unavailable.
1 / 2
Source
Primary capture
Collected · UTC
Open capture
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 16. Exercise extreme caution — do not enter credentials or personal information.

Additional indicators at a glance

Spamhaus DBL
DBL_PHISH
VirusTotal
VirusTotal
16 det.
URLScan
URLScan
Report ↗
TLS Certificate
Within stored validity dates
Google Trust Services · Hostname coverage not recorded
Age
12 mo
Observed status
Reachable · access restricted 403
PhishDestroy
DestroyList
Listed

Source evidence

8 · 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

16 / 89

Report
Interpretation & limits

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

Spamhaus DBL

DBL_PHISH

Interpretation & limits

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

OTX

no community references

Report
Interpretation & limits

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

CF Radar

provider verdict: clean

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.

Public blocklists

0 external matches

Details
Interpretation & limits

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

Evidence Summary

Critical
VirusTotal
16/89
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.

Assessment

app.veda.exchange returned HTTP status 403 on 2026-10-01, according to the recorded HTTP check. The same hostname was first observed on 2026-09-02, a date that also carries a PageSpeed performance score of 39.

Recorded Evidence

The PhishDestroy internal listing records this hostname, and the HTTP check on 2026-10-01 returned status 403. VirusTotal recorded 16 detections across 89 scanners on 2026-09-11. The IP address 104.21.11.134 is attributed to Cloudflare, Inc. in CA, and the PageSpeed check on 2026-09-02 returned a performance score of 39.

Interpretation

The PhishDestroy listing, the HTTP check, the VirusTotal scan and the PageSpeed measurement were captured on different dates, so their observations describe separate moments rather than one synchronized snapshot. Because the VirusTotal scan on 2026-09-11 and the HTTP check on 2026-10-01 are not contemporaneous, a reader cannot treat them as describing the same condition. The 403 response is a dated record, not a statement about current availability.

Recommended Actions

Retain the dated records for app.veda.exchange so later checks can be compared against the 2026-09-02 first observation and the 2026-10-01 HTTP result. When reviewing app.veda.exchange, avoid submitting sensitive information until the recorded status and listing are independently rechecked. Compare any subsequent observations with the existing dates before drawing conclusions.

Data coverage & collection

17 · datasets with records / 14 · 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
16 / 89 · engine detections
URLScan analysis
Automated verdict retained
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
0 · community references
External blocklists
0 · external matches
Cloudflare Radar
cleanCollection time not recorded
Spamhaus DBL
DBL_PHISH
Domain registration
Tucows Domains Inc.Collection time not recorded
Network & DNS
104.21.11.134 · 1 · nameserversCollection time not recorded
TLS certificate
Google Trust ServicesCollection time not recorded
Page captures
2 · retained captures
Observed indicators
1 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
39/100 · mobile performance
Availability history
17 · stored state changes
Source observation history
5 · stored source events
IP reputation
Network-level observations
Not recorded in this report 14

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

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

Observed indicators

0 wallet · 1 Telegram

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

Telegram
https://t.me/+GfI_iZQ6wsZlZWNhStored page reference

IoC extraction recorded 2026-09-03 04:00:10 UTC

Blocklist records

0 · external source matches

Public Blocklist Status

Domain, network & archive

Tucows Domains Inc. · 104.21.11.134 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
Observed indicators0 wallet · 1 Telegram — full values ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) Tucows CA(CA)
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for veda.exchange →
Registration (base domain)veda.exchange · Created Oct 25, 2025 (357d)
HTTP Status403 Forbidden
Elapsed Since First Report 23 days
What we count Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Reachable · access restricted.
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 DetectedSep 2, 2026
IoC Extractionscanned Sep 3, 20260 wallet · 1 Telegram IoC
Submitted URLhttps://app.veda.exchange/
Favicon Hash
ICANN OVERSIGHT Registration: veda.exchange

Accreditation and RAA context
Registrar accreditation and DNS abuse obligations

For the registrable domain veda.exchange 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.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
104.21.11.134
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 1
  • bethany.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services
Valid until
2026-11-14 00:00:00
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection source
PhishDestroy collector

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

viewdns.info · 104.21.11.134rapiddns.io

Latest Classified Outcome 2026-10-17 01:15:43 UTC

Primary outcome Provider block observed reason: Cloudflare anti-phishing block 95% confidence
Attribution Cloudflare mechanism: Phishing Interstitial source: Current Http Probe
Evidence layers Availability: Provider blocked Content: Provider blocked DNS: Resolved Registration: Unknown
Latest HTTP observation Provider block observed Cloudflare anti-phishing block Cloudflare Phishing Interstitial 95% provider marker verified 2026-10-17 01:15:43 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-09-25 01:43:28 UTC current episode first observed: 2026-10-01 01:55:57 UTC observed RIP window: 2026-09-25 01:43:28 UTC → 2026-10-01 01:55:57 UTC · 144.21h midpoint estimate ≈ 2026-09-28 01:49:42 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.
Technologies · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

16 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 8 detections
alphaMountain.ai
BitDefender
CRDF
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Kaspersky
Lionic
Netcraft
Seclookup
SOCRadar
Sophos
VIPRE
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of app.veda.exchange · checked Sep 2, 2026

39
Poor
Performance
FCP
1.77s
First Contentful Paint
LCP
11.76s
Largest Contentful Paint
CLS
0.097
Cumulative Layout Shift
TBT
1113ms
Total Blocking Time
SI
14.84s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
144.21
Estimate basis
Bounded by observations
Estimate precision
Low

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 yet scanned No crawler-versus-browser difference has been recorded yet

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan
Server header seen by scanner
cloudflare

Scanner note: cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial

Provider response during scan: cloudflare_phishing_interstitial

Title shown to the security scannerSuspected Phishing | Cloudflare
Title shown to a browser visitorVeda | Earn
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

Collection history, report status and investigation channels

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. Domain Status Transition 2026-09-25 10:10:55 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain state transitioned from alive to dead.
  2. VirusTotal Detections Update 2026-09-11 01:05:24 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 8 to 16. Added scanner alerts: BitDefender, Emsisoft, G-Data, Lionic, Netcraft, Seclookup, Sophos, Webroot.
  3. VirusTotal Detections Update 2026-09-03 22:22:35 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 4 to 8. Added scanner alerts: CRDF, ESET, Kaspersky, SOCRadar.
  4. VirusTotal Detections Update 2026-09-02 22:09:44 UTC
    Source: VirusTotal
    Event details
    VirusTotal scanner detections updated from 3 to 4. Added scanner alerts: Forcepoint ThreatSeeker.
  5. Threat First Observed 2026-09-02 17:01:42 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 104.21.11.134.
Stored observation history22

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

    blocked→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  3. Availability monitor · Recorded state

    blocked→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  5. Availability monitor · Recorded state

    blocked→Unknown

    probe_inconclusive

Earlier observations 17
  1. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  2. Availability monitor · Recorded state

    blocked→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  4. Availability monitor · Recorded state

    blocked→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  6. Availability monitor · Recorded state

    blocked→Unknown

    probe_inconclusive

  7. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  8. Availability monitor · Recorded state

    blocked→Unknown

    probe_inconclusive

  9. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  10. Availability monitor · Recorded state

    blocked→Unknown

    probe_inconclusive

  11. Availability monitor · Recorded state

    Unknown→blocked

    cloudflare_antiphishing · Cloudflare · phishing_interstitial

  12. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

  13. Availability monitor · Recorded state

    Reachable→Unavailable

  14. VirusTotal · Detection count

    8→16

  15. VirusTotal · Detection count

    4→8

  16. VirusTotal · Detection count

    3→4

  17. Availability monitor · First collection record

    Reachable

Threat Response Pipeline

Discovery
Analysis
Monitoring

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

Threat Ingested
app.veda.exchange detected and queued for full analysis
Sep 2, 2026
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
Sep 2, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Sep 2, 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.
VirusTotal
16/89 recorded on VirusTotal
Sep 11, 2026
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Sep 2, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 17, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response (HTTP 403); the cause was not independently established.
Sep 25, 2026
VT Detection +8
+8 new detections (8 → 16): BitDefender, Emsisoft, G-Data, Lionic +4
Sep 11, 2026
VT Detection +4
+4 new detections (4 → 8): CRDF, ESET, Kaspersky, SOCRadar
Sep 4, 2026
VT Detection +1
+1 new detection (3 → 4): Forcepoint ThreatSeeker
Sep 3, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Sep 2, 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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Related infrastructure

Shared hosting, registrar records and related domains

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 16 det. ChainPatrol URLQuery SSL Labs Hostname coverage not recorded CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked 0 stored notification records Reachable · access restricted

Listed domains receive at least one abuse report; this entry has no retained notification history.

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.

Immediate steps Find reporting contacts
Official reporting routes
PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 app.veda.exchange)
  • 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

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

About This Report: app.veda.exchange

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “Veda | Earn”.

VirusTotal detections for app.veda.exchange: 16 (2026-09-11 01:05:24 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.

submit an appeal or review the FAQ page.

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/app.veda.exchange"
  title="PhishDestroy threat report for app.veda.exchange"
  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>