The domain amlchecker.digital was observed serving an investment‑fraud landing page with the title “Nur einen Moment…”. The site resolves to the IP address 172.67.147.250, which belongs to AS13335 operated by Cloudflare, Inc., and is geolocated in the United States. No TLS certificate was presented, indicating the site was accessed over plain HTTP. Registration data show the domain was created through Web Commerce Communications Limited doing business as WebNic.cc, and the authoritative name servers are ns100.webnic.cc and ns101.webnic.cc.
Independent threat‑intel feeds have placed the domain on at least one security blocklist, and PhishDestroy has already taken the site offline. VirusTotal scans reported nine positive detections out of ninety‑five scanners, confirming malicious intent consistent with the investment‑scam classification supplied in the intelligence. The combination of a Cloudflare edge IP, lack of encryption, and rapid blocklist inclusion suggests a short‑lived, opportunistic campaign that leverages free hosting to hide behind a reputable CDN.
While the exact phishing kit or compromised credentials have not been disclosed, the observed indicators are sufficient to flag the domain as malicious. Defenders should add amlchecker.digital to blocklists, enforce DNS sinkholing or firewall deny rules for the resolved IP, monitor for any newly‑registered subdomains under the same registrar, and update web‑proxy filtering policies to reject traffic to the domain and its associated IP. Continuous re‑inspection of the IP range 172.67.147.0/24 is advised, as Cloudflare often serves multiple unrelated malicious payloads from adjacent addresses.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='amlchecker.digital', port=80): Max retries exceeded with url: / (Caused by NewConnectionEr
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 timelinelast reachable: 2026-09-26 10:02:13 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-26 10:02:13 UTC → 2026-09-30 16:14:55 UTC · 102.21hmidpoint estimate ≈ 2026-09-28 13:08:34 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.
Last analyzed Previous stored snapshot: 9 detections
ADMINUSLabs
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
カスペルスキー
Lionic
ソフォス
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.
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)
