simkaboksti72.com returned HTTP status 502 in a check recorded on 2026-10-01, indicating the server could not fulfill that request at that time. The domain was first observed on 2026-09-13, the same date its OTX record and SSL scan were captured.
Recorded Evidence
The domain simkaboksti72.com was first observed on 2026-09-13. An OTX check on 2026-09-13 recorded 4 pulses. A PhishDestroy internal listing was also recorded. VirusTotal, checked on 2026-09-16, reported 6 detections across 89 scanners. The domain resolved to IP address 179.198.49.117, associated with Poland and PowerRDP Network LTD. Registration data shows a registration date of 2026-09-11 with registrar Dominet (HK) Limited, and an SSL certificate issued by Let's Encrypt / YE2 scanned on 2026-09-13.
Interpretation
The recorded sources describe different aspects of simkaboksti72.com without forming a single verdict. The HTTP 502 response reflects only the server's reply at the time of that check, not the domain's overall content. The OTX pulses and PhishDestroy listing are separate catalogue observations, while the VirusTotal detections come from a different measurement date. Because the dates differ, these records should be compared as distinct snapshots rather than treated as one continuous signal.
Recommended Actions
Preserve the HTTP response record for simkaboksti72.com and the PhishDestroy listing as separate source documents. Compare the OTX pulse record with the VirusTotal detection record in separate review steps, since they were captured on different dates. Retain the registration and SSL scan records for reference, and re-check the domain's HTTP response before relying on the earlier status.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='simkaboksti72.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionErr
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:31:06 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-21 02:15:13 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-21 02:15:13 UTC → 2026-09-30 16:14:55 UTC · 230.00hmidpoint estimate ≈ 2026-09-25 21:15:04 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
Python
Programming languages
Python is an interpreted and general-purpose programming language.
Last analyzed First positive detection Previous stored snapshot: 4 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Gridinsoft
SOCRadar
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-21 10:43:55 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-13 06:09:37 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 179.198.49.117.
威胁响应 Pipeline
发现
Analysis
Notifications
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.
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
