Lompat ke laporan keamanan
Keamanan domain dan intelijen ancaman
1wtoken.xyz favicon

1wtoken.xyz

Registrar
Registrar of Domain Na…
Resolved IP
104.21.51.177
Registered
13/10/2026
PhishDestroy assessment Kritis
First observed Oct 19, 2026 09:41 UTC · PhishDestroy
Deteksi Total Virus: 1/92 Domain muda: 7 berumur hari
OTX: 4 refs 19/10/2026 1 Report Sent CDN
API
Domain ini telah ditandai sebagai berbahaya
Mesin keamanan melaporkan deteksi: 1. Berhati-hatilah — jangan memasukkan kredensial atau informasi pribadi.
ABUSE NOTICE · 24H+ 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 abuse@reg.ru. The latest stored availability evidence still shows the domain reachable; 32 hours 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
32 hours
Reports sent
1
Latest case ID
PD-20261019-9A6602
Current status
Observed active at latest stored check
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Domain age
Reports sent
view timeline
Ringkasan laporan

Domain dalam daftar blokir: 1wtoken.xyz — Belum terverifikasi. Ringkasan bukti: VirusTotal 1/92 (Forcepoint ThreatSeeker); PhishDestroy score 91/100.…

Analisis terperinci PhishDestroy AI di bawah tetap berbahasa Inggris untuk menjaga catatan forensik asli.

Source evidenceVirusTotal 1 / 92 · OTX 4 references 6 sources

VirusTotal

1 / 92 engine detections

Buka laporan

Google Safe Browsing

No threat flag

Buka laporan

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Kritis
VirusTotal
1 / 92
OTX
4 community refs
Page captures
2

PhishDestroy threat report

Overview

1wtoken.xyz is a newly registered domain that has been placed on the PhishDestroy blocklist. The site was first observed by PhishDestroy on 2026-10-19 and remains alive, although its content was unreachable when last checked on the same day. No legitimate brand or service is clearly advertised, suggesting a malicious intent aimed at crypto users.

How the scam works

Although the exact page content could not be retrieved, the classification and typical behavior of similar crypto‑related threats indicate that the site likely tries to lure visitors into connecting a cryptocurrency wallet or entering private keys. Once a wallet is linked, attackers can request transaction approvals, resulting in unauthorized transfers and loss of funds.

Evidence

VirusTotal scanned the domain and recorded one detection out of 92 scanning engines, with Forcepoint ThreatSeeker flagging it as malicious. The domain appears in four OTX pulses and is listed on the PhishDestroy blocklist. No additional detections from Google Safe Browsing, urlscan.io, or Spamhaus were reported, indicating limited but notable awareness among security vendors.

Infrastructure

The domain was registered on 2026-10-13 through REG.RU LLC, giving it only a six‑day window before PhishDestroy first saw it. Hosting resolves to IP address 104.21.51.177, a network commonly used for fast content delivery. TLS is provided by Let’s Encrypt (issuer "Let’s Encrypt / YE1"), which does not imply abuse but shows the site uses a valid, automated certificate.

What to do

Anyone who visited the site, entered credentials, or connected a wallet should immediately change all related passwords, enable two‑factor authentication, and revoke any wallet approvals granted to unknown addresses. Monitor blockchain activity for unauthorized transfers. Defenders should block 1wtoken.xyz at the network perimeter, add it to internal threat feeds, and continue monitoring for related indicators.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Tangkapan tersimpan · 2 captures

Sertifikat TLS
Diterbitkan oleh Let's Encrypt / YE1 · stored validity ends in 82 days

Domain details

Domain
URLScan verdict Analisis selesai score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Reputasi Edge-IP tidak dikaitkan dengan domain ini.
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomaindrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Registrar of Domain Na… (PERSONAL DATA, CAN NOT BE PUBLICLY DISCLOSED ACCORDING TO APPLICABLE LAWS.)
Kontak penyalahgunaanswaghitech@gmail.com, abuse@reg.ru
PendaftaranDibuat 13/10/2026 (7d · Very New!) — Expires 13/10/2027
Detail teknisProvenance & timestamps
Pertama Kali Terdeteksi19/10/2026
DOM Analysisanalyzed 19/10/2026score 91/100
Submitted URLhttps://1wtoken.xyz/
Favicon Hash
ID kasus
ICANN OVERSIGHT

Akreditasi dan konteks RAA

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 Tidak ada yang dikirim secara otomatis.

Network & certificates

Stored technical evidence

Network & DNS

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

Reputasi Edge-IP tidak dikaitkan dengan domain ini.

Server nama 2

  • olof.ns.cloudflare.com
  • summer.ns.cloudflare.com

Location describes the IP network.

Sertifikat TLS

Issuer
Let's Encrypt / YE1
Valid from
2026-10-13 13:35:21
Valid until
2027-01-11 13:35:20
Validity
Within stored validity dates
Collection time
2026-10-19 10:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprintdc5253b083f39f6e956a33c16b029fad8eb33afa8abcda12445054239607f8f9

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-19 20:21:20 UTC

Primary outcome DNS tidak aktif reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Tidak diketahui Probe Inconclusive 20% 2026-10-19 23:02:21 UTC
RDAP registration Tidak diketahui
Observed timeline last reachable: 2026-10-19 11:04:21 UTC current episode first observed: 2026-10-19 20:21:20 UTC observed RIP window: 2026-10-19 11:04:21 UTC → 2026-10-19 20:21:20 UTC · 9.28h midpoint estimate ≈ 2026-10-19 15:42:50 UTC · precision medium · 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.
Teknologi · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Laporkan Domain Ini Kirimkan bukti & bantu lindungi orang lain

Analisis VirusTotal

1 / Vendor keamanan 92 menandai domain ini
View on VT
Last analyzed Previous stored snapshot: 1 detection
Forcepoint ThreatSeeker
Analisis Performa Situs

Google PageSpeed Insights — mobile performance audit of 1wtoken.xyz · checked Oct 19, 2026

74
Needs Work
Performance
FCP
0.77s
First Contentful Paint
LCP
2.57s
Largest Contentful Paint
CLS
0.003
Cumulative Layout Shift
TBT
1145ms
Total Blocking Time
SI
1.83s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 403
Requested URL: https://1wtoken.xyz/
Just a moment...
Respons
HTTP 403
HTML body
5.7 KB
Compressed
3.4 KB
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=UTF-8
CF-Mitigated: challenge
Server: cloudflare
Content-Encoding: gzip
Security headers present
Content-Security-PolicyX-Frame-OptionsX-Content-Type-OptionsReferrer-PolicyPermissions-PolicyCross-Origin-Opener-PolicyCross-Origin-Resource-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 23
Accept-Ch
Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model,
alt-svc
h3=":443"; ma=86400
Cf-Mitigated
challenge
CF-RAY
a4ced51ba8733a7c-FRA
Connection
close
Content-Encoding
gzip
Content-Security-Policy
default-src 'none'; script-src 'nonce-MSxUT3ODb9SonFxwQXc1CY' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blo
Content-Type
text/html; charset=UTF-8
Critical-Ch
Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model,
Cross-Origin-Embedder-Policy
require-corp
Cross-Origin-Opener-Policy
same-origin
Cross-Origin-Resource-Policy
same-origin
Date
Mon, 19 Oct 2026 09:42:23 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Origin-Agent-Cluster
?1
Permissions-Policy
accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=(),xr-spatial-tracking=*
Referrer-Policy
same-origin
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=OnVVcNpAO8Rb8yjEM0dot0xSNuQimCazzPVN7wXqhbNTtW4B3wo4Rm%2BqjOfbWZAXIqBCh9ZQFyVoSWVcfZeh1YHCCLGkBcZzqRLm3M5dxakToTPSfQrpmDyJ6ld7ew%3D%3D"}]}
Server
cloudflare
Server-Timing
chlray;desc="a4ced51ba8733a7c"
Transfer-Encoding
chunked
X-Content-Type-Options
nosniff
X-Frame-Options
SAMEORIGIN

Values retained by the collector; long values may be shortened during collection.

Registration & observation details8

Availability observations

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

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

Stored observation history3

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

    protected→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Tidak diketahui→protected

    cloudflare_challenge · Cloudflare · challenge

  3. Availability monitor · First collection record

    Dapat dijangkau

Recorded activity

6 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. AlienVault OTX

    4 community references

    View source
  3. VirusTotal

    1/92 engine detections

    View source
  4. Abuse report sent

    PD-20261019-9A6602

    abuse@reg.ru
  5. Added to PhishDestroy

    1wtoken.xyz

    View source
  6. URLScan

    Page captured

    View source

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

1wtoken.xyz

Bukti & Laporan Eksternal

Snapshot bukti yang dikirim
Sent: Ledger records: 1 Case ID: PD-20261019-9A6602 Recipient: abuse@reg.ru
PDF notice generated Notice text archived (324 chars)
Abuse notice text as sent to the provider
Registrar: REG.RU (Russia)
Policy Violations: Abuse policy + ICANN contractual obligations; phishing classified as bad-faith use in UDRP; domains may be suspended/removed
Applicable Laws: Criminal Code RF Art.159 (fraud), Art.272 (illegal access), Art.273 (malware creation), Art.274.1 (critical infrastructure interference)
Analisis Mendalam
Help & reporting

Apakah Anda Terpengaruh oleh Situs Ini?

6 evidence signal groups linked 1 stored notification records Belum terverifikasi
If credentials were compromised, report immediately. Do not engage with recovery scammers.

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.

Official reporting routes

Waspadalah terhadap penipu yang mengatasnamakan pemulihan! Penjahat dapat menghubungi korban lagi sambil berpura-pura menjadi penyelidik, pengacara, atau agen pemulihan. Jangan membayar biaya di muka atau membagikan kredensial. Pelajari lebih lanjut tentang penipuan dalam proses pemulihan →

Laporkan kepada Pihak Berwenang di Daerah Anda

Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.

Direktori 97 negara

Template-based draft · optional AI wording assistance requires separate consent

Draf yang dibantu AI — detail insiden diproses oleh penyedia AI · Tinjau dan kirimkan sendiri
After a phishing incident

Rekomendasi & Saran bagi Para Korban

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

Apa yang harus saya lakukan segera?

Mendesak

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

  • Ubah semua kata sandi — email, akun Exchange, apa pun yang menggunakan kata sandi yang sama
  • Aktifkan 2FA menggunakan aplikasi otentikator (bukan SMS). Nonaktifkan pemulihan berbasis SMS
  • Kartu pembeku jika Anda telah memasukkan detail perbankan di situs phishing tersebut

Informasi apa saja yang sebaiknya saya kumpulkan untuk laporan saya?

Pedoman FBI

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.
  • Tanggal dan waktu yang tepat — dari setiap transaksi dan kontak pertama dengan penipu
  • Tangkapan layar — situs web penipuan, pesan obrolan, email, transaksi dompet digital, media sosial
  • Semua URL & domain digunakan oleh penipu (termasuk 1wtoken.xyz)
  • Komunikasi — email, pesan teks, nomor telepon, dan nama pengguna yang digunakan oleh penipu tersebut

Meskipun kamu belum mengetahui semua detailnya — tetap saja ajukan laporan. Informasi yang tidak lengkap tetap dapat membantu penyelidikan.

Ke mana saya harus melaporkan penipuan ini?

  • FBI IC3 — Pusat Pengaduan Kejahatan Internet (Laporan tingkat federal AS)
  • Europol — Pelaporan kejahatan siber di Eropa (UE)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Polisi setempat — membuat catatan resmi, meskipun mereka tidak dapat bertindak segera

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?

  • Situs web palsu — salinan yang persis sama dengan situs asli, dengan domain yang sedikit diubah
  • Pemotongan babi — kepercayaan yang dibangun selama beberapa minggu melalui Telegram/WhatsApp/aplikasi kencan, lalu uangnya dicuri
  • Penipuan pemulihan — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • Penipuan yang didukung oleh kecerdasan buatan — deepfakes, serangan phishing otomatis, dan situs yang dihasilkan oleh kecerdasan buatan (AI) yang membuat penipuan semakin sulit dideteksi

Bagaimana cara saya melindungi diri di masa depan?

  • Tandai situs resmi — jangan pernah mengklik tautan dari email, pesan langsung (DM), atau iklan
  • Memverifikasi domain — periksa PhishDestroy Sebelum berinteraksi. Periksa HTTPS, ejaan, dan usia domain
  • "Terlalu bagus untuk jadi kenyataan" = penipuan — imbal hasil yang dijamin, dukungan dari selebriti, tenggat waktu yang mendesak

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

Tetap Terinformasi, Tetap Aman

Pantau ancaman secara langsung atau ajukan keberatan terhadap daftar ini jika Anda yakin ini merupakan false positive

Pemberitahuan Ancaman Real-Time Ajukan Banding Terhadap Iklan Ini
About this reportSources, observation dates and corrections

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Sematkan Laporan Ini

Bagikan informasi ancaman ini di situs web atau blog Anda

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