PhishDestroy has listed agiaiwn.shop as a suspicious domain based on multiple security detections. The recorded page title is “Default Web Site Page”. The domain was first observed by PhishDestroy on 2026-10-20.
How the scam works
The current evidence consists only of external security detections; no specific phishing, malware, or fraud activity has been observed on the site itself. Consequently, the listing does not point to a particular scam mechanism.
Evidence
VirusTotal recorded four detections from 92 scanning engines, with alphaMountain.ai, CRDF, DNS8 and SOCRadar flagging the site; the data were retrieved on 2026-10-20 and the analysis was performed on 2026-10-15. Google Safe Browsing reported the domain as not flagged as of 2026-10-20. Spamhaus DBL listed agiaiwn.shop as a spam domain on 2026-10-20. OTX showed four pulses referencing the domain on 2026-10-20. PhishDestroy’s internal blocklist includes the domain as of 2026-10-20, while no external blocklists reported it.
Infrastructure
The recorded IP address for agiaiwn.shop is 91.92.35.94, which belongs to AS209101 IP Vendetta Inc. and is associated with the Netherlands. No additional registration or hosting details are available.
What to do
Visitors should avoid providing credentials, personal data or cryptocurrency information on the site and consider changing passwords for any accounts where credentials may have been entered. Organizations should add agiaiwn.shop to their blocklists and monitor network logs for connections to 91.92.35.94. No broader blocking of the entire IP range or hosting provider is required based on the current evidence.
RegistrationCreated Oct 14, 2026 (5d · Brand New!)—Expires Oct 14, 2027
Technical detailsProvenance & timestamps
First DetectedOct 20, 2026
DOM Analysisanalyzed Oct 20, 2026score 0/100
Submitted URLhttp://agiaiwn.shop/
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.
6 evidence signal groups linked1 stored notification recordsUnverified
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 agiaiwn.shop)
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.
(US)
