PhishDestroy first recorded earnpeak.net on 2026-10-25. Stored VirusTotal result: 16/92 engines flagged. Malicious: 12. Suspicious: 4. Analysis time (as stored): 2026-10-19 07:47 UTC. Retrieved (as stored): 2026-10-25 20:42 UTC.
Page title: “502 Bad Gateway”
More about the sources
Recorded security signals
Stored VirusTotal result: 16/92 engines flagged. Malicious: 12. Suspicious: 4. Analysis time (as stored): 2026-10-19 07:47 UTC. Retrieved (as stored): 2026-10-25 20:42 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 earnpeak.net on 2026-10-25. Stored VirusTotal result: 16/92 engines flagged. Malicious: 12. Suspicious: 4. Analysis time (as stored): 2026-10-19 07:47 UTC. Retrieved (as stored): 2026-10-25 20:42 UTC. Risk: critical (evidence score 98/100). Registrar: eNom. Hosting: DigitalOcean, LLC. Do not enter credentials or connect a wallet.
PhishDestroy listed earnpeak.net as a suspicious domain based on multiple vendor detections. The site returned HTTP 200 on 2026-10-25 but no page title was recorded. PhishDestroy first saw the domain on 2026-10-25, 269 days after its registration on 2026-01-29.
How the scam works
The vendor detections associated with earnpeak.net include phishing, malware and spam labels, which are common indicators of fraudulent or malicious sites. No specific malicious payload or credential‑stealing page was captured in the available scans, so the exact technique cannot be confirmed.
Evidence
VirusTotal scanned the domain on 2026-10-19 and reported 16 detections out of 92 engines, labeling it as phishing, malicious or suspicious. Google Safe Browsing checked on 2026-10-25 and did not flag the site. Spamhaus DBL listed the domain as spam on 2026-10-25. Cloudflare Radar scanned on 2026-10-25 and marked it malicious with a malware category. urlscan.io captured the site on 2026-10-10, assigning a malicious engine score of 83 while the overall verdict was non‑malicious. PhishDestroy’s internal blocklist includes the domain as of 2026-10-25, and OTX shows three pulses referencing it.
Infrastructure
The domain was registered with eNom, LLC on 2026-01-29 and uses the nameservers ns1‑ns4.mysecurecloudhost.com. The recorded IP address is 134.122.44.253, belonging to DigitalOcean, LLC in Canada. TLS was provided by a Let's Encrypt certificate issued on 2026-10-09 and valid until 2027-01-07.
What to do
Treat earnpeak.net as untrusted and avoid entering any credentials, personal data, or downloading files from it. Organizations should block the domain at the network perimeter and review access logs for connections to the recorded IP address. Users who may have reused passwords on other sites should change those passwords.
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.
Open report Page code check by a separate monitor · 0 / 100 · 2026-10-28 07:20 UTC
This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
Heuristic score
0
Analyzed at
2026-10-28T07:20:12Z
Source timestamp
2026-10-28 08:20:12
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
earnpeak.net — Suspicious Domain
AI description
PhishDestroy flags earnpeak.net as a suspicious domain after multiple vendor detections, though no malicious content was observed in scans.
AI summary
Overview PhishDestroy listed earnpeak.net as a suspicious domain based on multiple vendor detections. The site returned HTTP 200 on 2026-10-25 but no page title was recorded. PhishDestroy first saw the domain on 2026-10-25, 269 days after its registration on 2026-01-29. How the scam works The vendor detections associated with earnpeak.net include phishing, malware and spam labels, which are common indicators of fraudulent or malicious sites. No specific malicious payload or credential‑stealing page was captured in the available scans, so the exact technique cannot be confirmed. Evidence VirusTotal scanned the domain on 2026-10-19 and reported 16 detections out of 92 engines, labeling it as phishing, malicious or suspicious. Google Safe Browsing checked on 2026-10-25 and did not flag the site. Spamhaus DBL listed the domain as spam on 2026-10-25. Cloudflare Radar scanned on 2026-10-25 and marked it malicious with a malware category. urlscan.io captured the site on 2026-10-10, assigning a malicious engine score of 83 while the overall verdict was non‑malicious. PhishDestroy’s internal blocklist includes the domain as of 2026-10-25, and OTX shows three pulses referencing it. Infrastructure The domain was registered with eNom, LLC on 2026-01-29 and uses the nameservers ns1‑ns4.mysecurecloudhost.com. The recorded IP address is 134.122.44.253, belonging to DigitalOcean, LLC in Canada. TLS was provided by a Let's Encrypt certificate issued on 2026-10-09 and valid until 2027-01-07. What to do Treat earnpeak.net as untrusted and avoid entering any credentials, personal data, or downloading files from it. Organizations should block the domain at the network perimeter and review access logs for connections to the recorded IP address. Users who may have reused passwords on other sites should change those passwords. Useful links urlscan.io scan and screenshot: https://urlscan.io/result/01a12586-ca2a-75ba-8512-4ca78c32033f/ Cloudflare Radar report: https://radar.cloudflare.com/scan/003211a0-557e-41c6-b459-bb8f567c765c Stored capture screenshot: https://urlscan.io/screenshots/01a12586-ca2a-75ba-8512-4ca78c32033f.png Cloudflare Radar screenshot (2026-10-25T14:26:16Z): https://screenshots.phishdestroy.io/cf/003211a0-557e-41c6-b459-bb8f567c765c.png URLScan screenshot (2026-10-09T06:30:23Z): https://screenshots.phishdestroy.io/us/01a11f5a-e9f4-7728-87c5-b59eb801dedc.png URLScan capture report: https://urlscan.io/result/01a11f5a-e9f4-7728-87c5-b59eb801dedc/ URLScan screenshot (2026-10-09T12:00:13Z): https://screenshots.phishdestroy.io/us/01a12088-dd20-713c-8364-81d1802c9ef5.png URLScan capture report: https://urlscan.io/result/01a12088-dd20-713c-8364-81d1802c9ef5/ URLScan screenshot (2026-10-25T14:26:04Z): https://screenshots.phishdestroy.io/us/01a17374-37c5-7068-ad48-f31eea424c74.png URLScan capture report: https://urlscan.io/result/01a17374-37c5-7068-ad48-f31eea424c74/ VirusTotal report: https://www.virustotal.com/gui/domain/earnpeak.net Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=earnpeak.net Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/ Site owner? Request a review: https://phishdestroy.io/appeals/
PhishDestroy rates earnpeak.net as critical risk (evidence score 98/100) from the recorded evidence; it was first recorded on 2026-10-25. Stored VirusTotal result: 16/92 engines flagged. Malicious: 12. Suspicious: 4. Analysis time (as stored): 2026-10-19 07:47 UTC. Retrieved (as stored): 2026-10-25 20:42 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Is earnpeak.net safe to connect a wallet?
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on earnpeak.net. A confirmed blockchain transaction cannot be reversed.
What should I do if I used earnpeak.net?
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.
IP Reputation134.122.44.2530/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worseThis IP address has a low abuse score, but the domain itself is recognized as phishing.0 reportschecked 2026-10-25last reported · outside the counted period
Issued by Let's Encrypt / YE2· stored validity ends in 45 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
134.122.44.253
Network ASN
AS14061
AS name
DIGITALOCEAN-ASN - DigitalOcean, LLC, US
Organization
DigitalOcean, LLC
Observed location
Toronto, CA
Server header
nginx/1.18.0 (Ubuntu)
Nameservers 4
ns1.mysecurecloudhost.com
ns2.mysecurecloudhost.com
ns3.mysecurecloudhost.com
ns4.mysecurecloudhost.com
SOA
nsname: ns1.mysecurecloudhost.com
hostmaster: servers.mysecurecloudhost.com
serial: 2026100806
refresh: 3600
retry: 1800
expire: 1209600
minttl: 86400
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YE2
Valid from
2026-10-09 00:59:54
Valid until
2027-01-07 00:59:53
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintaf3b40833c3aae5d7d5dbaba4a87a22ec62afe5cd4b47631830e9da3ca55bbcdCertificate names · 1 SAN
earnpeak.net
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
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:57 UTC.
Recorded events: 11. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Supporting signal — Shares a page feature, infrastructure or a collector label; not proof of one operator.
Discovery only — Same registrar or CDN edge: listed for navigation, not evidence of a link.
Each spoke is one reason a domain is linked to this report. Node size marks VirusTotal detections, dashed nodes are already offline, and the full lists follow below. Full list of related reports
Content matches8
Same favicon file hash, or a recorded page title that starts with the same 20 characters. A content match does not establish a shared phishing kit or owner.
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 earnpeak.net)
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.