PhishDestroy listed aurix.click on its internal blocklist as a suspicious domain. The recorded page title advertises an AI trading platform. The domain was first seen by PhishDestroy on 2026-10-22, and an HTTP GET on that date returned a 200 status code.
How the scam works
A suspicious‑domain classification indicates the site could be used to lure visitors into providing credentials or personal data, but no specific malicious behavior was observed on the captured page. The AI‑trading claim is a common lure in fraudulent schemes, yet the listing is based on external detections rather than confirmed on‑site activity.
Evidence
VirusTotal scanned the domain on 2026-10-22; 15 vendors marked it malicious, 3 marked it suspicious, for a total of 18 detections out of 92 engines. Google Safe Browsing checked the same day and did not flag the URL. urlscan.io captured the page on 2026-10-22; its machine‑learning engine gave a malicious score of 97 while the overall verdict was non‑malicious. Cloudflare Radar scanned the site on 2026-10-22 and returned a malicious verdict with a malware category. OTX listed four pulses referencing the domain as of 2026-10-22. PhishDestroy’s internal blocklist contains the domain, whereas external blocklists returned zero hits on that date.
Infrastructure
The domain was registered with NETIM on 2026-05-31. DNS resolution returned the IP 185.62.57.222, recorded as belonging to Snel.com B.V. in the Netherlands. Nameservers are sage.ns.cloudflare.com and lina.ns.cloudflare.com, indicating Cloudflare DNS service. The TLS certificate, issued by ZeroSSL ECC DV SSL CA 2, is valid from 2026-08-31 to 2026-11-29 and covers only aurix.click.
What to do
If you visited the site and entered login or personal information, change those credentials immediately and monitor related accounts for unauthorized activity. Do not download files or grant any permissions from this site. Security teams should block aurix.click at firewalls or proxies, log any DNS or HTTP requests to 185.62.57.222, and keep the domain on threat‑intel feeds.
RegistrationCreated May 31, 2026 (143d)—Expires May 31, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 22, 2026
DOM Analysisanalyzed Oct 22, 2026score 25/1001 brand signal
Submitted URLhttp://aurix.click/
Favicon Hash
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.57.222
Network ASN
AS62370
Organization
Snel.com B.V.
Observed location
Rotterdam, NL
Nameservers 2
lina.ns.cloudflare.com
sage.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
ZeroSSL ECC DV SSL CA 2
Valid from
2026-08-31 00:00:00
Valid until
2026-11-29 23:59:59
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint1b87ee353a3e868f286092e4c254c8c6ef8a0d2c46eb8019ef32bea7dd0e133dCertificate names · 1 SANs
aurix.click
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 · aurix.click
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.
6 evidence signal groups linked1 stored notification recordsLast known active
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 aurix.click)
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.
(CA)
