facedook[.]services

PhishDestroy first recorded facedook.services on Mar 10, 2026. This English evidence brief is rebuilt from the current structured observations stored for the report. The current evidence score, computed from those stored observations, is 95/100.

The latest stored availability state is “Content unavailable” on Aug 3, 2026 at 01:10 UTC. This is a reachability snapshot, not proof of the cause of any outage, restriction, or status change.

VirusTotal returned 26 detections from 94 scanners in the stored check on Mar 11, 2026 at 05:02 UTC. The independent blocklist snapshot recorded 0 matches across 10 configured external sources on Aug 3, 2026 at 14:20 UTC. PhishDestroy's own listing is excluded from that count. A zero-match snapshot is not a safety verdict.

Other stored evidence. Google Safe Browsing stored a positive flag on Mar 10, 2026 at 13:59 UTC. AlienVault OTX stored 0 pulse references on Mar 10, 2026 at 13:59 UTC. OTX pulses are community-intelligence references, not vendor verdicts. Spamhaus DBL stored the result DBL_PHISH on Jul 14, 2026 at 02:32 UTC. A stored Cloudflare Radar snapshot labels the domain malicious. No source check timestamp is stored for this field. A URLScan capture is stored from Mar 26, 2026 at 11:11 UTC.

Stored context lists IP address 43.205.243.177, registration date Mar 10, 2026, apparent target Facebook. Except for the registration date, these fields do not share a source timestamp in this report and may change.

Treat these as stored, time-bound observations rather than a live safety guarantee. Source verdicts and reachability can change, and zero or missing vendor matches never prove that a domain is safe. Avoid interacting with the domain while uncertainty remains, and use the appeal process if this report is inaccurate.