VirusTotal
6 / 92 engine detections
Open reportkra023.com is a phishing page detected by PhishDestroy on 2026-09-07. Risk: critical (88/100). Registrar: Gname 061. Status: Last known active. Hosting: Shereverov Marat Ahmedovich. VirusTotal: 6/92 engines flag it. PhishDestroy detected it 9 days before VirusTotal engines flagged it (in PhishDestroy’s checks). Do not enter credentials or connect a wallet.
“Captcha”
6 / 92 engine detections
Open report3 community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
kra023.com is an impersonation phishing site that poses as a legitimate service to capture the accounts and money of that service's users. PhishDestroy first detected it on 2026-09-07. On 2026-10-19 the domain was still alive and serving a redirect, so visitors can still be routed onward from it.
The page is titled simply "Captcha", so the visitor first sees a human-verification step rather than a recognizable brand. We classified the site as impersonation, so that title reflects the entry gate, not the full scheme. Fake captcha screens make a page feel routine and trustworthy, and they can keep automated scanners from reaching the content behind them. After the check, the victim is redirected to pages that copy the targeted service and ask for login credentials, one-time codes, or deposits. Anything typed in goes to the operators, who can then take over the account or keep the payment.
On 2026-10-18, six of 92 VirusTotal engines flagged the domain: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar and VIPRE. That count is modest, but these six vendors work independently of each other and of us. The domain also appears in three AlienVault OTX threat pulses, which means other researchers have tied it to malicious activity. Among blocklists it is currently listed by PhishDestroy, so many browsers and filters that rely on other feeds may not warn users yet.
The domain was registered on 2026-06-16 through Gname 061 Inc. That is 83 days before our first detection, a gap that suggests it was set up in advance and brought into use later. It resolves to 178.20.210.39 on a network registered to Shereverov Marat Ahmedovich in Kazakhstan. Its free Let's Encrypt certificate shows a padlock in the browser, which only means the connection is encrypted and says nothing about whether the site is safe.
If you passed the captcha and entered a password on the pages that followed, change it now on the real service and on any other site where you use the same password. Turn on app-based two-factor authentication and review recent logins and active sessions. If you sent a deposit or shared card details, contact your bank or the payment provider right away, and do not pay any follow-up fees the site asks for. Defenders should block the domain and the IP 178.20.210.39 at DNS and proxy level, search their logs for past visits, and treat captcha-themed lures as a cue to look more closely.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a07c93-556f-77f9-b9dc-5aae420945f3 |
|---|---|
| Final url | https://captcha.zlon15.at/ |
| Status | 200 |
| Redirected | off-domain |
| Redirects | [
{
"to": "https://zlon15.at/",
"from": "https://kra023.com/",
"status": 302
},
{
"to": "https://zlon15.at/",
"from": "https://zlon15.at/",
"status": 302
},
{
"to": "https://zlon15.at/",
"from": "https://zlon15.at/"
},
{
"to": "https://zlon15.at/",
"from": "https://zlon15.at/",
"status": 302
},
{
"to": "https://captcha.zlon15.at/",
"from": "https://zlon15.at/",
"status": 302
}
] |
| Ip | 178.20.210.39 |
| Ptr | undefined.hostname.localhost |
| Contacted domains | [
"zlon15.at",
"kra023.com"
] |
| Contacted IP addresses | [
"178.20.210.39",
"188.114.96.3"
] |
| Asns | [
"210006",
"13335"
] |
| Countries | [
"DE"
] |
| Document hash | ab4834c32d8005a6a047f0bbc765059da616cef07401a6eaceb5cd4d811109fd |
| Script hashes | [
"9fa0fd5b129cc1062500cf31c6be66f6617d829c3e4ccf0dc7cdba46f992632e"
] |
| Cookies | [
"go",
"http_refererq2",
"tor_scheme_id",
"tor_port",
"session_id",
"session_id_e",
"connecting_hash_lite_version",
"connecting_hash",
"onion_server_id",
"session_temp_active"
] |
| Tls | {
"san": [
"*.zlon15.at",
"zlon15.at"
],
"cipher": "AES_128_GCM",
"issuer": "YE1",
"subject": "zlon15.at",
"protocol": "TLS 1.3",
"valid_to": "2026-11-29T10:39:33Z",
"valid_from": "2026-08-31T10:39:34Z"
} |
| Domain age days | 3 |
| Apex age days | 7 |
| Tls age days | 7 |
| Tls valid days | 89 |
| Requests | 11 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 91,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "nginx\nnginx",
"content-type": "text/html; charset=UTF-8",
"strict-transport-security": "max-age=63072000",
"x-frame-options": "SAMEORIGIN\nSAMEORIGIN",
"x-content-type-options": "nosniff\nnosniff",
"referrer-policy": "strict-origin-when-cross-origin"
} |
Observed: · Retrieved:
| Uuid | 13742de5-7665-4bad-b437-71be33e7547b |
|---|
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 53,
"malicious": 4,
"suspicious": 2,
"undetected": 33
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"VIPRE": "malware",
"SOCRadar": "phishing",
"Gridinsoft": "suspicious",
"alphaMountain.ai": "suspicious",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Tags | [
"dga"
] |
| Created | 2025-03-29T00:00:00Z |
| Updated | 2026-03-30T00:00:00Z |
| First seen | 2025-03-30T08:39:15Z |
| DNS records | [
{
"ttl": 1800,
"type": "SOA",
"rname": "dns.cloudflare.com",
"value": "colin.ns.cloudflare.com"
},
{
"ttl": 300,
"type": "A",
"value": "104.21.43.192"
},
{
"ttl": 21600,
"type": "NS",
"value": "colin.ns.cloudflare.com"
},
{
"ttl": 300,
"type": "A",
"value": "172.67.184.80"
},
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700:3033::6815:2bc0"
},
{
"ttl": 300,
"type": "AAAA",
"value": "2606:4700:3034::ac43:b850"
},
{
"ttl": 21600,
"type": "NS",
"value": "lisa.ns.cloudflare.com"
}
] |
| Dns at | 2026-10-18T20:22:55Z |
| Jarm | 27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c |
| Certificate | {
"san": [
"*.kra023.com",
"kra023.com"
],
"issuer": "Let's Encrypt / YE1",
"serial": "58b584c8d9ddd4f3d6f1b011cd0c9954514",
"sha256": "c7a0368c39fd6d5b60fde79110a4002fd77d765136387503a960d18bbb276430",
"subject": "kra023.com",
"valid_to": "2027-01-06T10:59:17Z",
"valid_from": "2026-10-08T10:59:18Z"
} |
| Registry data | {
"status": [
"client transfer prohibited",
"client delete prohibited",
"active"
],
"events": {
"expiration": "2028-06-16T16:00:00Z",
"registration": "2026-06-16T18:06:30Z",
"registrar expiration": "2028-06-16T16:00:00Z",
"last update of RDAP database": "2026-06-16T18:06:30Z"
},
"registrar": "NICENIC INTERNATIONAL GROUP CO., LIMITED",
"registrar_iana_id": "3765"
} |
No. PhishDestroy classifies kra023.com as a phishing page (risk: critical, 88/100); it was first detected on 2026-09-07. VirusTotal: 6/92 engines flag it. PhishDestroy detected it 9 days before VirusTotal engines flagged it (in PhishDestroy’s checks). Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on kra023.com. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
garrett.ns.cloudflare.comLocation describes the IP network.
c7a0368c39fd6d5b60fde79110a4002fd77d765136387503a960d18bbb276430*.zlon15.atzlon15.atSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
redirect: raw=redirect_301; http=301; via=http_proxy; location=https://kra023.com/; server=cloudflare
kra023.com
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unavailable→Reachable
Unknown→dns_inactive
dns_nxdomain
dns_inactive
dns_nxdomain
0→2
Reachable→Unavailable
Reachable
6/92 engine detections
View source3 community references
View sourceNo threat flag
View sourcekra023.com
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
kra023.com)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.