facebook-verification-badge.com is an impersonation phishing site built around the Facebook brand. Its name targets page owners, creators and businesses who want the blue verification badge. PhishDestroy first flagged it on 2026-09-06. As of 2026-10-19 the domain was still alive and answering requests with a redirect, so it remains usable for phishing.
How the scam works
Badge-themed phishing usually starts with a message warning that a page will be restricted, or offering verification if the owner confirms their details. The victim is sent to a lookalike Facebook form that asks for login credentials, two-factor codes and sometimes ID documents or payment details. The attackers then take over the account, lock out the owner, and use the page for scams or resell it. The page title currently reads "404: NOT_FOUND", while we classify the domain as a Facebook impersonation phishing page.
Evidence
When VirusTotal last checked on 2026-09-17, 17 of 89 security engines flagged the domain. Those engines included BitDefender, ESET, Forcepoint ThreatSeeker, Criminal IP, alphaMountain.ai, CRDF, CyRadar and the Vietnamese anti-scam project Chong Lua Dao. That is broad agreement across unrelated vendors. Spamhaus lists the domain on its DBL with a phishing designation, which blocks it in many mail filters. It also appears in 4 AlienVault OTX threat pulses and on the PhishDestroy blocklist.
Infrastructure
The domain was registered through Name.com, Inc. on 2026-06-23, about 75 days before PhishDestroy detected it. That gap suggests it was set up in advance rather than used the moment it was registered. It resolves to an address on Amazon's network in the United States. Large cloud hosting like this lets operators move or rebuild a site quickly.
What to do
Facebook does not grant verification through outside websites, so treat any badge offer that leads here as fraudulent. If you entered your Facebook login, change the password right away and also change it anywhere else you reused it. Turn on or reset two-factor authentication, log out all unknown sessions in Security settings, and check that your recovery email and phone number are still yours. If you lost access, use Facebook's official hacked-account recovery flow. If you submitted ID or card details, contact your bank and watch for identity fraud. Security teams should block the domain at DNS and mail gateways, enforce the Spamhaus DBL listing, and warn social media managers about badge-verification lures.
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-10-19 22:35:00 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-19 22:35:00 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.
使用技術 · 2 identified
V
Vercel
PaaS
Vercel is a cloud platform for static frontends and serverless functions.
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.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
(US)
