This page mimics the Meta Privacy Center, warning visitors that their ad account is scheduled for deletion and asking them to submit credentials. If you entered your password on this page, immediately change your real Facebook password and review your account security settings.
More about the sources
Recorded security signals
Stored VirusTotal result: 11/92 engines flagged. Malicious: 10. Suspicious: 1. Analysis time (as stored): 2026-11-22 04:49 UTC. Retrieved (as stored): 2026-11-22 15:32 UTC. Listed by external blocklists: OpenPhish. 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 reconciliation-alsafi-df09.s2485120.workers.dev on 2026-11-22. Stored VirusTotal result: 11/92 engines flagged. Malicious: 10. Suspicious: 1. Analysis time (as stored): 2026-11-22 04:49 UTC. Retrieved (as stored): 2026-11-22 15:32 UTC. Listed by external blocklists: OpenPhish. Risk: critical (evidence score 83/100). Registrar: Cloudflare. Do not enter credentials or connect a wallet.
URLScan capture · 2026-11-22 15:26 UTC · SHA-256 c9329e90…2a58954
PhishDestroy analysis, reviewed version
Meta privacy center layout and ad account warning
The page opens with a sidebar showing the Meta logo and "Privacy Center", alongside navigation options like "Privacy Policy" and "Settings". In the main content area, a red warning icon accompanies the headline "We have scheduled the deletion of your ad account and pages." The text claims that "unusual activity" was detected and warns that the visitor has twenty-four hours to resolve the issue. An illustration features a smartphone surrounded by security icons, followed by a section titled "What you can do to request a review:". Bullet points instruct users to ensure complete information, provide verification codes, and upload documents. A prominent blue button at the bottom reads "Request Review" to capture visitor inputs.
Credential collection and external form submission
The interface is hosted on a Cloudflare Workers subdomain, utilizing a URL structure typical of rapidly deployed infrastructure. It features an external form post targeting facebook.com alongside active password fields designed to harvest user credentials under the guise of an account review. urlscan classified the page as malicious, and 10 of 92 engines on VirusTotal flagged it on 22 Nov 2026. Vendors like ESET, Fortinet and Sophos classify the URL as malicious, providing concrete support for the assessment that the page is built to capture login details rather than service a legitimate Meta review request.
Recommended precautions for visitors
Official Meta notices regarding account status will always appear within the legitimate domain at facebook.com rather than on third-party worker subdomains. If you visited this link and submitted your password or other personal details, treat your account as compromised immediately. Log out of all active sessions, change your password, and enable two-factor authentication if it was not already active.
Source evidenceVirusTotal 11 / 924 sources
SourceResultRecorded · UTCOpen
VirusTotal
11 / 92 engine detections
Analysis:
Open report VirusTotalOriginal source recordObserved: 15 fields
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.
reconciliation-alsafi-df09.s2485120.workers.dev mimics a Meta privacy center page warning of ad account deletion, flagged by urlscan and 10 VirusTotal engines.
AI summary
Meta privacy center layout and ad account warning The page opens with a sidebar showing the Meta logo and "Privacy Center", alongside navigation options like "Privacy Policy" and "Settings". In the main content area, a red warning icon accompanies the headline "We have scheduled the deletion of your ad account and pages." The text claims that "unusual activity" was detected and warns that the visitor has twenty-four hours to resolve the issue. An illustration features a smartphone surrounded by security icons, followed by a section titled "What you can do to request a review:". Bullet points instruct users to ensure complete information, provide verification codes, and upload documents. A prominent blue button at the bottom reads "Request Review" to capture visitor inputs. Credential collection and external form submission The interface is hosted on a Cloudflare Workers subdomain, utilizing a URL structure typical of rapidly deployed infrastructure. It features an external form post targeting facebook.com alongside active password fields designed to harvest user credentials under the guise of an account review. urlscan classified the page as malicious, and 10 of 92 engines on VirusTotal flagged it on 22 Nov 2026. Vendors like ESET, Fortinet and Sophos classify the URL as malicious, providing concrete support for the assessment that the page is built to capture login details rather than service a legitimate Meta review request. Recommended precautions for visitors Official Meta notices regarding account status will always appear within the legitimate domain at facebook.com rather than on third-party worker subdomains. If you visited this link and submitted your password or other personal details, treat your account as compromised immediately. Log out of all active sessions, change your password, and enable two-factor authentication if it was not already active.
Questions about reconciliation-alsafi-df09.s2485120.workers.dev
Is reconciliation-alsafi-df09.s2485120.workers.dev a real Meta page?
No, this is not the official site. Real Meta security notifications and privacy center tools are hosted exclusively on official domains like facebook.com.
What happens if I clicked Request Review and entered my password?
The page sends your submitted credentials directly to an external endpoint controlled by whoever deployed the worker script. You should immediately log into your real Facebook account to change your password and terminate unauthorized sessions.
Why does the page claim my ad account is scheduled for deletion?
It uses a fabricated urgency tactic involving community standards violations to frighten you into acting quickly without verifying the URL in your address bar.
URLScan · 2026-11-22 1 / 3 Used in the analysisSource file SHA-256: c9329e90…2a58954SHA-256 of the prepared copy given to the model: b43bc757…c35742aStored capture 2 / 3 Cloudflare Radar 3 / 3
SourceURLScan · 2026-11-22
Recorded
StateStored capture
HTTP status200
Final URLhttps://reconciliation-alsafi-df09.s2485120.workers.dev/analysis_workspace/
Edge-IP reputation is not attributed to this domain.
Nameservers 2
clyde.ns.cloudflare.com
sofia.ns.cloudflare.com
TLS certificate
Issuer
YE1
Valid from
2026-11-21 11:21:31
Valid until
2027-02-19 11:21:30
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint154510bdd733fba3f66f53f2d3f4c3c743dc8c72ac26ed87b5256294b30284f6Certificate names · 2 SANs
*.s2485120.workers.dev
s2485120.workers.dev
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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-22 15:28 UTC.
Loads saved data; the suspicious site is not opened.
Captured network requests
#
Network request
HTTP method · status
Type
Uncompressed size
Response body SHA-256
Stored observation history1
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Domain monitor · First collection record
Reachable
All retained availability observations0
Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.
No retained observations are recorded.
Threat Response Pipeline
Discovery · recorded
Analysis · recorded
Monitoring · recorded
Recorded events: 8. 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.
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 reconciliation-alsafi-df09.s2485120.workers.dev)
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.