Skip to security report
bbllp.network favicon
Domain security and threat intelligence

bbllp.network

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

PhishDestroy first recorded bbllp.network on 2026-02-26. Stored VirusTotal result: 11/91 engines flagged.

More about the sources
Recorded security signals

Stored VirusTotal result: 11/91 engines flagged. Use caution — do not enter credentials or personal information.

VirusTotal detections: 11/91
Registrar
IndiaPDR
Resolved IP
United States104.21.112.1Cloudflare, Inc. · CDN
First seen by PhishDestroy
2026-02-26
OTX
community references
Page captures
open gallery
OTX: 24 refs 2026-02-26 CDN

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

Analysis

Domain summary

PhishDestroy first recorded bbllp.network on 2026-02-26. Stored VirusTotal result: 11/91 engines flagged. Risk: critical (evidence score 88/100). Registrar: PDR. Hosting: CLOUDFLARENET, US. Do not enter credentials or connect a wallet.

Critical
VirusTotal
11 / 91
Scam type (automated label)
Impersonation
Hosting
United States104.21.112.1Cloudflare, Inc. · CDN
Registrar
IndiaPDR
OTX
24 community refs
Page captures
2

PhishDestroy analysis, earlier unreviewed version

Analysis of bbllp.network indicates an active generic phishing infrastructure. The domain was registered on February 21, 2026 through PDR Ltd. d/b/a PublicDomainRegistry.com and is currently hosted behind Cloudflare (AS13335) with the IP address 104.21.112.1. The site serves over HTTP/3 and presents a Cloudflare challenge page titled "Just a moment..." while returning an HTTP 403 status code, suggesting that access is being intentionally blocked. The SSL certificate is issued by Google Trust Services / WE1, confirming a valid TLS layer. Reputation data shows a Gridinsoft trust score of 0/100 and the domain appears on one security blocklist. Two of ninety‑three VirusTotal scanners have flagged the domain, and it is listed as blocked by PhishDestroy. Nameservers earl.ns.cloudflare.com and melody.ns.cloudflare.com resolve the domain, consistent with the Cloudflare front‑end. While the exact phishing payload or targeted brand has not been disclosed, the combination of recent registration, low trust score, and detection by multiple security vendors supports a high‑risk classification. Defenders should add bbllp.network to URL and DNS blocklists, monitor for any resolution changes, and consider sinkholing the associated IP range if feasible. Continuous threat‑intel feeds should be consulted for any emerging indicators tied to this infrastructure.

Source evidenceVirusTotal 11 / 91 · OTX 24 references 7 sources

VirusTotal

11 / 91 engine detections

Retrieved / checked:
Open report

OTX

24 community references

Open report

URLScan

Page capture

Open report
URLScanOriginal source recordObserved: 17 fields
Separate monitor record

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

UUID
01988107-4b94-73c5-869e-e55babf5fdf3
Enriched at
2026-03-25T12:27:19Z
Source timestamps
Urlscan enriched at: 2026-03-25 13:27:19

PhishDestroy DOM

88 / 100 · heuristic score · 0 brand references · 1 classification

Content heuristic only; not the final score

Open report
Page code check by a separate monitor · 15 / 100 · 2026-04-10 19:21 UTC

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

Heuristic score
15
Analyzed at
2026-04-10T19:21:22Z
Source timestamp
2026-04-10 21:21:22
Technical metadata

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

AI title
bbllp.network: Confirmed Phishing Site
AI description
Analysis of bbllp.network indicates an active generic phishing infrastructure.
AI summary
Analysis of bbllp.network indicates an active generic phishing infrastructure. The domain was registered on February 21, 2026 through PDR Ltd. d/b/a PublicDomainRegistry.com and is currently hosted behind Cloudflare (AS13335) with the IP address 104.21.112.1. The site serves over HTTP/3 and presents a Cloudflare challenge page titled "Just a moment..." while returning an HTTP 403 status code, suggesting that access is being intentionally blocked. The SSL certificate is issued by Google Trust Services / WE1, confirming a valid TLS layer. Reputation data shows a Gridinsoft trust score of 0/100 and the domain appears on one security blocklist. Two of ninety‑three VirusTotal scanners have flagged the domain, and it is listed as blocked by PhishDestroy. Nameservers earl.ns.cloudflare.com and melody.ns.cloudflare.com resolve the domain, consistent with the Cloudflare front‑end. While the exact phishing payload or targeted brand has not been disclosed, the combination of recent registration, low trust score, and detection by multiple security vendors supports a high‑risk classification. Defenders should add bbllp.network to URL and DNS blocklists, monitor for any resolution changes, and consider sinkholing the associated IP range if feasible. Continuous threat‑intel feeds should be consulted for any emerging indicators tied to this infrastructure.
AI generated by
cerebras
AI generated at
2026-07-12T22:44:07Z
Revision
be720b630f617d203158adfa45cc2ba33370bda82d1df66badb3c5afdfdfee59
Mode
stored
Interpretation
Earlier stored analysis, not reviewed; text generation time is separate from source observation dates.

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

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Security Signals
SA Scamadviser Warnings 1/100
According to Tranco this site has a low rank We tried to analyze the content of the site but failed
The SSL certificate is valid

Questions about bbllp.network

Is bbllp.network legit?

PhishDestroy rates bbllp.network as critical risk (evidence score 88/100) from the recorded evidence; it was first recorded on 2026-02-26. Stored VirusTotal result: 11/91 engines flagged. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is bbllp.network safe to connect a wallet?

Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on bbllp.network. A confirmed blockchain transaction cannot be reversed.

What should I do if I used bbllp.network?

  • 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
  • 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
  • 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
  • Downloaded a file — do not open it and scan the device with security software

Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Separate monitor record

Page captures (2)

All capture links and hashes (2)
Observed page title
Nur einen Moment…
TLS Certificate
Issued by Google Trust Services / WE1
bbllp.network: caution — 11/91 VirusTotal engines. PhishDestroy risk score 88/100 (critical).
Social preview card bbllp.network: caution — 11/91 VirusTotal engines. PhishDestroy risk score 88/100 (critical). v e462abd914e1

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context United States104.21.112.1 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-02activeall-domainsblockchainblocklistcontentcryptocrypto scamcryptocurrencydestroylistdomainsdrainerfraudlive+4 more
Registrar PDR IN(IN)
RegistrationExpires 2026-08-05
Elapsed Since First Report 251 days
What we count Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First Detected2026-02-26
DOM Analysisanalyzed 2026-04-10score 88/100
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

Shared CDN edge
Resolved IP
United States104.21.112.1
Network ASN
AS13335
AS name
CLOUDFLARENET, US
Organization
Cloudflare, Inc.
Observed location
United StatesSan Francisco, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 1

  • melody.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-01-29 20:05:05
Valid until
2026-04-29 21:02:27
Hostname match
Yes
Validity
Stored certificate expired
Collection time
2026-03-15 08:10 UTC
Collection source
PhishDestroy collector
Certificate fingerprint51b5d3df60006a6e7207179ae11688826dd47bead8c4f9cc4ddf048acafcc29e
Certificate names · 2 SANs
  • bbllp.network
  • *.bbllp.network

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-11-21 18:03 UTC

The domain no longer resolves in DNS.

Technical details
Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN
RDAP registration
Observed timeline last reachable: 2026-11-04 12:05 UTC current episode first observed: 2026-11-04 22:21 UTC observed RIP window: 2026-11-04 12:05 UTC → 2026-11-04 22:21 UTC · 10.26h midpoint estimate ≈ 2026-11-04 17:13 UTC · precision medium · basis bounded
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 · 2 identified
Open complete records

VirusTotal Analysis

11 / 91 security vendors flagged this domain
View on VT
Last checked Previous stored snapshot: 13 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CyRadar
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
SOCRadar
Sophos
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
10.26
Estimate basis
Bounded by observations
Estimate precision
Medium

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

All stored data114
Open complete records

Captured network requests

Network requests: 23 SHA-256 hashes: 15 URLScan scan:

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-10-29 05:38 UTC.

Open this scan on URLScan 01988107-4b94-73c5-869e-e55babf5fdf3 ↗

Check for cloaking

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

No cloaking flag in this check

dns_nxdomain: no HTTP response; DNS NXDOMAIN recorded 2026-11-12 10:22:07.093838

bbllp.network
Saved result
Unreachable
Stored observation history29
Open complete records
Separate monitor HTTP observation

Source: domain_monitor. This stored snapshot does not establish current availability.

Observed · UTC
Recorded HTTP status
No response code recorded
Original source timestamp
2026-02-25 01:02:43
All retained availability observations126
Open complete records

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · recorded

Recorded events: 16. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested recorded
  • Threat Ingested
    bbllp.network detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · Cloudflare Radar Report · VirusTotal · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded · Content Observed Unavailable · Site Came Back Online · Content Observed Unavailable · Site Came Back Online · Cloudflare Radar Scan · Cloudflare Radar Scan · Content Observed Unavailable recorded
Publication & AvailabilityDestroyList Published · Time to First Unavailability recorded
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Time to First Unavailability
    Hours from detection to the first unavailable observation: 6018

Recorded activity

4 entries

Lifecycle

  1. Added to PhishDestroy
  2. First abuse report sent+1 h 0 min
  1. AlienVault OTX

    24 community references

    +70 d 7 h
  2. VirusTotal

    11/91 engine detections

    +153 d 15 h
  3. URLScan

    Page captured

    +26 d 14 h
  4. Added to PhishDestroy

    bbllp.network

How we investigate & report

Public scans, evidence and abuse channels

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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

Stored checks and requests

Content check

Status
Alive
Last checked
2026-03-04 19:15 UTC
All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Community reports

Reported by 1 community member, first seen 2025-08-06

Stored reports
1
Unique reported URLs
1
Accepted1

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

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.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

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.

  • 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 bbllp.network)
  • 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

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.

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/bbllp.network"
  title="PhishDestroy threat report for bbllp.network"
  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>