Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 15/92 engines flagged. malicious: 14. suspicious: 1. Analysis time (as stored): 2026-11-07T09:28:30Z. Retrieved (as stored): 2026-11-08T02:25:38Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
jflkp.csb.app favicon

jflkp.csb.app

In short

PhishDestroy first recorded jflkp.csb.app on 2026-11-07. Stored VirusTotal result: 15/92 engines flagged. malicious: 14. suspicious: 1. Analysis time (as stored): 2026-11-07T09:28:30Z. Retrieved (as stored): 2026-11-08T02:25:38Z.

“React App”

Review the evidence
Registrar
SwedenNamecheap
Resolved IP
United Kingdom172.64.151.115CloudFLARENET-EU · CDN
Registered
May 8, 2018
First observed
Nov 7, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 15/92
VirusTotal
15 / 92
engine detections ·
URLScan
Malicious
engine verdict · score 7
Page captures
7
open gallery
Domain age
3,106 days
registered 2018-05-08 according to WHOIS · source data differ
Nov 7, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded jflkp.csb.app on 2026-11-07. Stored VirusTotal result: 15/92 engines flagged. malicious: 14. suspicious: 1. Analysis time (as stored): 2026-11-07T09:28:30Z. Retrieved (as stored): 2026-11-08T02:25:38Z. Risk: critical (100/100). Registrar: Namecheap. Status: Last known active. Hosting: CloudFLARENET-EU. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
15 / 92
Hosting
United Kingdom172.64.151.115CloudFLARENET-EU · CDN
Registrar
SwedenNamecheap
Registered
May 8, 2018
Page captures
7
Page captures Source results Registration record

Recorded source summary

PhishDestroy stores a record for jflkp.csb.app. Source observations are dated separately; missing checks do not establish safety.

A reviewed analysis is not available for this text revision. Consult the dated source records below.

Source evidenceVirusTotal 15 / 92 7 sources

VirusTotal

15 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 14 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
47
Malicious
14
Suspicious
1
Undetected
30

Vendor labels

DNS8
phishing
ESET
suspicious
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Fortinet
phishing
SOCRadar
phishing
Seclookup
malicious
Gridinsoft
phishing
BitDefender
phishing
Chong Lua Dao
malicious
alphaMountain.ai
phishing

Reputation score

0

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

Registrar

NAMECHEAP INC

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    104.18.36.141
  • TTL, seconds
    300
    Type
    A
    Value
    172.64.151.115
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:440d::ac40:9773
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2a06:98c1:3102::6812:248d

DNS records observed

JARM fingerprint

27d40d40d00040d00042d43d00041df04c41293ba84f6efe3a613b22f983e6

Certificate

Subject alternative names
  • csb.app
  • *.csb.app
  • preview.csb.app
  • *.preview.csb.app
Issuer
Google Trust Services / WE1
Serial
c1e196142b9d2df813f651af0235e3ec
SHA-256
e997ace578e40696c555b6cef9bb8e5c6cdae52e4aa4dc8a984059d65b5fd770
Subject
csb.app
Valid until
Valid from

Registration record

Registrar
NAMECHEAP INC
Registrar IANA ID
1068
Registrar URL
http://www.namecheap.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • adel.ns.cloudflare.com
  • greg.ns.cloudflare.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 47,
    "malicious": 14,
    "suspicious": 1,
    "undetected": 30
}
Vendor labels
{
    "DNS8": "phishing",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "phishing",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Registrar
NAMECHEAP INC
Created
2018-05-08T16:00:02Z
Expires
2027-05-08T16:00:02Z
Updated
2022-06-15T08:46:31Z
First seen
2023-10-13T16:35:05Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "104.18.36.141"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.64.151.115"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:440d::ac40:9773"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2a06:98c1:3102::6812:248d"
    }
]
Dns at
2026-11-07T09:28:44Z
Jarm
27d40d40d00040d00042d43d00041df04c41293ba84f6efe3a613b22f983e6
Certificate
{
    "san": [
        "csb.app",
        "*.csb.app",
        "preview.csb.app",
        "*.preview.csb.app"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "c1e196142b9d2df813f651af0235e3ec",
    "sha256": "e997ace578e40696c555b6cef9bb8e5c6cdae52e4aa4dc8a984059d65b5fd770",
    "subject": "csb.app",
    "valid_to": "2027-02-02T05:48:18Z",
    "valid_from": "2026-11-04T04:50:17Z"
}
Registration record
{
    "registrar": "NAMECHEAP INC",
    "registrar_iana_id": "1068",
    "registrar_url": "http://www.namecheap.com",
    "created": "2018-05-08T16:00:02Z",
    "updated": "2022-04-29T11:13:42Z",
    "expires": "2027-05-08T16:00:02Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "adel.ns.cloudflare.com",
        "greg.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
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
scope
unknown
result_state
observed
numerator
15
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","BitDefender","Chong Lua Dao","CyRadar","DNS8","ESET","Fortinet","G-Data","Gridinsoft","Lionic","Seclookup","SOCRadar","Sophos","VIPRE","Webroot"]
observed_at
2026-11-07 09:28:30
checked_at
2026-11-08 03:25:38
fetched_at
2026-11-08 02:25:38
time_basis
as stored; legacy timezone not established

URLScan

Malicious · engine verdict · score 7

SHA-256 fc3ff9796eedc16ab581f69d725b068037436f907b66d9fec07956df8518acf3

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a0a3e0-e134-730d-9708-9159b73bf395

Final URL

https://jflkp.csb.app/

HTTP response

400

Redirect type

https-only

Redirects

  • To
    https://jflkp.csb.app/
    From
    http://jflkp.csb.app/
    Status
    307

IP address

2a06:98c1:3102::6812:248d

Contacted domains

  • fonts.gstatic.com
  • fonts.googleapis.com

Contacted IP addresses

  • 142.251.20.94
  • 2a00:1450:4001:c17::5f
  • 2a06:98c1:3102::6812:248d

Autonomous systems (ASN)

  • 15169
  • 13335

Server countries

  • US
  • DE

Document hash

9f078b944a4150efa1f162ae32a9b63f2e73c325bc69163ae94ebaad33073252

JavaScript globals

  • btnAnswerYes

Cookies

  • csb_anon_uid

TLS session and certificate

Subject alternative names
  • csb.app
  • *.csb.app
  • preview.csb.app
  • *.preview.csb.app
Cipher
AES_128_GCM
Issuer
WE1
Subject
csb.app
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

2049

Differs from the registration date in WHOIS (2018-05-08), which gives 3051 days on the scan date 2026-09-15. The two sources disagree; both values are kept as recorded.

Registered domain age, days

2049

Differs from the registration date in WHOIS (2018-05-08), which gives 3051 days on the scan date 2026-09-15. The two sources disagree; both values are kept as recorded.

Certificate age, days

9

Certificate validity, days

90

Page requests

4

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
7
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
cloudflare
Content-type
text/html, charset=UTF-8
Original source fields · JSON
Uuid
01a0a3e0-e134-730d-9708-9159b73bf395
Final url
https://jflkp.csb.app/
Status
400
Redirected
https-only
Redirects
[
    {
        "to": "https://jflkp.csb.app/",
        "from": "http://jflkp.csb.app/",
        "status": 307
    }
]
Ip
2a06:98c1:3102::6812:248d
Contacted domains
[
    "fonts.gstatic.com",
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "142.251.20.94",
    "2a00:1450:4001:c17::5f",
    "2a06:98c1:3102::6812:248d"
]
Asns
[
    "15169",
    "13335"
]
Countries
[
    "US",
    "DE"
]
Document hash
9f078b944a4150efa1f162ae32a9b63f2e73c325bc69163ae94ebaad33073252
Globals
[
    "btnAnswerYes"
]
Cookies
[
    "csb_anon_uid"
]
Tls
{
    "san": [
        "csb.app",
        "*.csb.app",
        "preview.csb.app",
        "*.preview.csb.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "csb.app",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-05T04:37:02Z",
    "valid_from": "2026-09-06T03:37:22Z"
}
Domain age days
2049

Differs from the registration date in WHOIS (2018-05-08), which gives 3051 days on the scan date 2026-09-15. The two sources disagree; both values are kept as recorded.

Apex age days
2049

Differs from the registration date in WHOIS (2018-05-08), which gives 3051 days on the scan date 2026-09-15. The two sources disagree; both values are kept as recorded.

Tls age days
9
Tls valid days
90
Requests
4
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 7,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html, charset=UTF-8"
}

OTX

no community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

0bda6073-d67e-4804-abca-e0607868122f

Final URL

https://jflkp.csb.app/

HTTP response

403

Navigation history

  • URL
    https://jflkp.csb.app/
    Status
    403

DOM structure hash

e1e0ec04ba2dccd9143717ccf431a0c9d267fac4083951806a2652b5fb5fcf8d

Document hash

03a64d2b1a53db0515005062247d7342d1d30d863b82aa94c989244cc91deb0f

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    jflkp.csb.app
    Type
    A
    Value
    104.18.36.141
  • Name
    jflkp.csb.app
    Type
    A
    Value
    172.64.151.115
  • Name
    jflkp.csb.app
    Type
    AAAA
    Value
    2a06:98c1:3102::6812:248d
  • Name
    jflkp.csb.app
    Type
    AAAA
    Value
    2606:4700:440d::ac40:9773

DNSSEC valid

No

IP address

127.0.1.31

127.0.1.31 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Registration record

Registrar
Namecheap Inc.
Registered
Updated
Expires
Nameservers
  • adel.ns.cloudflare.com
  • greg.ns.cloudflare.com
Original source fields · JSON
Uuid
0bda6073-d67e-4804-abca-e0607868122f
Final url
https://jflkp.csb.app/
Status
403
History
[
    {
        "url": "https://jflkp.csb.app/",
        "status": 403
    }
]
DOM structure hash
e1e0ec04ba2dccd9143717ccf431a0c9d267fac4083951806a2652b5fb5fcf8d
Document hash
03a64d2b1a53db0515005062247d7342d1d30d863b82aa94c989244cc91deb0f
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "jflkp.csb.app",
        "type": "A",
        "value": "104.18.36.141"
    },
    {
        "name": "jflkp.csb.app",
        "type": "A",
        "value": "172.64.151.115"
    },
    {
        "name": "jflkp.csb.app",
        "type": "AAAA",
        "value": "2a06:98c1:3102::6812:248d"
    },
    {
        "name": "jflkp.csb.app",
        "type": "AAAA",
        "value": "2606:4700:440d::ac40:9773"
    }
]
Dnssec valid
false
Ip
127.0.1.31

127.0.1.31 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Registration record
{
    "registrar": "Namecheap Inc.",
    "created": "2018-05-08T16:00:02Z",
    "updated": "2026-05-18T11:38:11Z",
    "expires": "2027-05-08T16:00:02Z",
    "nameservers": [
        "adel.ns.cloudflare.com",
        "greg.ns.cloudflare.com"
    ]
}

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

15 / 100 · heuristic score · 0 brand references · 0 classifications

Open report

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: 22 fields

Mail configuration

SPF lookups
0

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
1
Archived days
2
Snapshots per day
0
Average page size, bytes
9915

Crawler rules

User agents
  • *
Present
Yes

Page title and metadata

Page title
React App
Theme color
#000000

Forms and mixed content

Scripts without SRI
  • https://codesandbox.io/static/js/vendors~embed~sandbox-startup.94f8a764c.chunk.js
  • https://codesandbox.io/static/js/default~app~embed~sandbox~sandbox-startup.06fa816c4.chunk.js
  • https://codesandbox.io/static/browserfs12/browserfs.min.js
  • https://codesandbox.io/static/js/vendors~app~codemirror-editor~monaco-editor~sandbox.f80b3d7b3.chunk.js
  • https://codesandbox.io/static/js/common-sandbox.9e074986a.chunk.js
  • https://codesandbox.io/static/js/vendors~embed~sandbox.db748f498.chunk.js
  • https://codesandbox.io/static/js/vendors~sandbox.84fa4b581.chunk.js
  • https://codesandbox.io/static/js/default~app~embed~sandbox.5b0f0d656.chunk.js
  • https://codesandbox.io/static/js/sandbox-startup.862593056.js
  • https://codesandbox.io/static/js/sandbox.d867b1f77.js
Third-party scripts
12

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
15
TLS
26
Waiting
76
Connection
8
Download
0
Response time, ms
125

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
    108.162.193.115
    Host
    greg.ns.cloudflare.com
  • IP address
    108.162.192.55
    Host
    adel.ns.cloudflare.com
DNS zone
csb.app

Cookies

Cookies
  • Name
    csb_anon_uid
    Secure
    Yes
    Session cookie
    Yes
    HTTP-only
    Yes

Location

IP address
2a06:98c1:3102::6812:248d
ASN
13335
Organization
CloudFLARENET-EU
City
London
Country
GB

TLS certificate

Issuer
Google Trust Services / WE1
Subject
csb.app

DNS records

A
  • 172.64.151.115
  • 104.18.36.141
AAAA
  • 2606:4700:440d::ac40:9773
  • 2a06:98c1:3102::6812:248d

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

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
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:3102::6812:248d
IP version
6

Redirects

Redirect chain
  • https://jflkp.csb.app

Technology stack

Technologies
  • Google Font API
  • Cloudflare
  • HTTP/3

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html
Via
1.1 google
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-11-07T16:06:46Z",
    "first": "2025-11-25T21:24:23Z",
    "changes": 1,
    "days_archived": 2,
    "scans_per_day": 0,
    "avg_page_bytes": 9915
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true
}
Page title and metadata
{
    "title": "React App",
    "themeColor": "#000000"
}
Forms and mixed content
{
    "no_sri": [
        "https://codesandbox.io/static/js/vendors~embed~sandbox-startup.94f8a764c.chunk.js",
        "https://codesandbox.io/static/js/default~app~embed~sandbox~sandbox-startup.06fa816c4.chunk.js",
        "https://codesandbox.io/static/browserfs12/browserfs.min.js",
        "https://codesandbox.io/static/js/vendors~app~codemirror-editor~monaco-editor~sandbox.f80b3d7b3.chunk.js",
        "https://codesandbox.io/static/js/common-sandbox.9e074986a.chunk.js",
        "https://codesandbox.io/static/js/vendors~embed~sandbox.db748f498.chunk.js",
        "https://codesandbox.io/static/js/vendors~sandbox.84fa4b581.chunk.js",
        "https://codesandbox.io/static/js/default~app~embed~sandbox.5b0f0d656.chunk.js",
        "https://codesandbox.io/static/js/sandbox-startup.862593056.js",
        "https://codesandbox.io/static/js/sandbox.d867b1f77.js"
    ],
    "third_party_scripts": 12
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 15,
        "tls": 26,
        "wait": 76,
        "connect": 8,
        "download": 0
    },
    "response_ms": 125
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "108.162.193.115",
            "host": "greg.ns.cloudflare.com"
        },
        {
            "ip": "108.162.192.55",
            "host": "adel.ns.cloudflare.com"
        }
    ],
    "zone": "csb.app"
}
Cookies
{
    "cookies": [
        {
            "name": "csb_anon_uid",
            "secure": true,
            "session": true,
            "http_only": true
        }
    ]
}
Location
{
    "ip": "2a06:98c1:3102::6812:248d",
    "asn": "13335",
    "org": "CloudFLARENET-EU",
    "city": "London",
    "country": "GB"
}
Ssl
{
    "issuer": "Google Trust Services / WE1",
    "subject": "csb.app"
}
DNS records
{
    "A": [
        "172.64.151.115",
        "104.18.36.141"
    ],
    "AAAA": [
        "2606:4700:440d::ac40:9773",
        "2a06:98c1:3102::6812:248d"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2a06:98c1:3102::6812:248d",
    "family": 6
}
Redirects
{
    "chain": [
        "https://jflkp.csb.app"
    ]
}
Tech stack
{
    "technologies": [
        "Google Font API",
        "Cloudflare",
        "HTTP/3"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html",
        "via": "1.1 google"
    }
}

Questions about jflkp.csb.app

Is jflkp.csb.app legit?

PhishDestroy rates jflkp.csb.app as critical risk (100/100) from the recorded evidence; it was first recorded on 2026-11-07. Stored VirusTotal result: 15/92 engines flagged. malicious: 14. suspicious: 1. Analysis time (as stored): 2026-11-07T09:28:30Z. Retrieved (as stored): 2026-11-08T02:25:38Z. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is jflkp.csb.app safe to connect a wallet?

This report does not record which wallet requests jflkp.csb.app makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used jflkp.csb.app?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you 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 · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 7 captures

URLScan · 2026-09-15 1 / 7
SourceURLScan · 2026-09-15
Recorded
StateStored capture
HTTP status400
Final URLhttps://jflkp.csb.app/
Position1 / 7
Open capture Source Report Wayback Download
All capture links and hashes (7)
Observed page title
React App
TLS Certificate
Issued by WE1 · stored validity ends in 26 days

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 7 report ↗
IP Context United Kingdom172.64.151.115 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) Namecheap SE(SE)
Abuse contact["abuse@namecheap.com", "d807ea723facd141s@"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for csb.app →
Registration (base domain)csb.app · Created May 8, 2018 — Expires May 8, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedNov 7, 2026
DOM Analysisanalyzed Nov 8, 2026score 15/100
Submitted URLhttp://jflkp.csb.app/
Favicon Hash
ICANN OVERSIGHT Registration: csb.app

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For the registrable domain csb.app behind this subdomain, 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.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United Kingdom172.64.151.115
Network ASN
AS13335
Organization
CloudFLARENET-EU
Observed location
United KingdomLondon, GB
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • adel.ns.cloudflare.com
  • greg.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
WE1
Valid from
2026-09-06 03:37:22
Valid until
2026-12-05 04:37:02
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprinte997ace578e40696c555b6cef9bb8e5c6cdae52e4aa4dc8a984059d65b5fd770
Certificate names · 4 SANs
  • csb.app
  • *.csb.app
  • preview.csb.app
  • *.preview.csb.app

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

viewdns.info · 172.64.151.115rapiddns.io

Latest Classified Outcome 2026-11-08 11:09:02 UTC

The site was serving its pages at the latest check.

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

VirusTotal Analysis

15 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
DNS8
ESET
VIPRE
G-Data
Lionic
Sophos
CyRadar
Webroot
Fortinet
SOCRadar
Seclookup
Gridinsoft
BitDefender
Chong Lua Dao
alphaMountain.ai
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of jflkp.csb.app · checked Nov 8, 2026

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 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.

Captured network requests

Network requests: 4 SHA-256 hashes: 4 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-07 23:19 UTC.

Open this scan on URLScan 01a0a3e0-e134-730d-9708-9159b73bf395 ↗

Stored observation history1

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

    live_content

    content_served

Separate monitor HTTP observation

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

Observed · UTC
Recorded HTTP status
200
Probe value as recorded
200
Original source timestamp
2026-11-07 16:28:48
All retained availability observations5

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_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-08 12:09:02.000000
    Evidence SHA-256
    1d16e379dcb54e9de0606737d04f026bf284ec8aabc9c5dd1b30e2715f514e3c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-08 12:09:02
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-08 12:09:02.000000
    Evidence SHA-256
    1d16e379dcb54e9de0606737d04f026bf284ec8aabc9c5dd1b30e2715f514e3c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-08 12:09:02
    Evidence reason
    alive_content
  3. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-08 11:22:05.004741
    Evidence SHA-256
    2b635c6648ba6e529b842e210489cc0cc6e9715da198da3a1b40fdbd66628b9b
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-08 11:22:05.004741
    Evidence reason
  4. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    400
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-08 00:18:37.000000
    Evidence SHA-256
    460f8d1e1b094195d616e1b5dfb602e3106208b55ec6d737d91178b6f21662f0
    Evidence timestamp as recorded
    2026-11-08 00:18:37
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    false
  5. http_observationunknown
    Observation source
    http_observation
    Cause
    no_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    400
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-08 00:18:37.000000
    Evidence SHA-256
    cd81db8e59f2b0074bac3733787252558dd5eb743297babc75eb0a3a9aea5b15
    Evidence timestamp as recorded
    2026-11-08 00:18:37

Threat Response Pipeline

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

Recorded events: 8. 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: 1 of 1
  • Threat Ingested
    jflkp.csb.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 6 of 6
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 7
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • VirusTotal
    Detections recorded on VirusTotal: 15/92
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

3 entries
  1. Added to PhishDestroy

    jflkp.csb.app

    View source
  2. VirusTotal

    15/92 engine detections

    View source
  3. URLScan

    Malicious · engine verdict · score 7

    View source
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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation
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.

jflkp.csb.app

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 15 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked Last known active
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. Silence is the scammer’s greatest advantage. Break it.
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.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
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.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

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

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. 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.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

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

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • 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

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 jflkp.csb.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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

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.

Request a correction or appeal How PhishDestroy works
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/jflkp.csb.app"
  title="PhishDestroy threat report for jflkp.csb.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>