SSL certificate is invalid or expired. Issuer: WE1
証拠の概要
クリティカル
VirusTotal
2/93
URLScan
Stored capture
Analysis of the domain amltrust.online indicates it was actively flagged as a crypto scam phishing site prior to being taken offline on July 25, 2026. The domain, registered on January 20, 2026, through Eranet International Limited, resolved to the IP address 104.21.82.68, which is hosted on Cloudflare's infrastructure (AS13335) in the United States. While the domain is currently offline, its infrastructure and prior detection history suggest a deliberate attempt to deceive users, likely targeting cryptocurrency transactions or credentials. Two of 93 security vendors on VirusTotal flagged amltrust.online as malicious, though the specific detection rules or signatures were not disclosed.
The domain appears on at least one security blocklist, and it was proactively blocked by PhishDestroy, a specialized anti-phishing service. Gridinsoft assigned the domain a trust score of 0/100, further corroborating its classification as high-risk. The SSL certificate, issued under the identifier WE1, does not provide additional brand or organizational context, and the page title 'Just a moment...' is consistent with Cloudflare interstitial pages, often seen during temporary hosting or redirection setups. No concrete evidence links this domain to a specific cryptocurrency platform, wallet, or exchange, and the exact mechanics of the scam remain unconfirmed due to the lack of accessible page content.
However, the combination of its registration details, hosting provider, and detection by security vendors aligns with known patterns of crypto-related phishing operations. Defenders should treat this domain as compromised and include it in blocklists or monitoring systems, particularly for environments handling cryptocurrency transactions. Further investigation into associated IP ranges, registrar history, and certificate transparency logs may reveal additional connected infrastructure or campaigns.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='amltrust.online', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
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.
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:07:49 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-05-11 22:00:44 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-05-11 22:00:44 UTC → 2026-09-30 16:14:55 UTC · 3,402.24hmidpoint estimate ≈ 2026-07-21 19:07:49 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.
8 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
