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.
颁发者 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 声誉不属于此域。
域名服务器 2
coleman.ns.cloudflare.com
lola.ns.cloudflare.com
Location describes the IP network.
TLS 证书
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.
Template-based draft · optional AI wording assistance requires separate consent
AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident
针对受害者的建议与指导
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
我应该立即采取什么措施？
紧急
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（FBI）指南
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.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
当地警方 — 即使无法立即采取行动，也能留下正式记录
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?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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)
