onchain-dex.fit was recorded in a MetaMask blocklist entry dated 2026-10-11, which documents its presence as a listed domain on that day. The domain also appears in an internal listing from PhishDestroy, expanding the range of its recorded evidence.
Recorded Evidence
MetaMask included onchain-dex.fit in its external blocklist on 2026-10-11. SEAL also listed the domain as an external blocklist entry on the same date. PhishDestroy internally recorded onchain-dex.fit as listed on 2026-10-11. The domain was registered with Gname.com Pte. Ltd. on 2026-09-09.
Interpretation
PhishDestroy contains an internal listing record for onchain-dex.fit, which documents its inclusion according to their criteria. MetaMask and SEAL each provide external blocklist records, measuring the domain’s listing status as of their respective observation dates. These sources collectively offer a snapshot of the domain’s presence in both internal and external blocklist records.
Recommended Actions
For onchain-dex.fit, retain the MetaMask, SEAL, and PhishDestroy records for future reference and comparison. Use these dated blocklist entries to inform subsequent checks and to contextualize future observations of the domain’s listing status.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
등록 정보생성됨 2026년 9월 9일 (32d · New)—Expires 2027년 9월 9일
기술 세부 정보Provenance & timestamps
최초 발견2026년 10월 11일
Submitted URLhttp://onchain-dex.fit/
사건 ID
ICANN OVERSIGHT
인증 및 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.
Certificate fingerprint061f40dd022576a2e48e8beef2e43f045adbf2aa008f1f2c4421eb6bcb6f07e9Certificate names · 8 SANs
djgja242dfa.xyz
onchain-dex.club
onchain-dex.me
onchain-dex.net
onchain-dex.store
onchain-dex.website
onchain-dex.work
onchain-dex.xyz
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation알 수 없음Probe Inconclusive20%2026-10-11 11:25:03 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 11:25:03 UTC
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.
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.
Threat First Observed2026-10-11 11:25:03 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 54.192.35.46.
위협 대응 Pipeline
발견
Analysis
Monitoring
5 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.
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.
보고서 
(US)
