Skip to security report
Domain security and threat intelligence
bigfoodie.shop favicon

bigfoodie.shop

“Facebook | Facebook”

Registrar
Dynadot
Resolved IP
195.96.130.235
Registered
May 27, 2026
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 12/92 Automated brand label: Facebook
Oct 16, 2026
API
This domain has been flagged as malicious
Security engines reporting a detection: 12. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Domain age
Source evidenceVirusTotal 12 / 92 5 sources

VirusTotal

12 / 92 engine detections

Open report

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Critical
VirusTotal
12 / 92
Page captures
3

PhishDestroy threat report

Overview

bigfoodie.shop is an impersonation phishing page that poses as Facebook and targets people with Facebook accounts. PhishDestroy first detected it on 2026-10-16. As of 2026-10-19 the site was online and serving its phishing content.

How the scam works

The page carries the title "Facebook | Facebook" so that a visitor arriving from a link sees what looks like a genuine Facebook page. Pages of this kind typically show a copied login or account-verification screen and capture whatever the victim types, usually an email or phone number, a password and sometimes a two-factor code. With those credentials, operators can take over the account. They then use it to message the victim's contacts with further lures, run fraudulent ads, or resell access. The domain name suggests an online shop rather than a social network, and urlscan.io additionally flagged it as a fake shop, while PhishDestroy classifies it as Facebook impersonation.

Evidence

On VirusTotal, 12 of 92 security engines flagged the domain as of 2026-10-19. The flagging vendors include alphaMountain.ai, BitDefender, CRDF, CyRadar, Forcepoint ThreatSeeker, Fortinet, G-Data and Gridinsoft. urlscan.io returned a malicious verdict and marked the site as a fake shop. The domain is listed on the PhishDestroy blocklist.

Infrastructure

The domain was registered on 2026-05-27 through Dynadot Inc., less than five months before it was detected serving phishing content. It is hosted at IP 195.96.130.235 on the Malakmadze Web LLC network in the US. The site uses a TLS certificate from Let's Encrypt (YE1), so the padlock in the browser says nothing about whether the site is legitimate.

What to do

If you opened this site but typed nothing, close it and do not return. If you entered your Facebook login, change your Facebook password immediately from the official app or by typing the address yourself. Then turn on two-factor authentication and review active sessions so you can log out any devices you do not recognize. Change the same password anywhere else you reused it, and warn your contacts not to trust unusual messages sent from your account. Defenders should block the domain and IP 195.96.130.235 at the DNS, proxy and email gateway level, and search logs for users who visited it. Reports to the registrar and hosting provider help speed up takedown.

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 3 captures

Observed page title
Facebook | Facebook
Automated brand references
Facebook
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 64 days

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Fakeshop report ↗
IP Reputation abuse score 0/100 0 reports checked Oct 16, 2026
Registrar Dynadot US(US)
RegistrationCreated May 27, 2026 (145d) — Expires May 27, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 16, 2026
DOM Analysisanalyzed Oct 16, 2026score 88/1001 brand signal
Submitted URLhttp://bigfoodie.shop/
Favicon Hash
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
195.96.130.235
Network ASN
AS199242
Organization
HMZ Web Hosting Co
Observed location
Los Angeles, US

Nameservers 2

  • braelyn.ns.cloudflare.com
  • colin.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-09-24 20:27:23
Valid until
2026-12-23 20:27:22
Validity
Within stored validity dates
Collection time
2026-10-16 01:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprintc99761cb28683b4a0d64ddb5cfdfcecb14420db3d162d1343bf7f58772f7b946

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-19 10:47:29 UTC

Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-19 10:47:29 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-19 10:47:29 UTC last content: 2026-10-19 10:47:29 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
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

12 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 0 detections
alphaMountain.ai
BitDefender
CRDF
CyRadar
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Sophos
URLQuery

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of bigfoodie.shop · checked Oct 16, 2026

63
Needs Work
Performance
FCP
2.92s
First Contentful Paint
LCP
7.96s
Largest Contentful Paint
CLS
0.027
Cumulative Layout Shift
TBT
256ms
Total Blocking Time
SI
4.5s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://bigfoodie.shop/
Final URL: https://bigfoodie.shop/
Facebook | Facebook
Goza de los sabores más destacados del sector ✔ Calidad superior en cada producto ✅ Entregas en 24/48h ✅ ¡Forma parte de la BIFAM! ✅
Response
HTTP 200
HTML body
297.1 KB
Compressed
51.6 KB
Links
19 internal · 0 external
Detected technologies
react
Selected response headers
Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
Security headers present
X-Frame-OptionsX-Content-Type-OptionsX-XSS-ProtectionReferrer-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Open Graph title: Facebook
Open Graph description: Goza de los sabores más destacados del sector ✔ Calidad superior en cada producto ✅ Entregas en 24/48h ✅ ¡Forma parte de la BIFAM! ✅
Twitter card: summary_large_image
Saved response-header values · 13
Alt-Svc
h3=":443"; ma=2592000
Cache-Control
private, no-cache, no-store, max-age=0, must-revalidate
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Fri, 16 Oct 2026 00:04:22 GMT
Link
; rel=preload; as="style"
Referrer-Policy
strict-origin-when-cross-origin
Transfer-Encoding
chunked
Vary
RSC, Next-Router-State-Tree, Next-Router-Prefetch, Next-Router-Segment-Prefetch, Accept-Encoding
Via
1.1 Caddy
X-Content-Type-Options
nosniff
X-Frame-Options
SAMEORIGIN
X-XSS-Protection
1; mode=block

Values retained by the collector; long values may be shortened during collection.

Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history10

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unavailable→Reachable

  2. Availability monitor · Recorded state

    Reachable→Unavailable

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unavailable→Reachable

  5. Availability monitor · Recorded state

    Reachable→Unavailable

Earlier observations 5
  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unavailable→Reachable

  4. Availability monitor · Recorded state

    Reachable→Unavailable

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    12/92 engine detections

    View source
  3. URLScan

    Page captured

    View source
  4. Added to PhishDestroy

    bigfoodie.shop

    View source

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

bigfoodie.shop

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked 0 stored notification records Last known active

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Official reporting routes

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 →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

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 bigfoodie.shop)
  • 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)
  • Europol — European cybercrime reporting (EU)
  • 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

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
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.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/bigfoodie.shop"
  title="PhishDestroy threat report for bigfoodie.shop"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>