state-whatsapp.com presents a broken PHP error page that mimics the WhatsApp brand through its address while hiding its actual content. Visitors should avoid interacting with this domain and use the official whatsapp.com instead.
More about the sources
Recorded security signals
Stored VirusTotal result: 16/92 engines flagged. Malicious: 15. Suspicious: 1. Analysis time (as stored): 2026-11-11 20:37 UTC. Retrieved (as stored): 2026-11-18 03:03 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 state-whatsapp.com on 2026-11-18. Stored VirusTotal result: 16/92 engines flagged. Malicious: 15. Suspicious: 1. Analysis time (as stored): 2026-11-11 20:37 UTC. Retrieved (as stored): 2026-11-18 03:03 UTC. Risk: critical (evidence score 100/100). Registrar: GKG.Net. Status: Last known active. Hosting: Dimension Network & Communication Limited. Do not enter credentials or connect a wallet.
Critical
Status
Last known active
VirusTotal
16 / 92
Hosting
66.203.149.22Dimension Network & Communication Limited
URLScan capture · 2026-11-03 04:39 UTC · SHA-256 5071163f…3f70494
PhishDestroy analysis, reviewed version
Page layout and error output
The page at state-whatsapp.com displays a raw PHP error message rather than a functional web interface. At the top, the screen shows a bold "Fatal error: Uncaught Error: Call to member function execute() on bool in /www/wwwroot/one.deepnets.fyi/index.php:641" followed by a full stack trace detailing file paths and closure functions. No forms, buttons, or branding elements load successfully because the underlying script execution halts immediately. The address itself incorporates the WhatsApp brand name to appear connected to the messaging service, even though the true platform operates exclusively at whatsapp.com. Visitors encountering this server fault should close the tab immediately, as broken application states often precede malicious payload delivery or credential collection once fixed.
Security evaluations and independent detections
Security scanners including ESET, BitDefender and Fortinet classify the URL as a threat, PhishDestroy scores the evidence against it at 75/100 (critical). This confirms the address served malicious operations despite its broken appearance, matching a larger pattern where improperly deployed scripts expose server paths while phishing campaigns are being prepared.
Shared server infrastructure and campaign patterns
The underlying hosting setup connects this address to a wider network of suspicious properties. Specifically, 202 other reported domains resolve to the same IP address and 273 use the same nameserver pair, pointing to a heavily reused hosting environment. Neighbouring domains such as cors-whatsapp.com, column-whatsapp.com and style-whatsapp.com reside on the same infrastructure. Additionally, its IP address has 7 abuse reports on AbuseIPDB (port scanning, hacking and brute force), further establishing the risky nature of the underlying network resources.
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 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
state-whatsapp.com — PHP error page on WhatsApp domain
AI description
state-whatsapp.com displays a raw PHP error screen while flagged by Spamhaus DBL and 16 VirusTotal engines. Do not interact with the page and use whatsapp.com.
AI summary
Page layout and error output The page at state-whatsapp.com displays a raw PHP error message rather than a functional web interface. At the top, the screen shows a bold "Fatal error: Uncaught Error: Call to member function execute() on bool in /www/wwwroot/one.deepnets.fyi/index.php:641" followed by a full stack trace detailing file paths and closure functions. No forms, buttons, or branding elements load successfully because the underlying script execution halts immediately. The address itself incorporates the WhatsApp brand name to appear connected to the messaging service, even though the true platform operates exclusively at whatsapp.com. Visitors encountering this server fault should close the tab immediately, as broken application states often precede malicious payload delivery or credential collection once fixed. Security evaluations and independent detections Security scanners including ESET, BitDefender and Fortinet classify the URL as a threat, PhishDestroy scores the evidence against it at 75/100 (critical). This confirms the address served malicious operations despite its broken appearance, matching a larger pattern where improperly deployed scripts expose server paths while phishing campaigns are being prepared. Shared server infrastructure and campaign patterns The underlying hosting setup connects this address to a wider network of suspicious properties. Specifically, 202 other reported domains resolve to the same IP address and 273 use the same nameserver pair, pointing to a heavily reused hosting environment. Neighbouring domains such as cors-whatsapp.com, column-whatsapp.com and style-whatsapp.com reside on the same infrastructure. Additionally, its IP address has 7 abuse reports on AbuseIPDB (port scanning, hacking and brute force), further establishing the risky nature of the underlying network resources.
No, state-whatsapp.com is not an official WhatsApp property. WhatsApp operates exclusively on whatsapp.com, and addresses combining brand names with unrelated words are typically used for deceptive purposes.
Why does state-whatsapp.com show a PHP error?
Spamhaus DBL lists it as phishing, 16 of 92 engines on VirusTotal flagged it on 11 Nov 2026, and 1 AlienVault OTX community report references it.
What should I do if I visited state-whatsapp.com?
Simply visiting a broken PHP error page does not expose your data unless you downloaded a file or entered credentials. Close the browser tab and navigate directly to whatsapp.com if you need messaging services.
IP Reputation66.203.149.2245/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worse7 reportsFTP Brute-ForceFraud VoIPPort ScanHackingBrute-ForceWeb App Attackchecked 2026-11-18last reported
Certificate fingerprint00d64e3b63c2994b1ccaa4c778643c5dd19e9ee11becc57bedf6cf9a6adf274fCertificate names · 1 SAN
state-whatsapp.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-11-22 11:14 UTC
RDAP registration
Observed timelinelast reachable: 2026-11-22 11:14 UTClast content: 2026-11-21 11:15 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.
Technologies · 1 identified
HSTS
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
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-11-18 02:31 UTC.
Recorded events: 11. 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
5 entries
Lifecycle
Domain registered
VirusTotal analysis with detections+26 d 4 h
Added to PhishDestroy+6 d 5 h
AlienVault OTX
1 community references
+3 d 17 h
Wayback Machine
Page archived
+41 min
Added to PhishDestroy
state-whatsapp.com
same minute
URLScan
Page captured
+6 d 5 h
VirusTotal
16/92 engine detections
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.
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 matches4
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 state-whatsapp.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.