Stored VirusTotal result: 1/92 engines flagged. malicious: 0. suspicious: 1. Analysis time (as stored): 2026-10-28 19:56 UTC. Retrieved (as stored): 2026-10-28 20:03 UTC. Use caution — do not enter credentials or personal information.
PhishDestroy first recorded viprate.online on 2026-10-28. Stored VirusTotal result: 1/92 engines flagged. malicious: 0. suspicious: 1. Analysis time (as stored): 2026-10-28 19:56 UTC. Retrieved (as stored): 2026-10-28 20:03 UTC.
PhishDestroy first recorded viprate.online on 2026-10-28. Stored VirusTotal result: 1/92 engines flagged. malicious: 0. suspicious: 1. Analysis time (as stored): 2026-10-28 19:56 UTC. Retrieved (as stored): 2026-10-28 20:03 UTC. Risk: critical (72/100). Registrar: NameCheap. Status: Last known active. Hosting: CloudFLARENET-EU. Do not enter credentials or connect a wallet.
PhishDestroy’s intake on 2026-10-28 added viprate.online to its internal blocklist after a URLScan scan returned a malicious verdict. An earlier AI assessment on the same day observed no malicious content and labeled the site clean, noting only the recorded title “Viprate”. The page fetched on 2026-10-28 returned HTTP 200 and the recorded title was “Viprate”. No impersonation of a known brand or fake‑store elements were identified.
How the scam works
Because the domain is newly registered and has been flagged as suspicious, it could be used for typical phishing or credential‑harvesting attacks that rely on short‑lived sites to lure users. No concrete technique was observed on this page.
Evidence
VirusTotal’s analysis on 2026-10-28 reported one suspicious detection out of 92 engines, attributed to alphaMountain.ai. URLScan’s capture on 2026-10-28 gave a malicious verdict. Google Safe Browsing checked on 2026-10-28 did not flag the domain. PhishDestroy’s internal blocklist marks viprate.online as blocked, while external blocklists checked on that date returned zero matches and OTX showed no pulses.
Infrastructure
The domain was registered with NameCheap on 2026-10-26 and is set to expire on 2027-10-26. The recorded DNS entries listed Cloudflare‑provided A records such as 188.114.96.1 and AAAA records in the 2a06:98c1:3120:: range, and the domain used the Cloudflare name servers chloe.ns.cloudflare.com and todd.ns.cloudflare.com without DNSSEC. The TLS certificate observed was issued by Let’s Encrypt and was valid through 2027-01-25. Hosting was identified as the Cloudflare network (CloudFLARENET‑EU) located in Great Britain.
What to do
Visitors should avoid entering credentials or downloading files; if any credentials were submitted, change the associated passwords immediately. Defenders can block the exact domain viprate.online and monitor traffic to its recorded IP addresses, applying standard web‑filtering or intrusion‑detection rules.
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 Separate monitor score · 0 / 100 · 2026-10-28T20:22:17Z
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-28T20:22:17Z
Source timestamp
2026-10-28 21:22:17
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 summary
Overview PhishDestroy’s intake on 2026-10-28 added viprate.online to its internal blocklist after a URLScan scan returned a malicious verdict. An earlier AI assessment on the same day observed no malicious content and labeled the site clean, noting only the recorded title “Viprate”. The page fetched on 2026-10-28 returned HTTP 200 and the recorded title was “Viprate”. No impersonation of a known brand or fake‑store elements were identified. How the scam works Because the domain is newly registered and has been flagged as suspicious, it could be used for typical phishing or credential‑harvesting attacks that rely on short‑lived sites to lure users. No concrete technique was observed on this page. Evidence VirusTotal’s analysis on 2026-10-28 reported one suspicious detection out of 92 engines, attributed to alphaMountain.ai. URLScan’s capture on 2026-10-28 gave a malicious verdict. Google Safe Browsing checked on 2026-10-28 did not flag the domain. PhishDestroy’s internal blocklist marks viprate.online as blocked, while external blocklists checked on that date returned zero matches and OTX showed no pulses. Infrastructure The domain was registered with NameCheap on 2026-10-26 and is set to expire on 2027-10-26. The recorded DNS entries listed Cloudflare‑provided A records such as 188.114.96.1 and AAAA records in the 2a06:98c1:3120:: range, and the domain used the Cloudflare name servers chloe.ns.cloudflare.com and todd.ns.cloudflare.com without DNSSEC. The TLS certificate observed was issued by Let’s Encrypt and was valid through 2027-01-25. Hosting was identified as the Cloudflare network (CloudFLARENET‑EU) located in Great Britain. What to do Visitors should avoid entering credentials or downloading files; if any credentials were submitted, change the associated passwords immediately. Defenders can block the exact domain viprate.online and monitor traffic to its recorded IP addresses, applying standard web‑filtering or intrusion‑detection rules. Useful links urlscan.io scan and screenshot: https://urlscan.io/result/01a18411-eb5e-74ef-b0ea-ad9f3e22534c/ Cloudflare Radar report: https://radar.cloudflare.com/scan/ff72594d-bfaf-47f3-aa78-c49741fdca27 Stored capture screenshot: https://urlscan.io/screenshots/01a18411-eb5e-74ef-b0ea-ad9f3e22534c.png Cloudflare Radar screenshot (2026-10-28T20:03:39Z): https://screenshots.phishdestroy.io/cf/ff72594d-bfaf-47f3-aa78-c49741fdca27.png URLScan screenshot (2026-10-28T20:04:04Z): https://screenshots.phishdestroy.io/us/01a1841c-aab4-703f-b1fb-5c42d3b82ad0.png URLScan capture report: https://urlscan.io/result/01a1841c-aab4-703f-b1fb-5c42d3b82ad0/ VirusTotal report: https://www.virustotal.com/gui/domain/viprate.online Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=viprate.online Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/ Site owner? Request a review: https://phishdestroy.io/appeals/
PhishDestroy rates viprate.online as critical risk (72/100) from the recorded evidence; it was first recorded on 2026-10-28. Stored VirusTotal result: 1/92 engines flagged. malicious: 0. suspicious: 1. Analysis time (as stored): 2026-10-28 19:56 UTC. Retrieved (as stored): 2026-10-28 20:03 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Is viprate.online safe to connect a wallet?
This report does not record which wallet requests viprate.online makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.
What should I do if I used viprate.online?
It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you 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.
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.
Certificate fingerprintf8841a89eaeeca0d8c48c8f7d94c23e657eef315987ebbaef0143b9eba794640Certificate names · 2 SANs
*.viprate.online
viprate.online
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-16 12:03:49 UTC
RDAP registration
Observed timelinelast reachable: 2026-11-16 12:03:49 UTClast content: 2026-11-16 12:03:49 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.
Recorded subdomains1
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:52 UTC.
Recorded events: 9. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Pre-emptive Discovery & IngestionThreat Ingested1/1Recorded: 1 of 1
Threat Ingested
viprate.online detected and queued for full analysis
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. Silence is the scammer’s greatest advantage. Break it.
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.
If you made a payment, contact your bank or payment service through its official contacts as soon as possible. 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.
Scammers are criminals. Filing a report creates a legal record and helps protect others.
97-country directory
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.
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
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 viprate.online)
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.