okekjaiw.click returned HTTP status 502 on 2026-10-01, a server-error response recorded at that check time. The domain was first observed in this dataset on 2026-08-27, giving a dated starting point for later comparison.
Recorded Evidence
The HTTP check on 2026-10-01 recorded a 502 response for okekjaiw.click, while the first observation in the dataset dates to 2026-08-27. VirusTotal reported 17 detections across 90 scanners on 2026-09-06, and OTX recorded 7 pulses on 2026-09-06. The PhishDestroy internal listing was also recorded, and the registrar was Global Domain Group LLC.
Interpretation
Because the HTTP, VirusTotal, OTX, and PhishDestroy records carry different observation dates, each reflects only the moment it was captured. Comparing those dated snapshots shows how the recorded signals line up or diverge, without treating any one entry as a settled conclusion.
Recommended Actions
For okekjaiw.click, keep the dated HTTP, VirusTotal, OTX, and PhishDestroy records together so later checks can be compared against them. When new observations arrive, note their exact dates and avoid submitting sensitive information to the domain during review.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='okekjaiw.click', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
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.
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 01:20:39 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-15 22:18:06 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.
Last analyzed First positive detection Previous stored snapshot: 17 detections
alphaMountain.ai
ArcSight Threat Intelligence
BitDefender
Certego
Chong Lua Dao
CRDF
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
Lumu
SOCRadar
Sophos
VIPRE
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
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.
Domain Status Transition2026-09-11 22:17:53 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-11 01:37:06 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-04 23:43:10 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
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.
This report concerns an automated cryptocurrency laundering machine on the Polygon network that is used by the operators of an active macOS malware (stealer) campaign.
CONTEXT The malware campaign delivers a macOS stealer via fake "CipherCheck — I'm not a robot" verification p
1 report filed for okekjaiw.click (1 written by a person) · category: Other Hack · source checked
“This report concerns an automated cryptocurrency laundering machine on the Polygon network that is used by the operators of an active macOS malware (stealer) campaign.
CONTEXT The malware campaign delivers a macOS stealer via fake "CipherCheck — I'm not a robot" verification pages. Victims are tricked into pasting a base64-encoded command into Terminal, which installs a persistent LaunchAgent and pulls a second-stage payload from a Polygon smart contract used as a C2 directory (contract 0xA3a”
— reported by Anonymous on Aug 27, 2026 · Source: ChainAbuse (TRM Labs) — full report and evidence there.
(US)
