VirusTotal
2 / 89
“Home”
Security analysis of usdtex.network covers observed phishing indicators, infrastructure evidence, current status, and defensive guidance.
The detailed PhishDestroy AI analysis below remains in English to preserve the original forensic record.
Analysis of usdtex.network indicates that the domain was registered on 21 February 2026 through NameCheap, Inc. and is currently resolved to the Cloudflare‑owned address 172.67.187.229, which belongs to AS13335 (Cloudflare, Inc.) and is located in the United States. The site presents a single page whose title is “Home”; no further content has been captured because the service is listed as offline in the intelligence feed. The hosting environment is identified as Cloudflare with additional client‑side technologies Inertia.js, Cloudflare Browser Insights and HTTP/3, suggesting a modern web stack but providing no indication of malicious payloads. Reputation signals are strongly negative.
The domain appears on one public phishing blocklist, PhishDestroy, and received a Gridinsoft trust score of 0 out of 100. On VirusTotal, two of ninety‑three scanning engines flagged the domain, confirming the presence of suspicious activity. The SSL certificate is issued by Google Trust Services under the WE1 root, which is typical for Cloudflare‑proxied sites and does not mitigate the observed risk. Nameservers roan.ns.cloudflare.com and bristol.ns.cloudflare.com further confirm that the domain is fully proxied through Cloudflare’s DNS service.
Given the combination of an active blocklist entry, a zero trust score, and multiple vendor detections, the domain should be treated as a confirmed phishing infrastructure. Defenders should block outbound connections to 172.67.187.229, add usdtex.network to URL filtering and email security policies, and monitor for any future DNS changes or new sub‑domains that may be activated. Because the site is presently offline, continuous observation is advised to detect re‑appearance or changes in hosting configuration. No additional intelligence regarding the specific phishing campaign, targeted brand, or payload is available at this time.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/layla_supportStored page referenceIoC extraction recorded 2026-07-29 02:33:06 UTC
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: timeout: raw=timeout; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='usdtex.network', port=80): Read timed out. (read timeout=7)
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.
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.
Edge-IP reputation is not attributed to this domain.
bristol.ns.cloudflare.comLocation describes the IP network.
53e4d7562d4a21c92cc83e7b7cbbc6732c755b8c4350336f69d0b0ec661c86bbSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of usdtex.network · checked Mar 2, 2026
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
Reported by 1 community member, first seen Feb 19, 2026
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive