amlcheck-bankasi.lol returned an HTTP 502 status code on 2026-10-01, documenting a server error at that point. The domain was also included in the PhishDestroy internal listing, providing another dated record for review.
Recorded Evidence
On 2026-10-01, amlcheck-bankasi.lol produced an HTTP 502 response. VirusTotal, on 2026-09-13, showed 4 detections out of 89 scanners for this domain. OTX referenced amlcheck-bankasi.lol in two pulses on 2026-09-13. The domain was listed in the PhishDestroy internal catalogue, and its registration date was recorded as 2026-08-17 by Global Domain Group LLC.
Interpretation
These records highlight that amlcheck-bankasi.lol was observed by multiple security and monitoring sources within a short period. The HTTP status code documents a server-side issue on a specific date, while the OTX and VirusTotal entries show it was referenced and detected by external security tools. The PhishDestroy listing adds an internal publisher perspective to the domain's recorded activity.
Recommended Actions
Review amlcheck-bankasi.lol using the HTTP response, VirusTotal results, OTX pulse references, and PhishDestroy catalogue entry for further analysis. Preserve all dated source records for future comparison and monitoring. Use these observations to inform any technical or administrative steps regarding this domain.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='amlcheck-bankasi.lol', port=80): Max retries exceeded with url: / (Caused by NewConnection
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.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-11 01:00:13 UTC
RDAP registration未知
Observed timelinecurrent episode first observed: 2026-09-30 16:14:55 UTCfirst terminal observation: 2026-09-30 16:14:55 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.
技术 · 3 identified
Cloudflare Browser Insights
AnalyticsRUM
Cloudflare Browser Insights is a tool that measures the performance of websites from the perspective of users.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Last analyzed First positive detection Previous stored snapshot: 2 detections
CRDF
Fortinet
LevelBlue
SOCRadar
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.
VirusTotal Detections Update2026-09-13 04:57:27 UTC
VirusTotal scanner detections updated from 2 to 4. Added scanner alerts: CRDF, SOCRadar.
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
已捕获威胁
amlcheck-bankasi.lol 已检测到并排入队，待进行全面分析
2026年9月4日
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
2026年9月13日
Cloudflare Radar Report
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.
(US)
