PhishDestroy first recorded happy-dividend.com on 2026-10-28. Stored VirusTotal result: 16/92 engines flagged. Malicious: 13. Suspicious: 3. Analysis time (as stored): 2026-10-24 18:15 UTC. Retrieved (as stored): 2026-10-28 02:52 UTC.
More about the sources
Recorded security signals
Stored VirusTotal result: 16/92 engines flagged. Malicious: 13. Suspicious: 3. Analysis time (as stored): 2026-10-24 18:15 UTC. Retrieved (as stored): 2026-10-28 02:52 UTC. Use caution — do not enter credentials or personal information.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
Analysis
Domain summary
PhishDestroy first recorded happy-dividend.com on 2026-10-28. Stored VirusTotal result: 16/92 engines flagged. Malicious: 13. Suspicious: 3. Analysis time (as stored): 2026-10-24 18:15 UTC. Retrieved (as stored): 2026-10-28 02:52 UTC. Risk: critical (evidence score 100/100). Registrar: Porkbun. Status: Last known active. Hosting: Cloudflare, Inc. Do not enter credentials or connect a wallet.
PhishDestroy added happy-dividend.com to its internal blocklist on 2026-10-28 following an intake that highlighted 13 malicious detections on VirusTotal. The domain was first seen by PhishDestroy on that same date. A page fetch performed on 2026-10-28 returned HTTP 403, while an earlier URLScan capture from 2026-05-16 recorded a reachable page returning HTTP 200. No page title was recorded.
How the scam works
The domain is flagged because security engines have identified it as malicious or phishing, a category that typically involves deceptive pages designed to trick visitors into revealing credentials or installing unwanted software. No specific malicious behavior was observed on the captured page, so the exact scam technique cannot be confirmed for this site.
Evidence
VirusTotal analysis on 2026-10-24 reported 13 malicious and 3 suspicious detections out of 92 engines, with 16 total detections from vendors such as BitDefender, Fortinet and G-Data. Google Safe Browsing checked on 2026-10-28 did not flag the domain. PhishDestroy’s internal blocklist marks the domain as listed. OTX listed three pulses referencing the domain as of 2026-10-28. URLScan captured the site on 2026-05-16, showing an HTTP 200 response and an engine verdict of malicious with a score of 95. Cloudflare Radar scanned the domain on 2026-10-28 and classified it as malicious, labeling it under malware and phishing categories.
Infrastructure
The domain was registered with Porkbun LLC on 2025-12-04 and is set to expire on 2026-12-04. DNS records resolve to Cloudflare IP addresses 104.21.77.110 and 172.67.207.48, as well as corresponding IPv6 addresses. The site uses a Cloudflare CDN and presents a TLS certificate issued by Google Trust Services, valid from 2026-09-07 to 2026-12-06. Cloudflare’s web application firewall is enabled for the domain.
What to do
Visitors should avoid entering any credentials, downloading files, or interacting with the site, and should change any passwords used on it. Organizations should block happy-dividend.com at the DNS or proxy level, monitor for connections to its IP addresses, and review logs for any access attempts. Security teams can add the domain to threat intelligence feeds and continue to monitor VirusTotal and other sources for updates.
This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.
Urlscan result at: 2026-10-28 05:31:10; Urlscan enriched at: 2026-10-28 10:11:38
Technical metadata
PhishDestroy narrative
Narrative generation metadata
Open report Title, description and generation record
The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
AI title
happy-dividend.com — Suspicious Domain
AI description
PhishDestroy flags happy-dividend.com as a suspicious domain after multiple security engines marked it malicious, even though Google Safe Browsing shows no…
AI summary
Overview PhishDestroy added happy-dividend.com to its internal blocklist on 2026-10-28 following an intake that highlighted 13 malicious detections on VirusTotal. The domain was first seen by PhishDestroy on that same date. A page fetch performed on 2026-10-28 returned HTTP 403, while an earlier URLScan capture from 2026-05-16 recorded a reachable page returning HTTP 200. No page title was recorded. How the scam works The domain is flagged because security engines have identified it as malicious or phishing, a category that typically involves deceptive pages designed to trick visitors into revealing credentials or installing unwanted software. No specific malicious behavior was observed on the captured page, so the exact scam technique cannot be confirmed for this site. Evidence VirusTotal analysis on 2026-10-24 reported 13 malicious and 3 suspicious detections out of 92 engines, with 16 total detections from vendors such as BitDefender, Fortinet and G-Data. Google Safe Browsing checked on 2026-10-28 did not flag the domain. PhishDestroy’s internal blocklist marks the domain as listed. OTX listed three pulses referencing the domain as of 2026-10-28. URLScan captured the site on 2026-05-16, showing an HTTP 200 response and an engine verdict of malicious with a score of 95. Cloudflare Radar scanned the domain on 2026-10-28 and classified it as malicious, labeling it under malware and phishing categories. Infrastructure The domain was registered with Porkbun LLC on 2025-12-04 and is set to expire on 2026-12-04. DNS records resolve to Cloudflare IP addresses 104.21.77.110 and 172.67.207.48, as well as corresponding IPv6 addresses. The site uses a Cloudflare CDN and presents a TLS certificate issued by Google Trust Services, valid from 2026-09-07 to 2026-12-06. Cloudflare’s web application firewall is enabled for the domain. What to do Visitors should avoid entering any credentials, downloading files, or interacting with the site, and should change any passwords used on it. Organizations should block happy-dividend.com at the DNS or proxy level, monitor for connections to its IP addresses, and review logs for any access attempts. Security teams can add the domain to threat intelligence feeds and continue to monitor VirusTotal and other sources for updates. Useful links urlscan.io scan and screenshot: https://urlscan.io/result/019e2fb8-0641-7593-9148-e21effd47b1d/ Cloudflare Radar report: https://radar.cloudflare.com/scan/efa577ec-911c-4ddb-8866-3cfa41ee607f Stored capture screenshot: https://urlscan.io/screenshots/019e2fb8-0641-7593-9148-e21effd47b1d.png Cloudflare Radar screenshot (2026-10-28T02:20:39Z): https://screenshots.phishdestroy.io/cf/efa577ec-911c-4ddb-8866-3cfa41ee607f.png URLScan screenshot (2026-05-15T13:45:40Z): https://screenshots.phishdestroy.io/us/019e2be2-aa93-7537-9f6c-f3501aeebc61.png URLScan capture report: https://urlscan.io/result/019e2be2-aa93-7537-9f6c-f3501aeebc61/ VirusTotal report: https://www.virustotal.com/gui/domain/happy-dividend.com Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=happy-dividend.com Archived copy: https://web.archive.org/web/20261028021740/https://happy-dividend.com/ Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/ Site owner? Request a review: https://phishdestroy.io/appeals/
PhishDestroy rates happy-dividend.com as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-10-28. Stored VirusTotal result: 16/92 engines flagged. Malicious: 13. Suspicious: 3. Analysis time (as stored): 2026-10-24 18:15 UTC. Retrieved (as stored): 2026-10-28 02:52 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Is happy-dividend.com safe to connect a wallet?
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on happy-dividend.com. A confirmed blockchain transaction cannot be reversed.
What should I do if I used happy-dividend.com?
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Downloaded a file — do not open it and scan the device with security software
Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.
Certificate fingerprint7fe4ce68e50ae81c3a035d79347c518d67f1ded714ba1e08840f9187feb54d95Certificate names · 2 SANs
happy-dividend.com
*.happy-dividend.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: Resolved
Latest HTTP observationLive contentOrdinary HTTP content served90%2026-11-22 11:16 UTC
RDAP registration
Observed timelinelast reachable: 2026-11-22 11:16 UTClast content: 2026-11-22 11:16 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 01:53 UTC.
Recorded events: 15. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
The domain remains reachable or access-restricted; future checks may update this observation.
ongoing
Recorded activity
6 entries
Lifecycle
Domain registered
VirusTotal analysis with detections+324 d 10 h
Added to PhishDestroy+3 d 7 h
AlienVault OTX
3 community references
+32 min
Cloudflare Radar
Phishing
+2 min
Wayback Machine
Page archived
+4 min
Added to PhishDestroy
happy-dividend.com
+3 d 7 h
VirusTotal
16/92 engine detections
+161 d 10 h
URLScan
Malicious · engine verdict · score 95
How we investigate & report
Public scans, evidence and abuse channels
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.
Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
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.
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Downloaded a file — do not open it and scan the device with security software
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed
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 happy-dividend.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
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 →
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.