VirusTotal
7 / 89
“Meta | Community Standards Violation”
On 2026-10-01, facebook-verify-fanpage.com returned an HTTP 502 status in a recorded check. The same domain was first observed on 2026-09-10, according to the recorded first-observation date.
The domain's registration date is recorded as 2026-09-08 with registrar Name.com, Inc. An SSL scan on 2026-09-10 identified the issuer as Let's Encrypt / YR2. VirusTotal recorded 7 detections across 89 scanners on 2026-09-12. OTX recorded 2 pulses on 2026-09-10, and the PhishDestroy internal listing is recorded as true.
The HTTP check, SSL scan, OTX pulses and VirusTotal results carry different observation dates, so a reader comparing them should note that each reflects only its own recorded moment. The PhishDestroy internal listing and the OTX pulses are separate recorded sources, and neither states a shared scope with the HTTP or SSL observations.
Anyone reviewing facebook-verify-fanpage.com should retain the dated records above so later checks can be compared against the same fields. Subsequent observations should be logged with their own dates rather than merged with the existing entries. During any review, avoid submitting sensitive information through the domain until the recorded status is better understood.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='facebook-verify-fanpage.com', port=80): Max retries exceeded with url: / (Caused by NewCon
Edge-IP reputation is not attributed to this domain.
dns1.p08.nsone.netdns2.p08.nsone.netdns3.p08.nsone.netdns4.p08.nsone.netLocation describes the IP network.
1e6e3476adcaba0f47571cef02218962fe543d3312eb0f2510190ccd88bfeae2Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
11 recorded events. 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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive