ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@dynadot.com.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
aml.legal was observed returning HTTP status 200 on 2026-10-01, indicating a successful response at that time. The domain was first recorded on 2026-09-06, and its PageSpeed performance score on that date was 97.
Recorded Evidence
On 2026-09-19, VirusTotal reported 4 detections out of 89 scanners for aml.legal. OTX recorded 4 pulses for this domain on 2026-09-11. The PhishDestroy internal listing included aml.legal as of the evidence date, and the domain's registration with Dynadot Inc was documented on 2026-07-31. A certificate from Google Trust Services / WE1 was observed on 2026-09-06.
Interpretation
The evidence from VirusTotal and OTX was gathered on different dates, providing separate perspectives on aml.legal's status over time. The HTTP response, PhishDestroy listing, and certificate observation were also recorded on distinct dates, allowing for a chronological comparison rather than a single unified snapshot.
Recommended Actions
Retain all dated records for aml.legal to enable future comparison and trend analysis. When reviewing aml.legal, avoid entering sensitive information and rely on the specific dates of each observation to inform your assessment.
Extracted from stored page analysis
Observed indicators
1 wallet · 0 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
DOM Analysisanalyzed 2026年9月6日score 81/10014 brand signals
IoC Extractionscanned 2026年9月7日1 wallet · 0 Telegram IoC
Submitted URLhttps://aml.legal/
Favicon Hash
ケース 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.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationコンテンツ公開中Ordinary HTTP content served90%2026-10-11 10:36:40 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:36:40 UTClast content: 2026-10-11 10:36:40 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.
使用技術 · 2 identified
Cloudflare
CDN
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Google PageSpeed Insights — mobile performance audit of aml.legal· checked Sep 6, 2026
97
Good
Performance
FCP
1.26s
First Contentful Paint
LCP
1.65s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
189ms
Total Blocking Time
SI
2.68s
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.
VirusTotal Detections Update2026-09-08 12:33:48 UTC
VirusTotal scanner detections updated from 3 to 0. Resolved alerts: CRDF, Gridinsoft, SOCRadar.
VirusTotal Detections Update2026-09-07 13:59:36 UTC
VirusTotal scanner detections updated from 2 to 3. Added scanner alerts: Gridinsoft.
VirusTotal Detections Update2026-09-07 03:46:50 UTC
VirusTotal scanner detections updated from 1 to 2. Added scanner alerts: SOCRadar.
VirusTotal Detections Update2026-09-07 02:36:23 UTC
VirusTotal scanner detections updated from 0 to 1. Added scanner alerts: CRDF.
Threat First Observed2026-09-06 11:40:28 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 172.67.210.41.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
15 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.
