PhishDestroy added donupex.com to its internal blocklist on 2026-10-21 after a trusted auto intake flagged the domain as only two days old and the page provided insufficient content for deeper analysis. The intake AI recorded an "unknown" verdict on the same date because no malicious behavior could be observed. On 2026-10-21 urlscan captured an HTTP status code 666 and a redirect chain that ended at a Google Chrome page.
How the scam works
No specific malicious behavior was observed on the site, so the listing does not confirm any particular fraud technique. Suspicious, newly‑registered domains are sometimes used for phishing, credential harvesting, or unwanted redirects, but the exact purpose of this domain cannot be determined from the available evidence.
Evidence
VirusTotal scanned the domain on 2026-10-21 and reported one suspicious detection out of 92 engines, flagged by Gridinsoft. Google Safe Browsing checked the domain on the same date and did not flag it. urlscan recorded the site on 2026-10-21; its overall verdict was clean, while its machine‑learning engine labeled it malicious with a score of 85 and tags urlscan-ml and urlscan-ml-60c5e22. OTX listed two pulses referencing donupex.com as of 2026-10-21, and no external blocklists reported the domain as malicious at that time. PhishDestroy’s internal list marks the domain as blocked.
Infrastructure
The domain was registered on 2026-10-19 through Dynadot Inc. DNS resolution recorded the IP address 172.67.150.154, which belongs to Cloudflare, Inc. and is associated with Canada. Cloudflare’s web application firewall was observed as active for the site.
What to do
Visitors should avoid entering credentials or downloading files from this domain. If any personal information was submitted, change the associated passwords and monitor accounts for unusual activity. Defenders should add donupex.com to blocklists and review DNS or proxy logs for accesses to this exact domain.
Issued by Let's Encrypt / YE2· stored validity ends in 88 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
172.67.150.154
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Nameservers 2
coleman.ns.cloudflare.com
lola.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YE2
Valid from
2026-10-19 18:42:04
Valid until
2027-01-17 18:42:03
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint29c86c739d2db94e35bcaf1e5702a89ec91c6216b742966659011e1c665e7e6eCertificate names · 2 SANs
*.donupex.com
donupex.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
4 evidence signal groups linked0 stored notification recordsUnverified
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 donupex.com)
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)
