The domain amlbotchecking.digital, created on 19 June 2025 and registered through Web Commerce Communications Limited dba WebNic.cc, is currently offline but retains an elevated risk profile due to confirmed brand impersonation of AMLBot. Infrastructure analysis shows the domain resolves to IP 172.67.156.241, which belongs to AS13335 Cloudflare, Inc., located in the United States. No SSL certificate is presented, and the HTTP response yields a 522 timeout, as reflected in the page title "amlbotchecking.digital | 522: Connection timed out." The domain is listed on a single security blocklist and has been blocked by PhishDestroy.
Detection engines on VirusTotal flagged the domain in 2 of 95 scans, indicating that some security vendors have identified malicious characteristics. Additional reputation data includes a Gridinsoft trust score of 0 out of 100 and classification as an investment‑scam variant, with the employed phishing kit identified as an Airdrop Scam. Nameservers ns100.webnic.cc and ns101.webnic.cc are consistent with the registrar’s infrastructure.
While the site is presently taken offline, defenders should continue to monitor the associated IP address for any resurgence of malicious activity, ensure that any URLs containing the amlbotchecking.digital pattern are blocked at firewall or proxy layers, and update threat‑intelligence feeds with the observed indicators. Awareness campaigns targeting users of the AMLBot brand are advisable, given the domain’s explicit impersonation intent.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='amlbotchecking.digital', port=80): Max retries exceeded with url: / (Caused by NewConnecti
DOM Analysisanalyzed 2026年4月23日score 61/1001 brand signal
Submitted URLhttps://amlbotchecking.digital/
ICANN OVERSIGHT
認定と RAA の背景
Registrar accreditation and DNS abuse obligations
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:11:18 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-07-30 22:18:59 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-07-30 22:18:59 UTC → 2026-09-30 16:14:55 UTC · 1,481.93hmidpoint estimate ≈ 2026-08-30 19:16:57 UTC · precision very 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.
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.
11 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.
(MY)
