On 24 July 2026 analysts observed the domain amlcheck.support resolving to the IPv4 address 142.250.185.206. The address is allocated to AS15169 Google LLC and is geolocated in the United States, indicating the site was hosted on Google’s infrastructure. The domain was registered on 21 February 2026 through PDR Ltd. d/b/a PublicDomainRegistry.com and does not present an SSL/TLS certificate, meaning connections are unencrypted. An HTTP request returned a page whose title field contained the string “YouTube”, a common brand used in credential‑harvesting campaigns.
The site was classified as a crypto‑related scam in the intelligence feed and appears on the PhishDestroy blocklist, the only public blocklist currently listing it. VirusTotal scanned the URL with 95 antivirus engines and reported no detections; this absence of flags does not confirm benign intent. As of the report date the host is offline, and no further HTTP response could be retrieved.
The combination of a newly created domain, lack of TLS, use of a reputable hosting provider, and a page title that mimics a well‑known service aligns with typical phishing infrastructure. Defenders should continue to monitor the domain for re‑activation, block the resolved IP address at network perimeter, add the domain to internal blocklists, and consider threat‑intel sharing with partners. Additional analysis of any future content, TLS adoption, or redirection behavior would be required to fully characterize the campaign.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='amlcheck.support', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro
DOM Analysisanalyzed 2026年7月29日score 48/1002 brand signals
ケース 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.
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:59 UTC
RDAP registration不明
Observed timelinecurrent episode first observed: 2026-09-30 16:14:55 UTCfirst terminal observation: 2026-09-30 16:14:55 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.
9 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.
(IN)
