VirusTotal
4 / 89
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.
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.
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.
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.
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='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.
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.
norah.ns.cloudflare.comLocation describes the IP network.
13 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.
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