Analysis shows that vultex.network was registered on February 21, 2026 through PDR Ltd. d/b/a PublicDomainRegistry.com and is hosted behind Cloudflare infrastructure (ASN 13335). The domain resolves to IP address 104.21.76.38, which GeoIP maps to the United States. DNS resolution uses the Cloudflare nameservers brianna.ns.cloudflare.com and bradley.ns.cloudflare.com, and the site serves traffic over HTTP/3 with an HTTP 200 response. The TLS certificate is issued by Google Trust Services under the WE1 identifier, indicating a valid HTTPS configuration.
The landing page carries the title "Vultex: Donald Trump’s Leading Blockchain Crypto Casino" and explicitly promotes a cryptocurrency gambling service, matching the known "Gambler Scam" phishing kit. This content directly impersonates a crypto‑casino brand, leveraging the high‑profile name to lure victims into a fraudulent investment or betting scheme. The site’s visual and textual elements mirror legitimate gambling platforms, increasing its credibility for unsuspecting users.
Threat intelligence flags the domain as high‑risk. VirusTotal reports that 16 of 95 security vendors have marked the domain as malicious, and it appears on at least one external blocklist. The combined evidence—brand impersonation, use of a reputable TLS certificate, and detection by multiple security vendors—confirms a coordinated campaign targeting cryptocurrency gambling enthusiasts. The site remains active as of the report date, July 12, 2026.
Defenders should add vultex.network to network‑level blocklists and enforce DNS filtering to prevent resolution. Monitoring outbound connections to IP 104.21.76.38 can help detect compromised hosts attempting to reach the infrastructure. Security teams should also audit email and web traffic for similar brand‑impersonation patterns, especially those referencing high‑profile political figures combined with crypto‑gaming terminology, and educate end‑users about the specific lure used in this campaign.
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='vultex.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
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 DetectedFeb 26, 2026
DOM Analysisanalyzed Apr 23, 2026score 88/100
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:10:48 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-07-09 10:29:44 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-07-09 10:29:44 UTC → 2026-09-30 16:14:55 UTC · 1,997.75hmidpoint estimate ≈ 2026-08-20 01:22:19 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.
Technologies · 2 identified
Cloudflare
CDN
Web infrastructure and security company providing CDN, DDoS mitigation, and DNS services.
Google PageSpeed Insights — mobile performance audit of vultex.network· checked Mar 2, 2026
100
Good
Performance
FCP
0.77s
First Contentful Paint
LCP
1.82s
Largest Contentful Paint
CLS
0.019
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.77s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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
vultex.network 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.
Jul 21, 2026
Time to First Unavailability
3408 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 · vultex.network
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.
(IN)
