The domain jtx.waitlists.network returned HTTP status 403 on 2026-10-01, according to the recorded HTTP check. The same source set also notes a first observation date of 2026-08-10, roughly seven weeks earlier.
Recorded Evidence
The PhishDestroy internal listing for jtx.waitlists.network was recorded as true, and the HTTP check on 2026-10-01 returned status 403. A VirusTotal scan on 2026-08-20 recorded 14 detections across 91 scanners. The SSL certificate, scanned on 2026-08-11, was issued by Google Trust Services / WE1. A PageSpeed check on 2026-08-11 recorded a performance score of 100.
Interpretation
The PhishDestroy listing, the HTTP check, the VirusTotal scan and the SSL scan were captured on different dates, so they describe separate moments rather than one continuous state. Because the VirusTotal and SSL observations predate the HTTP check, a reader cannot treat them as simultaneous with the later response. The PageSpeed score reflects a single 2026-08-11 measurement and does not describe how the page behaved on other dates.
Recommended Actions
Retain the dated records for jtx.waitlists.network, including the PhishDestroy listing, the 2026-10-01 HTTP result and the 2026-08-20 VirusTotal figures, so later comparisons rest on the same source set. When reviewing the domain again, compare new observations against these exact dates rather than assuming the earlier values still apply. Avoid submitting passwords, payment details or other sensitive information while examining the domain.
집계 기준
Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: 연결 가능 · 액세스가 제한됨.
각 보고서에 포함된 내용
저장된 발신 보고서 기록은 공급업체 평가, 등록 데이터, 호스팅 세부 정보, 분류 또는 스크린샷과 같이 당시 사용 가능한 증거를 참조할 수 있습니다. 이 페이지는 전달된 정확한 페이로드, 수신, 확인 또는 수신자의 작업을 추론하지 않습니다.
기술 세부 정보Provenance & timestamps
최초 발견2026년 8월 10일
ICANN OVERSIGHTRegistration: waitlists.network
인증 및 RAA 상황
Registrar accreditation and DNS abuse obligations
For the registrable domain waitlists.network 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.
Certificate fingerprint938e2dba6f8c6cdc5a265aaa4a4997ff0be0714176660f645b0655a5edf768acCertificate names · 1 SANs
waitlists.network
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Observed timelinelast reachable: 2026-09-15 22:18:00 UTCcurrent episode first observed: 2026-10-01 01:43:41 UTCobserved RIP window: 2026-09-15 22:18:00 UTC → 2026-10-01 01:43:41 UTC · 363.43hmidpoint estimate ≈ 2026-09-23 12:00:50 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.
기술 · 4 identified
P
PHP
Programming languages
PHP is a general-purpose scripting language used for web development.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Er is een ongeautoriseerde SPL‑tokentransfer uitgevoerd vanaf mijn wallet naar een onbekend adres. De transactie werd ondertekend via mijn multisig‑authority zonder mijn toestemming. Ik vermoed dat mijn wallet of multisig‑configuratie is misbruikt door een scammer of een schadeli
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
1 report filed for jtx.waitlists.network (1 written by a person) · category: Phishing · source checked
“Er is een ongeautoriseerde SPL‑tokentransfer uitgevoerd vanaf mijn wallet naar een onbekend adres. De transactie werd ondertekend via mijn multisig‑authority zonder mijn toestemming. Ik vermoed dat mijn wallet of multisig‑configuratie is misbruikt door een scammer of een schadelijke dApp.”
— reported by Anonymous on Jul 12, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
Template-based draft · optional AI wording assistance requires separate consent
AI 지원 초안 - 사고 세부정보는 AI 제공업체에서 처리됩니다. · 직접 검토하고 제출하세요.
After a phishing incident
피해자를 위한 권고 사항 및 조언
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.
모든 비밀번호 변경 — 이메일, 익스체인지 계정 등, 동일한 비밀번호를 사용하는 모든 것
2단계 인증 활성화 인증 앱(SMS 제외)을 사용합니다. SMS 기반 복구 기능을 비활성화하세요.
카드 동결 피싱 사이트에 은행 계좌 정보를 입력한 경우
보고서를 작성하기 위해 어떤 정보를 수집해야 할까요?
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.
정확한 날짜 및 시간 — 각 거래 내역 및 사기범과의 첫 접촉 시점
스크린샷 — 사기 웹사이트, 채팅 메시지, 이메일, 지갑 거래, 소셜 미디어
모든 URL 및 도메인 사기꾼이 사용한 (다음과 같은 것들을 포함하여 jtx.waitlists.network)
커뮤니케이션 — 사기꾼이 사용한 이메일, 문자, 전화번호, 사용자 이름
비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
지역 경찰 — 비록 당장 조치를 취할 수는 없더라도 공식 기록을 남깁니다
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?
가짜 웹사이트 — 도메인을 약간만 변경한, 정식 사이트와 픽셀 단위로 완벽하게 일치하는 복제 사이트
pig butchering — Telegram·왓츠앱·데이트 앱을 통해 몇 주에 걸쳐 신뢰를 쌓은 뒤, 돈을 훔쳐갔다
회복 사기 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI를 이용한 사기 — 딥페이크, 자동화된 피싱, AI로 생성된 사이트 등으로 인해 사기 행각을 적발하기가 더 어려워지고 있다
앞으로 어떻게 하면 스스로를 지킬 수 있을까요?
공식 사이트 즐겨찾기 추가 — 이메일, DM 또는 광고에 포함된 링크는 절대 클릭하지 마세요
도메인 확인 — 확인하기 PhishDestroy 상호작용을 시작하기 전에 HTTPS, 맞춤법, 도메인 등록 기간을 확인하세요.
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.
(US)
