Skip to security report
whatspp.online favicon
Domain security and threat intelligence

whatspp.online

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

PhishDestroy first recorded whatspp.online on 2026-08-01. Stored VirusTotal result: 17/92 engines flagged. Analysis time (as stored): 2026-10-15 03:06 UTC. Retrieved (as stored): 2026-10-26 02:10 UTC.

Page title: “https://www.whatspp.online/”

More about the sources
Recorded security signals

Stored VirusTotal result: 17/92 engines flagged. Analysis time (as stored): 2026-10-15 03:06 UTC. Retrieved (as stored): 2026-10-26 02:10 UTC. Use caution — do not enter credentials or personal information.

VirusTotal detections: 17/92 Spamhaus DBL: phishing domain
Registrar
REGISTER S.P.A
Resolved IP
United States216.239.32.21Google LLC
Registered
2026-06-27
First seen by PhishDestroy
2026-08-01
URLQuery
detections
Page captures
open gallery
Domain age
registered 2026-06-27 according to RDAP · source data differ
2026-08-01

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

Analysis

Domain summary

PhishDestroy first recorded whatspp.online on 2026-08-01. Stored VirusTotal result: 17/92 engines flagged. Analysis time (as stored): 2026-10-15 03:06 UTC. Retrieved (as stored): 2026-10-26 02:10 UTC. Risk: critical (evidence score 100/100). Registrar: REGISTER S.P.A. Status: Content unavailable. Hosting: Google LLC. Do not enter credentials or connect a wallet.

Critical
Status
Content unavailable
VirusTotal
17 / 92
Hosting
United States216.239.32.21Google LLC
Registrar
REGISTER S.P.A
Registered
2026-06-27
Page captures
10

PhishDestroy analysis, earlier unreviewed version

The domain whatspp.online was registered on 27 June 2026 through the registrar REGISTER S.P.A. and currently resolves to the IP address 216.239.32.21, served by the nameservers ns1.amenworld.com and ns2.amenworld.com. As of the report date, 1 August 2026, the domain is listed on two independent phishing blocklists, PhishDestroy and OpenPhish, indicating that it has been observed in active phishing campaigns. VirusTotal analysis shows that 13 of 91 security vendors have flagged the domain as malicious, reinforcing the blocklist evidence.

The domain remains active, and its risk level is classified as high. No additional public intelligence such as SSL certificate details, HTTP response codes, or page titles has been disclosed, limiting the depth of technical fingerprinting. The combination of recent registration, presence on reputable blocklists, and multi‑vendor detection suggests a purpose‑built infrastructure for credential harvesting or related fraudulent activity.

Defenders should continue to block the domain at network perimeters, update endpoint protection signatures to include the observed detection count, and monitor DNS queries for the associated IP and nameserver pair. Threat hunters may also query the registrar for any further registration changes and consider sinkholing the IP address if operationally feasible. Continuous re‑evaluation is advisable, as additional indicators such as content analysis or SSL information may emerge in subsequent investigations.

Source evidenceVirusTotal 17 / 92 7 sources

VirusTotal

17 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 13 fields
Separate collector summary

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.

Source
VirusTotal
Numerator
13
Denominator
91
Vendors
alphaMountain.ai, BitDefender, CRDF, CSIS Security Group, CyRadar, Emsisoft, Fortinet, G-Data, Lionic, Netcraft, SOCRadar, Sophos, Webroot
Checked at
2026-08-01 20:14:09

Spamhaus DBL

phishing domain

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
whatspp.online — Generic Phishing Investigation Report
AI description
Security analysis of whatspp.online covers observed phishing indicators, infrastructure evidence, current status, and defensive guidance.
AI summary
The domain whatspp.online was registered on 27 June 2026 through the registrar REGISTER S.P.A. and currently resolves to the IP address 216.239.32.21, served by the nameservers ns1.amenworld.com and ns2.amenworld.com. As of the report date, 1 August 2026, the domain is listed on two independent phishing blocklists, PhishDestroy and OpenPhish, indicating that it has been observed in active phishing campaigns. VirusTotal analysis shows that 13 of 91 security vendors have flagged the domain as malicious, reinforcing the blocklist evidence. The domain remains active, and its risk level is classified as high. No additional public intelligence such as SSL certificate details, HTTP response codes, or page titles has been disclosed, limiting the depth of technical fingerprinting. The combination of recent registration, presence on reputable blocklists, and multi‑vendor detection suggests a purpose‑built infrastructure for credential harvesting or related fraudulent activity. Defenders should continue to block the domain at network perimeters, update endpoint protection signatures to include the observed detection count, and monitor DNS queries for the associated IP and nameserver pair. Threat hunters may also query the registrar for any further registration changes and consider sinkholing the IP address if operationally feasible. Continuous re‑evaluation is advisable, as additional indicators such as content analysis or SSL information may emerge in subsequent investigations.
AI generated by
cerebras
AI generated at
2026-08-01T18:14:16Z
Revision
c99f26b1b2a196d5f54c5f9ebee2cb4f1666286b2095349b169bc042a2fc7871
Mode
stored
Interpretation
Earlier stored analysis, not reviewed; text generation time is separate from source observation dates.

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing

Questions about whatspp.online

Is whatspp.online legit?

PhishDestroy rates whatspp.online as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-08-01. Stored VirusTotal result: 17/92 engines flagged. Analysis time (as stored): 2026-10-15 03:06 UTC. Retrieved (as stored): 2026-10-26 02:10 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is whatspp.online safe to connect a wallet?

Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on whatspp.online. A confirmed blockchain transaction cannot be reversed.

What should I do if I used whatspp.online?

  • 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.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Page captures (10)

All capture links and hashes (10)
Observed page title
https://www.whatspp.online/
TLS Certificate
Issued by Google Trust Services · stored validity ends in 54 days
whatspp.online: caution — Flagged by Spamhaus DBL, 13/91 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card whatspp.online: caution — Flagged by Spamhaus DBL, 13/91 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v 461881636b25

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 97 report ↗
IP Reputation United States216.239.32.21 0/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worse This IP address has a low abuse score, but the domain itself is recognized as phishing. 5 reports PhishingPort Scan checked 2026-08-01 last reported
Registrar REGISTER S.P.A
Hosting abuse contact network-abuse@google.com Google LLC · AS15169
RegistrationCreated 2026-06-27 (147d) — Expires 2027-06-27
Registrant countryMorocco VirusTotal WHOIS
Registrant1f8f4166599d23ee261945b3002a5065s@ VirusTotal WHOIS
Time to First Unavailability 4 days
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First Detected2026-08-01
Submitted URLhttp://whatspp.online/
Favicon Hash
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

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.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States216.239.32.21
Network ASN
AS15169
Organization
Google LLC
Observed location
United StatesMountain View, US
Server header
scaffolding on HTTPServer2

Nameservers 2

  • ns1.amenworld.com
  • ns2.amenworld.com

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services
Valid from
2026-06-27 14:16:48
Valid until
2026-09-25 15:04:58
Hostname match
No
Validity
Stored certificate expired
Collection time
2026-08-01 19:02 UTC
Collection source
PhishDestroy collector
Certificate fingerprint5b4f4c3a3032bcfb4524be8d55619ec1bdb4ece22ec36cdf6360d2de2f58fbba
Certificate names · 1 SAN
  • www.whatspp.online

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-11-21 18:03 UTC

The domain no longer resolves in DNS.

Technical details
Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN
RDAP registration
Observed timeline last reachable: 2026-08-03 10:54 UTC current episode first observed: 2026-09-30 16:14 UTC observed RIP window: 2026-08-03 10:54 UTC → 2026-09-30 16:14 UTC · 1,397.33h midpoint estimate ≈ 2026-09-01 13:34 UTC · precision very low · basis bounded
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.
Technologies · 5 identified
Open complete records

VirusTotal Analysis

17 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive result retrieved by PhishDestroy
CRDF
ESET
VIPRE
G-Data
Lionic
Sophos
CyRadar
Webroot
Fortinet
SOCRadar
Kaspersky
LevelBlue
Seclookup
BitDefender
alphaMountain.ai
CSIS Security Group
Forcepoint ThreatSeeker

Archived Evidence

Wayback Machine Snapshot
View Archive

Saved snapshots 1

PageSpeed (mobile): 71

Google PageSpeed Insights — mobile performance audit of whatspp.online ·

71
Needs Work
Performance
FCP
3.88 s
First Contentful Paint
LCP
5.28 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
39 ms
Total Blocking Time
SI
3.88 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
1397.33
Estimate basis
Bounded by observations
Estimate precision
very_low

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

All stored data115
Open complete records

Captured network requests

Network requests: 115 SHA-256 hashes: 111 URLScan scan:

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 03:20 UTC.

Open this scan on URLScan 019fbe8b-9d09-7309-9b8f-b310773078b8 ↗

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

whatspp.online
Saved result
Unreachable
Stored observation history24
Open complete records
All retained availability observations113
Open complete records

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · recorded

Recorded events: 14. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested recorded
  • Threat Ingested
    whatspp.online detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Cloudflare Radar: Malicious · Forensic Evidence Collected · Technical Analysis Recorded · Content Observed Unavailable recorded
Publication & AvailabilityDestroyList Published · Content Observed Unavailable · Time to First Unavailability recorded
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Content Observed Unavailable
    The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
  • Time to First Unavailability
    Hours from detection to the first unavailable observation: 100

Recorded activity

4 entries

Lifecycle

  1. Domain registered
  2. Added to PhishDestroy+35 d 4 h
  3. VirusTotal analysis with detections+74 d 8 h
  1. VirusTotal

    17/92 engine detections

    +74 d 8 h
  2. Wayback Machine

    Page archived

    +1 min
  3. URLScan

    Page captured

    +6 min
  4. Added to PhishDestroy

    whatspp.online

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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

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.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

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
  • 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 whatspp.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)
  • Europol — European cybercrime reporting (EU)
  • 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

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/whatspp.online"
  title="PhishDestroy threat report for whatspp.online"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>