Skip to security report
server-security-page-2--barbnone.replit.app favicon
Domain security and threat intelligence

server-security-page-2--barbnone.replit.app

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

On 2026-11-08, server-security-page-2--barbnone.replit.app displayed a centered white card labeled "example.com" with a globe icon, above a dimmed multilingual notice that the domain is for documentation examples. The card shows a session line reading "Linux - Chrome - 7th November 2026 11:25 PM" and "Quebec, Canada", then text asking the visitor to provide the password for user@example.com to continue, with a Password field, a "Show password" checkbox, a blue NEXT button, and a footer reading "© 2026 example.com Secure Portal | Privacy". A "Made with Replit" badge appears at the lower right.

Page title: “PORTAL - Mail Authentication”

More about the sources
Recorded security signals

Stored VirusTotal result: 1/92 engines flagged. Malicious: 0. Suspicious: 1. Analysis time (as stored): 2026-11-07 19:50 UTC. Retrieved (as stored): 2026-11-08 07:53 UTC. Use caution — do not enter credentials or personal information.

VirusTotal detections: 1/92
Registrar
Nom-IQ
Resolved IP
United States34.117.33.233Google LLC
Registered
2021-04-16
First seen by PhishDestroy
2026-11-08
Page captures
open gallery
Domain age
registered 2021-04-16 according to RDAP · source data differ
2026-11-08

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 server-security-page-2--barbnone.replit.app on 2026-11-08. Stored VirusTotal result: 1/92 engines flagged. Malicious: 0. Suspicious: 1. Analysis time (as stored): 2026-11-07 19:50 UTC. Retrieved (as stored): 2026-11-08 07:53 UTC. Risk: critical (evidence score 100/100). Registrar: Nom-IQ. Status: Last known active. Hosting: Google LLC. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
1 / 92
Hosting
United States34.117.33.233Google LLC
Registrar
Nom-IQ
Registered
2021-04-16
Page captures
5

URLScan capture · 2026-11-08 06:25 UTC · SHA-256 1994bd97…78cc6cc

PhishDestroy analysis, reviewed version

On 2026-11-08, server-security-page-2--barbnone.replit.app displayed a centered white card labeled "example.com" with a globe icon, above a dimmed multilingual notice that the domain is for documentation examples. The card shows a session line reading "Linux - Chrome - 7th November 2026 11:25 PM" and "Quebec, Canada", then text asking the visitor to provide the password for user@example.com to continue, with a Password field, a "Show password" checkbox, a blue NEXT button, and a footer reading "© 2026 example.com Secure Portal | Privacy". A "Made with Replit" badge appears at the lower right.

The stored VirusTotal domain result reports 1 detections out of 92 engines. DNS8 reported "suspicious".

Source evidenceVirusTotal 1 / 92 4 sources

VirusTotal

1 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 12 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
19
Denominator
92
Vendors
Criminal IP, alphaMountain.ai, BitDefender, CyRadar, DNS8, ESET, Emsisoft, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Kaspersky, LevelBlue, Lionic, Netcraft, SOCRadar, URLQuery, VIPRE, Webroot
Checked at
2026-11-13 04:07:13
Fetched at
2026-11-13 03:07:13

URLScan

Malicious

SHA-256 3b152bdd…dadc19b

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

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

UUID
01a1b9d5-424c-7299-b7c8-3762289767b6
Score
100
Malicious
✓
Result at
2026-11-09T04:30:23Z
Enriched at
2026-11-08T09:11:53Z
Source timestamps
Urlscan result at: 2026-11-09 05:30:23; Urlscan enriched at: 2026-11-08 10:11: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
server-security-page-2--barbnone.replit.app: example.com Secure Portal password prompt
AI description
PhishDestroy records server-security-page-2--barbnone.replit.app showing an example.com Secure Portal password prompt requesting a user password to continue.
AI summary
On 2026-11-08, server-security-page-2--barbnone.replit.app displayed a centered white card labeled "example.com" with a globe icon, above a dimmed multilingual notice that the domain is for documentation examples. The card shows a session line reading "Linux - Chrome - 7th November 2026 11:25 PM" and "Quebec, Canada", then text asking the visitor to provide the password for user@example.com to continue, with a Password field, a "Show password" checkbox, a blue NEXT button, and a footer reading "© 2026 example.com Secure Portal | Privacy". A "Made with Replit" badge appears at the lower right. The stored VirusTotal domain result reports 1 detections out of 92 engines. DNS8 reported "suspicious".
AI generated by
threat-v6-mimo
AI generated at
2026-11-08T07:46:51Z
Revision
0b60388a0d8c2443919c820cc10b20e875b94bd2967cc18a9bae57100625d6dc
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
Website checksOriginal source recordRetrieved: 21 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

Page title and metadata

Page title
PORTAL - Mail Authentication

Trackers

Requests
10
Observed services
  • Name
    Google
    Company
    Google
    Country
    US
    Category
    Advertising
    Requests
    1
  • Name
    Cloudflare
    Company
    Cloudflare
    Country
    US
    Category
    Hosting
    Requests
    3
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Clearbit
    Company
    Clearbit
    Country
    US
    Category
    Site Analytics
    Requests
    1
  • Name
    ipapi
    Company
    Kloudend
    Country
    US
    Category
    Site Analytics
    Requests
    1

Forms and mixed content

Scripts without SRI
  • https://replit-cdn.com/replit-pill/replit-pill.global.js
Third-party scripts
1

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
2
TLS
17
Waiting
221
Connection
15
Download
0
Response time, ms
255

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

Carbon estimate

Bytes
21180
CO₂, grams
0.0008
Cleaner than, %
56

DNS servers

Nameservers
  • IP address
    216.239.32.107
    Host
    ns-cloud-b1.googledomains.com
  • IP address
    216.239.38.107
    Host
    ns-cloud-b4.googledomains.com
  • IP address
    216.239.34.107
    Host
    ns-cloud-b2.googledomains.com
  • IP address
    216.239.36.107
    Host
    ns-cloud-b3.googledomains.com
DNS zone
replit.app

Cookies

Cookies
  • Name
    GAESA

Location

IP address
34.117.33.233
ASN
396982
Organization
Google LLC
City
Kansas City
Country
US

TLS certificate

Issuer
Google Trust Services / WR3
Subject
replit.app

DNS records

A
  • 34.117.33.233

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=63072000; includeSubDomains
Observation
HSTS header does not contain the preload directive.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
max-age=63072000; includeSubDomains
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
34.117.33.233
IP version
4

Redirects

Redirect chain
  • https://server-security-page-2--barbnone.replit.app

HTTP headers

Response headers
Server
Google Frontend
Content-Type
text/html; charset=utf-8
Strict-Transport-Security
max-age=63072000; includeSubDomains
Via
1.1 google
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: ✓
Page title and metadata
Title: PORTAL - Mail Authentication
Trackers
Requests: 10; Trackers: (Name: Google; Company: Google; Country: US; Category: Advertising; Requests: 1), (Name: Cloudflare; Company: Cloudflare; Country: US; Category: Hosting; Requests: 3), (Name: Google Static; Company: Google; Country: US; Category: Hosting; Requests: 1), (Name: Clearbit; Company: Clearbit; Country: US; Category: Site Analytics; Requests: 1), (Name: ipapi; Company: Kloudend; Country: US; Category: Site Analytics; Requests: 1)
Forms and mixed content
No sri: https://replit-cdn.com/replit-pill/replit-pill.global.js; Third party scripts: 1
Status
Up: ✓; Code: 200; Timings: DNS: 2; TLS: 17; Wait: 221; Connect: 15; Download: 0; Response ms: 255
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
Carbon
Bytes: 21180; Co2 grams: 0.0008; Cleaner than: 56
DNS server
NS: (IP: 216.239.32.107; Host: ns-cloud-b1.googledomains.com), (IP: 216.239.38.107; Host: ns-cloud-b4.googledomains.com), (IP: 216.239.34.107; Host: ns-cloud-b2.googledomains.com), (IP: 216.239.36.107; Host: ns-cloud-b3.googledomains.com); Zone: replit.app
Cookies
Cookies: (Name: GAESA)
Location
IP: 34.117.33.233; ASN: 396982; Org: Google LLC; City: Kansas City; Country: US
SSL
Issuer: Google Trust Services / WR3; Subject: replit.app
DNS records
A: 34.117.33.233
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Header: max-age=63072000; includeSubDomains; Message: HSTS header does not contain the preload directive.
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: max-age=63072000; includeSubDomains; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Get IP
IP: 34.117.33.233; Family: 4
Redirects
Chain: https://server-security-page-2--barbnone.replit.app
HTTP headers
Headers: Server: Google Frontend; Content type: text/html; charset=utf-8; Strict transport security: max-age=63072000; includeSubDomains; Via: 1.1 google
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing Phishing Security threats

Questions about server-security-page-2--barbnone.replit.app

Is server-security-page-2--barbnone.replit.app legit?

PhishDestroy rates server-security-page-2--barbnone.replit.app as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-11-08. Stored VirusTotal result: 1/92 engines flagged. Malicious: 0. Suspicious: 1. Analysis time (as stored): 2026-11-07 19:50 UTC. Retrieved (as stored): 2026-11-08 07:53 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is server-security-page-2--barbnone.replit.app safe to connect a wallet?

Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on server-security-page-2--barbnone.replit.app. A confirmed blockchain transaction cannot be reversed.

What should I do if I used server-security-page-2--barbnone.replit.app?

  • 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 (5)

All capture links and hashes (5)
Observed page title
PORTAL - Mail Authentication
TLS Certificate
Issued by WR3 · stored validity ends in 64 days

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Genericemail report ↗
IP Reputation United States34.117.33.233 51/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worse 15 reports Fraud OrdersFTP Brute-ForcePhishingFraud VoIPEmail SpamPort ScanHackingSpoofingBrute-ForceBad Web BotWeb App Attack checked 2026-11-08 last reported
Registrar (base domain) Nom-IQ
Registration (base domain)replit.app · Created 2021-04-16 — Expires 2034-04-16
HTTP Status301 Moved Permanently
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-11-08
DOM Analysisanalyzed 2026-11-08score 0/100
Submitted URLhttp://server-security-page-2--barbnone.replit.app/
ICANN OVERSIGHT Registration: replit.app

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

Registrable domain behind this subdomain: replit.app. 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
United States34.117.33.233
Network ASN
AS396982
AS name
GOOGLE-CLOUD-PLATFORM - Google LLC, US
Organization
Google LLC
Observed location
United StatesKansas City, US
Server header
Google Frontend

Nameservers 4

  • ns-cloud-b1.googledomains.com
  • ns-cloud-b2.googledomains.com
  • ns-cloud-b3.googledomains.com
  • ns-cloud-b4.googledomains.com

Location describes the IP network.

TLS certificate

Issuer
WR3
Valid from
2026-10-28 04:51:45
Valid until
2027-01-26 05:47:40
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint9d66dbe59ada0a41e27e591854785cf65280827d651cc4eab47765cf85053250
Certificate names · 2 SANs
  • replit.app
  • *.replit.app

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 11:26 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting DNS: Resolved
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-11-21 11:26 UTC
RDAP registration
Observed timeline last reachable: 2026-11-21 11:26 UTC last content: 2026-11-09 11:10 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 · 5 identified
Open complete records

VirusTotal Analysis

1 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive result retrieved by PhishDestroy Previous stored snapshot: 1 detection
DNS8

Archived Evidence

Wayback Machine Snapshot
View Archive

Saved snapshots 1

PageSpeed (mobile): 96

Google PageSpeed Insights — mobile performance audit of server-security-page-2--barbnone.replit.app ·

96
Good
Performance
FCP
1.8 s
First Contentful Paint
LCP
2.55 s
Largest Contentful Paint
CLS
0.002
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
1.8 s
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://server-security-page-2--barbnone.replit.app/
Final URL: https://server-security-page-2--barbnone.replit.app/
PORTAL - Mail Authentication
Response
HTTP 200
HTML body
20.7 KB
Compressed
5.4 KB
Links
0 internal · 0 external
Selected response headers
Cache-Control: private
Content-Type: text/html; charset=utf-8
Server: Google Frontend
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 12
Accept-Ranges
bytes
Alt-Svc
h3=":443"; ma=2592000
Cache-Control
private
Content-Length
21180
Content-Type
text/html; charset=utf-8
Date
Sun, 08 Nov 2026 07:43:44 GMT
Expires
Sun, 08 Nov 2026 07:43:44 GMT
Last-Modified
Sat, 07 Nov 2026 18:46:17 GMT
Server
Google Frontend
Strict-Transport-Security
max-age=63072000; includeSubDomains
Via
1.1 google
X-Cloud-Trace-Context
e5b45f60efe96ad31894d7fa211d7452;o=1

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.

All stored data106
Open complete records

Captured network requests

Network requests: 11 SHA-256 hashes: 8 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-08 07:40 UTC.

Open this scan on URLScan 01a1b9d5-424c-7299-b7c8-3762289767b6 ↗

Stored observation history14

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

    Redirecting elsewhere

    HTTP redirect

  2. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  3. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  4. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  5. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

Earlier observations 9
  1. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  2. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  3. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  4. Availability monitor · Recorded state

    Redirecting elsewhere

    HTTP redirect

  5. Availability monitor · Recorded state

    Behind a check page or access restriction

    access restricted · access restriction

  6. Availability monitor · Recorded state

    Behind a check page or access restriction

    access restricted · access restriction

  7. Availability monitor · Recorded state

    Serving page content

    page content returned

  8. Availability monitor · Recorded state

    Behind a check page or access restriction→Serving page content

    page content returned

  9. Availability monitor · Recorded state

    Behind a check page or access restriction

    access restricted · access restriction

All retained availability observations53
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
    server-security-page-2--barbnone.replit.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Cloudflare Radar: Malicious · Forensic Evidence Collected · Technical Analysis Recorded recorded
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

5 entries

Lifecycle

  1. Domain registered
  2. VirusTotal analysis with detections+2030 d 23 h
  3. Added to PhishDestroy+11 h 45 min
  1. Wayback Machine

    Page archived

    +9 min
  2. Cloudflare Radar

    Phishing

    +6 min
  3. Added to PhishDestroy

    server-security-page-2--barbnone.replit.app

    +1 h 10 min
  4. URLScan

    Malicious

    +10 h 35 min
  5. VirusTotal

    1/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

Check for cloaking

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

server-security-page-2--barbnone.replit.app

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 server-security-page-2--barbnone.replit.app)
  • 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/server-security-page-2--barbnone.replit.app"
  title="PhishDestroy threat report for server-security-page-2--barbnone.replit.app"
  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>