kustenkap.com is an impersonation phishing site: a page built to pass itself off as a service people already trust, so visitors hand over information they would only give the real one. PhishDestroy first flagged it on 2026-09-13. As of 2026-10-19 the site is dead and no longer serves threatening content. It has been offline since that date.
How the scam works
Impersonation phishing copies the look, wording and flow of a known brand closely enough that a hurried visitor does not question it. Victims usually arrive through a link in an email, message, ad or search result. They are then asked to sign in, verify an account or confirm details, and whatever they type goes straight to the operators. That can mean account passwords, one-time codes, card numbers or identity details, which are then used to take over accounts or commit fraud. The page title currently reads "404 Not Found", which differs from the impersonation content we classified.
Evidence
Independent scanners back the classification. On 2026-09-21, VirusTotal showed 15 of 89 engines flagging the domain, including alphaMountain.ai, BitDefender, Chong Lua Dao, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet and G-Data. That is a meaningful minority, and the vendors come from several separate threat-intelligence pipelines rather than one source. The domain also appears in 3 AlienVault OTX community pulses, and PhishDestroy lists it on its own blocklist.
Infrastructure
The domain was registered on 2025-09-09 through NameCheap, Inc., almost exactly a year before PhishDestroy detected it. That gap suggests the name was held in reserve or used quietly before the phishing page drew attention. The site was hosted at 104.219.250.37 on Namecheap's own network in the US, so registration and hosting were kept with a single provider.
What to do
If you entered a password on kustenkap.com, change it right away on the genuine service and on any other site where you reused it. Then turn on two-factor authentication. If you supplied card or banking details, contact your bank to block the card and dispute unfamiliar charges. If you shared identity information, watch for follow-up messages that cite those details to seem legitimate. Defenders should keep the domain and its IP on block and watch lists, since dormant phishing domains are sometimes revived. They should also search mail and proxy logs for earlier visits around 2026-09-13.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
(US)
