VirusTotal
17 / 90
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.
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.
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.
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.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: 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.
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.
Edge-IP reputation is not attributed to this domain.
rex.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.
12 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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
1 community report
CategoryOTHER_HACK
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
“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”
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive