PhishDestroy added automindpy.digital to its internal blocklist on 2026-10-22, citing a VirusTotal scan that returned 13 malicious detections. The domain was first seen by PhishDestroy on 2026-10-22, 123 days after its registration on 2026-06-21. A GET request recorded on that date returned HTTP 200.
How the scam works
The listing does not identify a concrete fraud technique; the recorded page title advertises an AI‑powered trading platform, a theme sometimes used in deceptive financial offers. Without observed credential‑phishing forms or wallet‑draining scripts, the risk remains limited to a potentially misleading promotional site that could be leveraged for social engineering.
Evidence
VirusTotal analysis on 2026-10-21 recorded 13 malicious and 3 suspicious detections out of 92 engines. Google Safe Browsing checked on 2026-10-22 did not flag the domain. OTX listed five pulses referencing the domain as of 2026-10-22. urlscan.io scanned the site on 2026-10-22; its machine‑learning engine assigned a malicious score of 98, though the overall verdict was non‑malicious. Cloudflare Radar scan on 2026-10-22 marked the domain malicious for malware. PhishDestroy’s internal blocklist includes the domain, while external blocklists returned no hits on the same day.
Infrastructure
The domain was registered with NETIM SAS on 2026-06-21 and was 122 days old at the time of scanning. The recorded IP was 185.62.56.121, associated with Snel.com B.V. in the Netherlands, and the domain used Cloudflare name servers (alexa.ns.cloudflare.com, ned.ns.cloudflare.com). TLS was provided by a ZeroSSL ECC DV SSL CA 2 certificate, valid from 2026-09-11 to 2026-12-10. No DNSSEC records were observed.
What to do
Avoid entering credentials, financial information, or downloading files from this site. If any credentials were submitted, change the associated passwords and monitor the accounts for unauthorized activity. Defenders should block the exact domain and review logs for any connections to this host.
RegistrationCreated Jun 21, 2026 (122d)—Expires Jun 21, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 22, 2026
DOM Analysisanalyzed Oct 22, 2026score 25/1002 brand signals
Submitted URLhttp://automindpy.digital/
Case ID
ICANN OVERSIGHT
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.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
185.62.56.121
Network ASN
AS62370
Organization
Snel.com B.V.
Observed location
Rotterdam, NL
Nameservers 2
alexa.ns.cloudflare.com
ned.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
ZeroSSL ECC DV SSL CA 2
Valid from
2026-09-11 00:00:00
Valid until
2026-12-10 23:59:59
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintc800725bdda3495ed8a8d5e95835906014861d049e1f66e129b2f146accaee4aCertificate names · 1 SANs
automindpy.digital
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · automindpy.digital
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
5 evidence signal groups linked0 stored notification recordsLast known active
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including automindpy.digital)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.
