VirusTotal
9 / 89 engine detections
Buka laporan“404 Not Found”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@namecheap.com.
The latest stored availability evidence still shows the domain reachable; 7 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.
Phishing: upload-txt.website — Terakhir diketahui aktif (HTTP 200). Ringkasan bukti: VirusTotal 9/89 (alphaMountain.ai, BitDefender, ESET, Fortinet, G-Data)…
Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.
9 / 89 engine detections
Buka laporanchecked — no detections recorded
Buka laporanchecked — no match recorded
24 community references
Buka laporanprovider verdict: clean
Buka laporan14 diperiksa — tidak ada blokir
No threat flag
Buka laporanPage capture
Buka laporanResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
The domain upload-txt.website is classified as high-risk active generic phishing infrastructure. It registers in 24 AlienVault OTX pulses and appears on 2 security blocklists, with registration completed via NameCheap, Inc. on January 14, 2026. Gridinsoft assigns a trust score of 0/100 while VirusTotal shows 14 out of 95 vendors flagging the domain. The threat type is recorded as generic_phishing and the status remains active on the report date of July 12, 2026.
Infrastructure analysis reveals the domain resolves to IP 172.67.164.119. It employs an SSL certificate issued by Let's Encrypt and supports technologies PHP, Cloudflare, and HTTP/3. Specific blocklist entries include PhishDestroy and BLP-Malware. The page title returned is 404 Not Found, yet the domain continues to appear in threat feeds without indication of removal.
Uncertainty centers on the exact content currently delivered because the observed title suggests either a configuration change or partial remediation. No brand or kit details are present in the available data, and the original purpose cannot be confirmed solely from the title. The creation date in 2026 aligns with normal registration timelines and does not indicate anomaly.
Defenders should add both the domain and resolving IP 172.67.164.119 to internal blocklists, review network logs for connections to this address, and monitor for related NameCheap registrations exhibiting similar detection patterns. Ongoing tracking of the listed blocklist entries and OTX pulses is advised to maintain coverage while the domain retains active status.
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.
Reputasi Edge-IP tidak dikaitkan dengan domain ini.
guy.ns.cloudflare.comliberty.ns.cloudflare.comLocation describes the IP network.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
upload-txt.website
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
Tidak diketahui→live_content
content_served
15→14
24 community references
View source9/89 engine detections
View sourceNo threat flag
View sourcePage captured
View sourceupload-txt.website
View sourcePD-20260317-35ABE1
Dilaporkan oleh 1 anggota komunitas; pertama terlihat 17/03/2026
PD-20260317-35ABE1 Recipient: abuse@namecheap.com Registrar: Namecheap Inc (United States) Policy Violations: Domain Registration Agreement prohibits hacking, misuse of domain to conduct attacks, scam and fraudulent activities; AUP allows immediate suspension Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
Jika Anda memasukkan kredensial akun, informasi pribadi atau pembayaran, atau mengunduh file dari domain ini, segera ambil tindakan. Di bawah ini adalah sumber daya untuk membantu Anda melaporkan insiden tersebut dan melindungi diri Anda sendiri.
Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
upload-txt.website)Meskipun kamu belum mengetahui semua detailnya — tetap saja ajukan laporan. Informasi yang tidak lengkap tetap dapat membantu penyelidikan.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Analisis ancaman menggunakan daftar blokir yang disimpan, WHOIS, DNS, dan bukti pemindaian publik
Pindai SekarangLaporkan domain yang mencurigakan ke basis data ancaman kami — lindungi komunitas
LaporanLaporan phishing terbaru dan perubahan ketersediaan yang diamati
PantauPantau ancaman secara langsung atau ajukan keberatan terhadap daftar ini jika Anda yakin ini merupakan false positive
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.