amlcheck[.]support
Phishing and security check for amlcheck.support
“YouTube”
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.
Threat Response Pipeline
Public Blocklist Status
Stored Capture
Domain Intelligence
Technical detailsDNS, SSL SANs, timestamps
ICANN OVERSIGHT
Accreditation and RAA context
Accreditation and RAA context
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.
VirusTotal Analysis
Evidence & External Reports
PD-1769244255-amlcheck.suppor Recipient: abuse@publicdomainregistry.com Were You Affected by This Site?
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Report to Your Local Authorities
Select your country to get official cybercrime contacts, or create a complaint draft →.
Check Any Domain
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowReport Phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent phishing reports and observed availability changes
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive