Skip to security report
kv-cont-blared.pages.dev favicon
Domain security and threat intelligence

kv-cont-blared.pages.dev

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

On 2026-10-04, kv-cont-blared.pages.dev displayed a Facebook Business Help Center-branded support page. The interface features a heading asking how the service can help and states that more information is needed to address user issues. A central form contains a section titled most common issues with a radio button option labeled I need to contact the support team. Visitors can select this option and click a blue Next button to proceed through the form.

Page title: “Business Help Center | Privacy Policy”

More about the sources
Recorded security signals

Stored VirusTotal result: 20/92 engines flagged. Analysis time (as stored): 2026-11-14 18:00 UTC. Retrieved (as stored): 2026-11-16 22:30 UTC. Use caution — do not enter credentials or personal information.

VirusTotal detections: 20/92 Last known active
Resolved IP
Canada172.66.47.150Cloudflare, Inc. · CDN
First seen by PhishDestroy
2026-10-04
Page captures
open gallery
2026-10-04 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 kv-cont-blared.pages.dev on 2026-10-04. Stored VirusTotal result: 20/92 engines flagged. Analysis time (as stored): 2026-11-14 18:00 UTC. Retrieved (as stored): 2026-11-16 22:30 UTC. Risk: critical (evidence score 100/100). Status: Reachable · access restricted. Hosting: Cloudflare, Inc. Do not enter credentials or connect a wallet.

Critical
Status
Reachable · access restricted
VirusTotal
20 / 92
Hosting
Canada172.66.47.150Cloudflare, Inc. · CDN
Page captures
1

Stored capture capture · 2026-10-04 01:01 UTC · SHA-256 92ee5c3c…6238535

PhishDestroy analysis, reviewed version

On 2026-10-04, kv-cont-blared.pages.dev displayed a Facebook Business Help Center-branded support page. The interface features a heading asking how the service can help and states that more information is needed to address user issues. A central form contains a section titled most common issues with a radio button option labeled I need to contact the support team. Visitors can select this option and click a blue Next button to proceed through the form.

The page uses a blue abstract geometric banner across the top and presents a clean white content area below for user interaction. It prompts visitors to submit details regarding their support inquiries through the provided interface options.

Source evidenceVirusTotal 20 / 92 5 sources

VirusTotal

20 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 13 fields
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

Source
VirusTotal
Result state
observed
Numerator
20
Denominator
92
Vendors
ChainPatrol, Criminal IP, alphaMountain.ai, BitDefender, CyRadar, ESET, Emsisoft, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Kaspersky, Lionic, Netcraft, SafeToOpen, SOCRadar, Sophos, URLQuery, VIPRE, Webroot
Observed at
2026-11-14 18:00:02
Checked at
2026-11-16 23:30:10
Fetched at
2026-11-16 22:30:11

URLScan

Malicious

SHA-256 4856138c…1419892

Open report
URLScanOriginal source recordObserved: 20 fields
Separate monitor record · 2026-11-17 04:30 UTC

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

UUID
01a1046d-b298-76f8-abdf-471e55285079
Score
100
Malicious
✓
Result at
2026-11-17T04:30:53Z
Source timestamps
Urlscan result at: 2026-11-17 05:30:53
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
kv-cont-blared.pages.dev Facebook-branded support center page
AI description
PhishDestroy records a Facebook-branded support form page hosted at kv-cont-blared.pages.dev to gather user issues.
AI summary
On 2026-10-04, kv-cont-blared.pages.dev displayed a Facebook Business Help Center-branded support page. The interface features a heading asking how the service can help and states that more information is needed to address user issues. A central form contains a section titled most common issues with a radio button option labeled I need to contact the support team. Visitors can select this option and click a blue Next button to proceed through the form. The page uses a blue abstract geometric banner across the top and presents a clean white content area below for user interaction. It prompts visitors to submit details regarding their support inquiries through the provided interface options.
AI generated by
threat-v6-gemini
AI generated at
2026-11-16T22:29:35Z
Revision
0c261655942e59ca0a9e69462fe7bc7236c41880e96a37722870bfc490f21f39
Mode
reviewed
Interpretation
Selected public package; 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
This website does not have many visitors This website is being iframed by another website This website is using a (free) website platform IPQS flagged this website for Phishing IPQS has flagged this website as suspicious
According to the SSL check the certificate is valid

Questions about kv-cont-blared.pages.dev

Is kv-cont-blared.pages.dev legit?

PhishDestroy rates kv-cont-blared.pages.dev as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-10-04. Stored VirusTotal result: 20/92 engines flagged. Analysis time (as stored): 2026-11-14 18:00 UTC. Retrieved (as stored): 2026-11-16 22:30 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is kv-cont-blared.pages.dev safe to connect a wallet?

Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on kv-cont-blared.pages.dev. A confirmed blockchain transaction cannot be reversed.

What should I do if I used kv-cont-blared.pages.dev?

  • 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

Page captures (1)

All capture links and hashes (1)

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Facebook report ↗
IP Context Canada172.66.47.150 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider pages.dev
HTTP Status403 Forbidden
Elapsed Since First Report 44 days
What we count Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Reachable · access restricted.
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.
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-10-04
Submitted URLhttp://kv-cont-blared.pages.dev/help/contact/317928204491396%25252525252525252525252CN/A%25252525252525252525252Chttps%25252525252525252525253A/openphis
Observed page title
Business Help Center | Privacy Policy
TLS Certificate
Issued by WE1 · stored validity ends in 35 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada172.66.47.150
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • adi.ns.cloudflare.com
  • karl.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
WE1
Valid from
2026-09-29 16:38:15
Valid until
2026-12-28 17:38:12
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintbdd6754a87502dc70ce18be2d0348abf33e8c71acd769398a3f99869fd1c81a7
Certificate names · 2 SANs
  • kv-cont-blared.pages.dev
  • *.kv-cont-blared.pages.dev

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

VirusTotal Analysis

20 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive result retrieved by PhishDestroy
ESET
VIPRE
G-Data
Lionic
Sophos
CyRadar
Webroot
Emsisoft
Fortinet
Netcraft
SOCRadar
URLQuery
Kaspersky
Gridinsoft
SafeToOpen
BitDefender
ChainPatrol
Criminal IP
alphaMountain.ai
Forcepoint ThreatSeeker
PageSpeed (mobile): 100

Google PageSpeed Insights — mobile performance audit of kv-cont-blared.pages.dev ·

100
Good
Performance
FCP
0.76 s
First Contentful Paint
LCP
0.76 s
Largest Contentful Paint
CLS
0.019
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
0.76 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
All stored data107
Open complete records

Captured network requests

Network requests: 11 SHA-256 hashes: 10 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-11-16 22:24 UTC.

Open this scan on URLScan 01a1046d-b298-76f8-abdf-471e55285079 ↗

Check for cloaking

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

Page titles differ

Our scanner could not complete this check.

Browser
Business Help Center | Privacy Policy
Crawler
Suspected Phishing | Cloudflare
kv-cont-blared.pages.dev
Stored observation history4

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

    Blocked

    Cloudflare antiphishing · Cloudflare · Phishing interstitial

  2. Availability monitor · Recorded state

    Blocked

    Cloudflare antiphishing · Cloudflare · Phishing interstitial

  3. Availability monitor · Recorded state

    Blocked

    Cloudflare antiphishing · Cloudflare · Phishing interstitial

  4. Domain monitor · Recorded state

    Reachable→Unavailable

All retained availability observations7
Open complete records

Threat Response Pipeline

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

Recorded events: 10. 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
    kv-cont-blared.pages.dev detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Automated brand label: Facebook · Forensic Evidence Collected · Content Observed Unavailable recorded
Publication & AvailabilityDestroyList Published · Time to First Unavailability · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Time to First Unavailability
    Hours from detection to the first unavailable observation: 1047
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

3 entries

Lifecycle

  1. Domain registered
  2. Added to PhishDestroy+2223 d 3 h
  3. VirusTotal analysis with detections+41 d 11 h
  1. VirusTotal

    20/92 engine detections

    +41 d 11 h
  2. Added to PhishDestroy

    kv-cont-blared.pages.dev

    +5 h 1 min
  3. URLScan

    Malicious

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.

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

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 kv-cont-blared.pages.dev)
  • 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/kv-cont-blared.pages.dev"
  title="PhishDestroy threat report for kv-cont-blared.pages.dev"
  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>