The domain amlguard.digital is currently active and classified as a high‑risk crypto scam. Registration details show the domain was created through a DNS and CDN provider, with authoritative nameservers osmar.ns.cloudflare.com and pam.ns.cloudflare.com. DNS resolution points to IP address 188.114.96.3, which belongs to an autonomous system operating in the United States. HTTP requests return status code 525, indicating a TLS handshake failure, while the presented TLS certificate is issued by a widely recognized certificate authority (WE1). The page title returned by the server is "AMLGuard," and the site employs a CDN‑based performance service that reports usage of HTTP/3 and browser insight technologies. Threat intelligence indicates that one of ninety‑five security scanners flagged the domain, and it appears on two external blocklists. The domain has been blocked by the PhishDestroy and ScamSniffer blocklists, and its Gridinsoft trust score is 0 out of 100. Defenders should treat any traffic to amlguard.digital as malicious, enforce network‑level blocks, and consider adding the domain to internal allow‑list exclusions. Continuous monitoring is advised to detect any changes in hosting or certificate attributes, but the current evidence supports immediate containment and user awareness actions.
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 observationRedirectingHTTP redirect observed80%2026-10-11 10:07:16 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:07:16 UTClast content: 2026-10-10 10:06:32 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
Performance monitoring tool that measures website speed from real users.
Google PageSpeed Insights — mobile performance audit of amlguard.digital· checked Mar 2, 2026
100
Good
Performance
FCP
0.77s
First Contentful Paint
LCP
0.77s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.77s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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.
Domain Status Transition2026-10-09 01:42:17 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-18 10:07:35 UTC
Domain state transitioned from alive to dead.
Domain Status Transition2026-03-09 02:57:20 UTC
Domain state transitioned from alive to dead.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
13 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.
(US)
