Skip to security report
Redirect recorded cont17ct-vunari-biz-selor-kemra.pages.devweb.facebook.com Details
cont17ct-vunari-biz-selor-kemra.pages.dev favicon
Domain security and threat intelligence

cont17ct-vunari-biz-selor-kemra.pages.dev

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 cont17ct-vunari-biz-selor-kemra.pages.dev on 2026-11-22. Stored VirusTotal result: 20/92 engines flagged. Malicious: 19. Suspicious: 1. Analysis time (as stored): 2026-11-21 12:35 UTC. Retrieved (as stored): 2026-11-22 00:59 UTC.

Page title: “Meta for Business | Page Appeal”

More about the sources
Recorded security signals

Stored VirusTotal result: 20/92 engines flagged. Malicious: 19. Suspicious: 1. Analysis time (as stored): 2026-11-21 12:35 UTC. Retrieved (as stored): 2026-11-22 00:59 UTC. Use caution — do not enter credentials or personal information.

VirusTotal detections: 20/92 Last known active
Resolved IP
Canada188.114.96.3CloudFlare, Inc. · CDN
First seen by PhishDestroy
2026-11-22
Page captures
open gallery
2026-11-22 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 cont17ct-vunari-biz-selor-kemra.pages.dev on 2026-11-22. Stored VirusTotal result: 20/92 engines flagged. Malicious: 19. Suspicious: 1. Analysis time (as stored): 2026-11-21 12:35 UTC. Retrieved (as stored): 2026-11-22 00:59 UTC. Risk: critical (evidence score 95/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
Canada188.114.96.3CloudFlare, Inc. · CDN
Page captures
9

Recorded source summary

cont17ct-vunari-biz-selor-kemra.pages.dev is a tenant hostname on Cloudflare, not a separately registered domain. PhishDestroy first observed the hostname on Nov 22, 2026. Stored content metadata identifies Facebook as the apparent target. The captured page title is “Meta for Business | Page Appeal”. Page analysis recorded additional brand references to Instagram. Current evidence score: 95/100 (critical).

Positive findings are stored from 3 sources: VirusTotal, Cloudflare Radar, and URLScan. VirusTotal recorded 20 detections among 92 engines: DNS8, ESET, VIPRE, G-Data, Lionic, Sophos, CyRadar, Webroot, Emsisoft, Fortinet, Netcraft, SOCRadar, URLQuery, Kaspersky, Gridinsoft, MalwareURL, BitDefender, Criminal IP, alphaMountain.ai, Forcepoint ThreatSeeker on Nov 21, 2026 at 12:35 UTC. Cloudflare Radar classified the hostname as malicious and assigned the categories security threats and phishing. URLScan returned a malicious verdict with score 100; scan metadata linked the capture to Facebook and assigned phishing as its category on Nov 22, 2026 at 04:30 UTC.

An access-restricted HTTP 403 response was recorded on Nov 22, 2026 at 11:59 UTC. Latest classified outcome: provider block observed; cause cloudflare antiphishing; mechanism phishing interstitial; observed actor Cloudflare on Nov 22, 2026 at 10:59 UTC. Cloudflare is the hosting platform for this tenant, not its registrar. At collection time, the hostname resolved to 188.114.96.3 on AS13335 (Cloudflare, Inc.). The IP and ASN identify shared Cloudflare infrastructure, not the tenant operator. DOM analysis on Nov 22, 2026 at 03:20 UTC returned 10/100. The evidence archive retains 9 visual captures from PhishDestroy, URLScan, and Cloudflare Radar. The platform TLS certificate was issued by WE1 with validity through Jan 8, 2027.

The content indicators and 3 positive source findings support the current Facebook impersonation and phishing classification. The target field identifies Facebook.

Source evidenceVirusTotal 20 / 92 4 sources

VirusTotal

20 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 14 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
Criminal IP, alphaMountain.ai, BitDefender, CyRadar, DNS8, ESET, Emsisoft, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Kaspersky, Lionic, MalwareURL, Netcraft, SOCRadar, Sophos, URLQuery, VIPRE, Webroot
Observed at
2026-11-21 12:35:05
Checked at
2026-11-22 01:59:55
Fetched at
2026-11-22 00:59:55

URLScan

Malicious

SHA-256 48deb345…83a5318

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

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

UUID
01a200c2-6e15-77cb-b279-4f911189b522
Score
100
Malicious
✓
Result at
2026-11-22T04:30:11Z
Enriched at
2026-11-22T09:11:27Z
Source timestamps
Urlscan result at: 2026-11-22 05:30:11; Urlscan enriched at: 2026-11-22 10:11:27

PhishDestroy DOM

10 / 100 · heuristic score · 2 brand references · 0 classifications

Content heuristic only; not the final score

Open report
Page code check by a separate monitor · 10 / 100 · 2026-11-22 03:20 UTC

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

Heuristic score
10
Analyzed at
2026-11-22T03:20:08Z
Source timestamp
2026-11-22 04:20:08

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
Website checksOriginal source recordRetrieved: 16 fields

Mail configuration

SPF lookups
0

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Crawler rules

User agents
  • *
Present
Yes
Disallow
  • /

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443
  • 8080

DNS servers

Nameservers
  • IP address
    173.245.59.118
    Host
    ian.ns.cloudflare.com
  • IP address
    108.162.192.100
    Host
    abby.ns.cloudflare.com
DNS zone
cont17ct-vunari-biz-selor-kemra.pages.dev

Page quality

Layout shift (CLS)
0.001
SEO score
36
Speed Index, s
0.76
First Contentful Paint (FCP), s
0.76
Largest Contentful Paint (LCP), s
0.76
Total Blocking Time (TBT), ms
0
Performance score
100
Accessibility score
96
Best practices score
96

Location

IP address
2a06:98c1:3121::3
ASN
13335
Organization
Cloudflare, Inc.
City
Washington
Country
US

TLS certificate

Subject alternative names
  • cont17ct-vunari-biz-selor-kemra.pages.dev
  • *.cont17ct-vunari-biz-selor-kemra.pages.dev
Key size, bits
256
Certificate chain
  • cont17ct-vunari-biz-selor-kemra.pages.dev
  • WE1
  • GTS Root R4
Issuer
Google Trust Services / WE1
Serial
D3A2A5A0F5F785910E76E3AAF2656E6B
SHA-256
70fe932ebaa12e48f2de50078d5ed1413d318cc2d687177917829590ef00ee16
Subject
cont17ct-vunari-biz-selor-kemra.pages.dev
Valid until
Valid from

DNS records

A
  • 188.114.97.3
  • 188.114.96.3
NS
  • abby.ns.cloudflare.com
  • ian.ns.cloudflare.com
SOA
Primary nameserver
abby.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2417084850
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2a06:98c1:3121::3
  • 2a06:98c1:3120::3

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
SAMEORIGIN
Referrer-Policy
same-origin
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2a06:98c1:3120::3
IP version
6

HTTP headers

Response headers
Server
cloudflare
Content-Type
text/html; charset=utf-8
X-Frame-Options
SAMEORIGIN
Referrer-Policy
same-origin
Original source fields · JSON
Mail configuration
Spf lookups: 0
Protective DNS results
Resolvers: 12; Blocked by: CloudFlare Family; Blocked count: 1
Crawler rules
Agents: *; Present: ✓; Disallow: /
TLS connection
Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443, 8080
DNS server
NS: (IP: 173.245.59.118; Host: ian.ns.cloudflare.com), (IP: 108.162.192.100; Host: abby.ns.cloudflare.com); Zone: cont17ct-vunari-biz-selor-kemra.pages.dev
Quality
Cls: 0.001; Seo: 36; Si s: 0.76; Fcp s: 0.76; Lcp s: 0.76; Tbt ms: 0; Performance: 100; Accessibility: 96; Best practices: 96
Location
IP: 2a06:98c1:3121::3; ASN: 13335; Org: Cloudflare, Inc.; City: Washington; Country: US
SSL
San: cont17ct-vunari-biz-selor-kemra.pages.dev, *.cont17ct-vunari-biz-selor-kemra.pages.dev; Bits: 256; Chain: cont17ct-vunari-biz-selor-kemra.pages.dev, WE1, GTS Root R4; Issuer: Google Trust Services / WE1; Serial: D3A2A5A0F5F785910E76E3AAF2656E6B; SHA256: 70fe932ebaa12e48f2de50078d5ed1413d318cc2d687177917829590ef00ee16; Subject: cont17ct-vunari-biz-selor-kemra.pages.dev; Valid to: 2027-01-08T02:25:36Z; Valid from: 2026-10-10T01:25:39Z
DNS records
A: 188.114.97.3, 188.114.96.3; NS: abby.ns.cloudflare.com, ian.ns.cloudflare.com; Soa: Nsname: abby.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2417084850; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800; Aaaa: 2a06:98c1:3121::3, 2a06:98c1:3120::3
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Message: Site does not serve any HSTS headers.
HTTP security policies
Xframeoptions: SAMEORIGIN; Referrerpolicy: same-origin; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Firewall
Waf: Cloudflare; Has waf: ✓
Get IP
IP: 2a06:98c1:3120::3; Family: 6
HTTP headers
Headers: Server: cloudflare; Content type: text/html; charset=utf-8; X frame options: SAMEORIGIN; Referrer policy: same-origin
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Security threats Phishing Phishing

Questions about cont17ct-vunari-biz-selor-kemra.pages.dev

Is cont17ct-vunari-biz-selor-kemra.pages.dev legit?

PhishDestroy rates cont17ct-vunari-biz-selor-kemra.pages.dev as critical risk (evidence score 95/100) from the recorded evidence; it was first recorded on 2026-11-22. Stored VirusTotal result: 20/92 engines flagged. Malicious: 19. Suspicious: 1. Analysis time (as stored): 2026-11-21 12:35 UTC. Retrieved (as stored): 2026-11-22 00:59 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is cont17ct-vunari-biz-selor-kemra.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 cont17ct-vunari-biz-selor-kemra.pages.dev. A confirmed blockchain transaction cannot be reversed.

What should I do if I used cont17ct-vunari-biz-selor-kemra.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 (9)

All capture links and hashes (9)

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Facebook report ↗
IP Context Canada188.114.96.3 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 11h
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.
Technical detailsProvenance & timestamps
First Detected2026-11-22
DOM Analysisanalyzed 2026-11-22score 10/1002 brand signals
Submitted URLhttp://cont17ct-vunari-biz-selor-kemra.pages.dev/appeals/submit-appeal-form/return
Favicon Hash
Observed page title
Meta for Business | Page Appeal
Automated brand references
Facebook Instagram
TLS Certificate
Issued by WE1 · stored validity ends in 46 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada188.114.96.3
Network ASN
AS13335
AS name
CLOUDFLARENET - Cloudflare, Inc., US
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

SOA

  • nsname: abby.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2417084850
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Location describes the IP network.

TLS certificate

Issuer
WE1
Valid from
2026-10-10 01:25:39
Valid until
2027-01-08 02:25:36
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint70fe932ebaa12e48f2de50078d5ed1413d318cc2d687177917829590ef00ee16
Certificate names · 2 SANs
  • cont17ct-vunari-biz-selor-kemra.pages.dev
  • *.cont17ct-vunari-biz-selor-kemra.pages.dev

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-22 11:59 UTC

The latest check was inconclusive.

Technical details
Primary outcome Provider block observed reason: Cloudflare anti-phishing block 95% confidence
Attribution Cloudflare mechanism: Phishing Interstitial source: Current Http Probe
Evidence layers Availability: Provider blocked Content: Provider blocked DNS: Stale
Latest HTTP observation Provider block observed Cloudflare anti-phishing block Cloudflare Phishing Interstitial 95% provider marker verified 2026-11-22 11:59 UTC
RDAP registration
Observed timeline last reachable: 2026-11-22 00:58 UTC current episode first observed: 2026-11-22 11:59 UTC observed RIP window: 2026-11-22 00:58 UTC → 2026-11-22 11:59 UTC · 11.01h midpoint estimate ≈ 2026-11-22 06:29 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 · 3 identified
Open complete records

VirusTotal Analysis

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

Google PageSpeed Insights — mobile performance audit of cont17ct-vunari-biz-selor-kemra.pages.dev ·

100
Good
Performance
FCP
0.76 s
First Contentful Paint
LCP
0.76 s
Largest Contentful Paint
CLS
0
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
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
11.01
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 data115
Open complete records

Captured network requests

Network requests: 7 SHA-256 hashes: 7 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-22 00:59 UTC.

Open this scan on URLScan 01a200c2-6e15-77cb-b279-4f911189b522 ↗

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
Meta for Business | Page Appeal
Crawler
Suspected Phishing | Cloudflare
cont17ct-vunari-biz-selor-kemra.pages.dev
Stored observation history3

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. Domain monitor · Recorded state

    Reachable→Unavailable

  3. Domain monitor · First collection record

    Reachable

All retained availability observations3

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. Current http probeblocked
    Observation source
    Current http probe
    Cause
    Cloudflare antiphishing
    Availability state
    Provider blocked
    Content state
    Provider blocked
    DNS state
    stale
    Recorded HTTP status
    403
    Recorded actor type
    Cdn security
    Recorded actor
    Cloudflare
    Mechanism
    Phishing interstitial
    Monitor confidence
    95
    Provider action verified
    ✓
    Registrar mechanism verified
    ✗
    Linked to a report
    ✗
    Original source timestamp
    2026-11-22 12:59:26.000000
    Evidence SHA-256
    060de5667e28abd0dfd598690bfa1377c468ef73a2ede1e47a4fcf2fcb5c39cc
    HTTP probe value as recorded
    403
    Evidence timestamp as recorded
    2026-11-22 12:59:26
    Evidence reason
    Cloudflare ban
  2. Current state backfill
    Observation source
    Current state backfill
    Cause
    Probe inconclusive
    Availability state
    unreachable
    DNS state
    stale
    Monitor confidence
    20
    Provider action verified
    ✗
    Registrar mechanism verified
    ✗
    Linked to a report
    ✗
    Original source timestamp
    2026-11-22 01:58:49.000000
    Evidence SHA-256
    7d868dc62f6f77c6e4e5822154c74b32acfad8786ffe3f8d43a58784a7bab9b4
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-22 01:58:49
  3. Http observation
    Observation source
    Http observation
    Cause
    Probe inconclusive
    Availability state
    unreachable
    Monitor confidence
    20
    Provider action verified
    ✗
    Registrar mechanism verified
    ✗
    Linked to a report
    ✗
    Original source timestamp
    2026-11-22 01:58:49.000000
    Evidence SHA-256
    7d868dc62f6f77c6e4e5822154c74b32acfad8786ffe3f8d43a58784a7bab9b4
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-22 01:58:49

Threat Response Pipeline

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

Recorded events: 12. 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
    cont17ct-vunari-biz-selor-kemra.pages.dev detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Cloudflare Radar: Malicious · Automated brand label: Facebook · Forensic Evidence Collected · Technical Analysis Recorded · 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: 11
  • 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. VirusTotal analysis with detections+2271 d 10 h
  3. Added to PhishDestroy+12 h 23 min
  1. Added to PhishDestroy

    cont17ct-vunari-biz-selor-kemra.pages.dev

    same minute
  2. URLScan

    Page captured

    +12 h 23 min
  3. VirusTotal

    20/92 engine detections

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 cont17ct-vunari-biz-selor-kemra.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.

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/cont17ct-vunari-biz-selor-kemra.pages.dev"
  title="PhishDestroy threat report for cont17ct-vunari-biz-selor-kemra.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>