The domain amlchecknow.digital was registered on February 21, 2026 through PDR Ltd. d/b/a PublicDomainRegistry.com and immediately pointed to Cloudflare nameservers ashley.ns.cloudflare.com and marvin.ns.cloudflare.com. The site presented a page title identical to the domain name and was classified as a crypto scam. An SSL certificate labeled WE1 was observed, indicating the use of Transport Layer Security despite the site’s brief operational window. VirusTotal scans recorded detections by six of ninety‑five security vendors, and the domain is listed on a single external blocklist.
PhishDestroy confirmed the domain as malicious and has taken it offline, which is reflected in the current offline status. The available evidence confirms that the domain was used for phishing‑related activity targeting cryptocurrency interests, but no additional details about the payload, landing page content, or victim interaction have been disclosed. Uncertainty remains regarding the specific phishing kit employed, the hosting IP address, and whether the domain might be re‑activated by the threat actor.
Defenders should continue to block the domain at network and endpoint layers, monitor the associated Cloudflare nameservers for any future re‑registration, and add the domain to internal threat intelligence feeds. Ongoing observation of related registrations through the same registrar and the same SSL certificate fingerprint may reveal a broader campaign. Given the confirmed detections and blocklist presence, maintaining a deny‑list entry for amlchecknow.digital is advised to prevent potential re‑use.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='amlchecknow.digital', port=80): Max retries exceeded with url: / (Caused by NewConnectionE
Minimum notice count2 is the number of stored outgoing report records for this domain. It does not by itself prove acknowledgement or action by a recipient.
ICANN RAA §3.18
The history below lists stored escalation records and timestamps. It does not by itself establish receipt, acknowledgement, compliance, or enforcement by any recipient.
技术详情Provenance & timestamps
首次发现2026年2月19日
DOM Analysisanalyzed 2026年7月29日score 78/100
案件 ID
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation未知Probe Inconclusive20%2026-10-11 01:17:09 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-15 22:17:48 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.
Google PageSpeed Insights — mobile performance audit of amlchecknow.digital· checked Mar 2, 2026
100
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
0.76s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.76s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Abuse Report Escalation History · 2 reports over 32 days · click to expand
PhishDestroy does not flood registrars.
Follow-up reports are sent only when one of the following is true: a user-initiated re-report was submitted via our public form, our monitoring detected the domain resurfacing in a search engine result or third-party feed, or our live-checker confirmed the domain remains technically active and still exhibits fraudulent behaviour. Each escalation below represents an independent trigger — not automated noise.
2 abuse reports filed over 234 days — eventually taken down
PDR Ltd. d/b/a PublicDomainRegistry.com was notified 2 times before the domain was removed. ICANN Compliance was CC’d on at least one escalation — receipt of each complaint is therefore on the record.
2
reports
234
days
ICANN CC
Report #1Feb 19, 2026 · 06:35 UTC
Phishing Abuse Report: amlchecknow[.]digital
abuse-contact@publicdomainregistry.com
Report #2ICANN CC751h still activeMar 22, 2026 · 16:35 UTC
ICANN RAA §3.18 requires accredited registrars to publish an abuse point-of-contact and take reasonable and prompt steps in response to reports of illegal activity. The timeline above documents delivered reports — registrar acknowledgement and takedown timing are independently verifiable via the archived email threads on request.
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-03-02 04:48:02 UTC
VirusTotal scanner detections updated from 5 to 6. Added scanner alerts: CRDF.
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
17 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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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.
(IN)
