Skip to security report
kimiyawax.com favicon
Domain security and threat intelligence

kimiyawax.com

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 kimiyawax.com on 2026-10-30. Stored VirusTotal result: 17/92 engines flagged. Malicious: 14. Suspicious: 3. Analysis time (as stored): 2026-10-27 07:09 UTC. Retrieved (as stored): 2026-10-30 20:54 UTC.

More about the sources
Recorded security signals

Stored VirusTotal result: 17/92 engines flagged. Malicious: 14. Suspicious: 3. Analysis time (as stored): 2026-10-27 07:09 UTC. Retrieved (as stored): 2026-10-30 20:54 UTC. Use caution — do not enter credentials or personal information.

VirusTotal detections: 17/92
Registrar
Realtime
Resolved IP
United Kingdom138.68.171.21DigitalOcean, LLC
Registered
2025-11-08
First seen by PhishDestroy
2026-10-30
OTX
community references
Page captures
open gallery
Domain age
registered 2025-11-08 according to WHOIS
OTX: 1 ref 2026-10-30

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 kimiyawax.com on 2026-10-30. Stored VirusTotal result: 17/92 engines flagged. Malicious: 14. Suspicious: 3. Analysis time (as stored): 2026-10-27 07:09 UTC. Retrieved (as stored): 2026-10-30 20:54 UTC. Risk: critical (evidence score 95/100). Registrar: Realtime. Hosting: DigitalOcean, LLC. Do not enter credentials or connect a wallet.

Critical
VirusTotal
17 / 92
Hosting
United Kingdom138.68.171.21DigitalOcean, LLC
Registrar
Realtime
Registered
2025-11-08
OTX
1 community ref
Page captures
3

PhishDestroy analysis, earlier unreviewed version

The captured page at kimiyawax.com is a browser error screen rather than site content: it reports "This site can't be reached" with the explanation "The connection was reset" and the code ERR_CONNECTION_RESET. The only interactions offered are a Details button, a Reload button, and links suggesting the user check the connection or the proxy and firewall, so no page content or form from the site itself was retrieved.

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

Source evidenceVirusTotal 17 / 92 · OTX 1 references 5 sources

VirusTotal

17 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 11 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
17
Denominator
92
Vendors
alphaMountain.ai, BitDefender, Chong Lua Dao, CyRadar, DNS8, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Kaspersky, Lionic, Seclookup, SOCRadar, Sophos, VIPRE, Webroot
Observed at
2026-10-27 07:09:48
Checked at
2026-10-30 21:55:17
Fetched at
2026-10-30 20:55:18

OTX

1 community reference

Open report

URLScan

Page capture

SHA-256 a92247a1…c375ef6

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

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

UUID
019f0826-59b0-77cd-8d67-0695f6392e34
Score
0
Malicious
✗
Result at
2026-11-01T04:30:36Z
Enriched at
2026-10-31T09:11:47Z
Source timestamps
Urlscan result at: 2026-11-01 05:30:36; Urlscan enriched at: 2026-10-31 10:11:47
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 summary
The captured page at kimiyawax.com is a browser error screen rather than site content: it reports "This site can't be reached" with the explanation "The connection was reset" and the code ERR_CONNECTION_RESET. The only interactions offered are a Details button, a Reload button, and links suggesting the user check the connection or the proxy and firewall, so no page content or form from the site itself was retrieved. The stored VirusTotal domain result reports 17 detections out of 92 engines. DNS8 reported "suspicious"; ESET reported "suspicious".
AI generated by
threat-v6-mimo
AI generated at
2026-10-30T21:04:46Z
Revision
e249c8f51b0b079a00e344cbaa5d31a7af92a708225ae5a97759e2df41f02150
Mode
stored
Interpretation
Earlier stored analysis, not reviewed; 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: 10 fields

Mail configuration

MX records
  • kimiyawax.com
SPF record
v=spf1 ip4:77.245.159.85 include:_spf.hosting.com.tr -all
DKIM
  • default
DMARC
Yes
DKIM key size, bits
2048
SPF lookups
1

CAA records

Domain
kimiyawax.com

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Ports

Open ports
  • 22
  • 80
  • 443

DNS servers

Nameservers
  • IP address
    77.245.156.176
    Host
    ns1.hosting.com.tr
  • IP address
    104.247.178.109
    Host
    ns2.hosting.com.tr
DNS zone
kimiyawax.com

Location

IP address
138.68.171.21
ASN
14061
Organization
DigitalOcean, LLC
City
Slough
Country
GB

DNS records

A
  • 138.68.171.21
MX
  • Mail server
    kimiyawax.com
    Priority
    0
NS
  • ns1.hosting.com.tr
  • ns2.hosting.com.tr
SOA
Primary nameserver
ns1.hosting.com.tr
Hostmaster
noc.hosting.com.tr
Serial
2022020402
Refresh, seconds
10800
Retry, seconds
3600
Expiry, seconds
604800
Minimum TTL, seconds
300
TXT
  • v=spf1 ip4:77.245.159.85 include:_spf.hosting.com.tr -all

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

IP lookup

IP address
138.68.171.21
IP version
4

Registration record

Registrar
Realtime Register B.V.
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • ns1.hosting.com.tr
  • ns2.hosting.com.tr
Original source fields · JSON
Mail configuration
MX: kimiyawax.com; Spf: v=spf1 ip4:77.245.159.85 include:_spf.hosting.com.tr -all; Dkim: default; Dmarc: ✓; Dkim bits: 2048; Spf lookups: 1
Caa records
Domain: kimiyawax.com
Protective DNS results
Resolvers: 12; Blocked by: CloudFlare Family; Blocked count: 1
Ports
Open: 22, 80, 443
DNS server
NS: (IP: 77.245.156.176; Host: ns1.hosting.com.tr), (IP: 104.247.178.109; Host: ns2.hosting.com.tr); Zone: kimiyawax.com
Location
IP: 138.68.171.21; ASN: 14061; Org: DigitalOcean, LLC; City: Slough; Country: GB
DNS records
A: 138.68.171.21; MX: Exchange: kimiyawax.com; Priority: 0; NS: ns1.hosting.com.tr, ns2.hosting.com.tr; Soa: Nsname: ns1.hosting.com.tr; Hostmaster: noc.hosting.com.tr; Serial: 2022020402; Refresh: 10800; Retry: 3600; Expire: 604800; Minttl: 300; Txt: v=spf1 ip4:77.245.159.85 include:_spf.hosting.com.tr -all
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Get IP
IP: 138.68.171.21; Family: 4
Registration record
Registrar: Realtime Register B.V.; Created: 2025-11-08T10:10:22Z; Updated: 2026-10-08T08:58:03Z; Expires: 2027-11-08T10:10:22Z; Status: clientTransferProhibited https://icann.org/epp; Nameservers: ns1.hosting.com.tr, ns2.hosting.com.tr
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Malware Security threats Malware

Questions about kimiyawax.com

Is kimiyawax.com legit?

PhishDestroy rates kimiyawax.com as critical risk (evidence score 95/100) from the recorded evidence; it was first recorded on 2026-10-30. Stored VirusTotal result: 17/92 engines flagged. Malicious: 14. Suspicious: 3. Analysis time (as stored): 2026-10-27 07:09 UTC. Retrieved (as stored): 2026-10-30 20:54 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is kimiyawax.com safe to connect a wallet?

Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on kimiyawax.com. A confirmed blockchain transaction cannot be reversed.

What should I do if I used kimiyawax.com?

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

All capture links and hashes (3)
kimiyawax.com: caution — 17/92 VirusTotal engines. PhishDestroy risk score 95/100 (critical).
Social preview card kimiyawax.com: caution — 17/92 VirusTotal engines. PhishDestroy risk score 95/100 (critical). v 02447d81d32b

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 54 report ↗
IP Reputation United Kingdom138.68.171.21 0/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worse This IP address has a low abuse score, but the domain itself is recognized as phishing. 0 reports checked 2026-10-30 last reported · outside the counted period
Registrar Realtime
RegistrationCreated 2025-11-08 — Expires 2027-11-08
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-10-30
DOM Analysisanalyzed 2026-10-30score 0/100
Submitted URLhttp://kimiyawax.com/
Favicon Hash
Observed page title
404 Not Found
TLS Certificate
Issued by Let's Encrypt / YR1

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United Kingdom138.68.171.21
Network ASN
AS14061
AS name
DIGITALOCEAN-ASN - DigitalOcean, LLC, US
Organization
DigitalOcean, LLC
Observed location
United KingdomSlough, GB
Server header
nginx/1.18.0 (Ubuntu)

Nameservers 2

  • ns1.hosting.com.tr
  • ns2.hosting.com.tr

SOA

  • nsname: ns1.hosting.com.tr
  • hostmaster: noc.hosting.com.tr
  • serial: 2022020402
  • refresh: 10800
  • retry: 3600
  • expire: 604800
  • minttl: 300

Mail routing 1 MX record

  • kimiyawax.compriority 0

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR1
Valid from
2026-07-08 13:46:27
Valid until
2026-10-06 13:46:26
Hostname match
No
Validity
Stored certificate expired
Collection source
PhishDestroy collector
Certificate fingerprint6b26408a69e8dc5a85c5f000c914a272393dfae3834a7421598b31f3d91cc0ff
Certificate names · 1 SAN
  • ad11.3cx.uk

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

Recorded subdomains6

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • autodiscover.kimiyawax.comDomain record
  • cpanel.kimiyawax.comDomain record
  • cpcalendars.kimiyawax.comDomain record
  • cpcontacts.kimiyawax.comDomain record
  • webdisk.kimiyawax.comDomain record
  • webmail.kimiyawax.comDomain record

VirusTotal Analysis

17 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive result retrieved by PhishDestroy
DNS8
ESET
VIPRE
G-Data
Lionic
Sophos
CyRadar
Webroot
Fortinet
SOCRadar
Kaspersky
Seclookup
Gridinsoft
BitDefender
Chong Lua Dao
alphaMountain.ai
Forcepoint ThreatSeeker
Registration & observation details1

Availability observations

Last reachable observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

All stored data97
Open complete records

Captured network requests

Network requests: 2 SHA-256 hashes: 2 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-10-30 20:59 UTC.

Open this scan on URLScan 019f0826-59b0-77cd-8d67-0695f6392e34 ↗

Stored observation history9

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→Not resolving in DNS

    domain does not exist in DNS

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

All retained availability observations89
Open complete records

Threat Response Pipeline

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

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
    kimiyawax.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · OTX Community References · Cloudflare Radar: Malicious · Forensic Evidence Collected · Technical Analysis Recorded recorded
Publication & AvailabilityDestroyList Published recorded

Recorded activity

4 entries

Lifecycle

  1. Domain registered
  2. VirusTotal analysis with detections+352 d 20 h
  3. Added to PhishDestroy+3 d 13 h
  1. AlienVault OTX

    1 community references

    +17 min
  2. Added to PhishDestroy

    kimiyawax.com

    +3 d 13 h
  3. VirusTotal

    17/92 engine detections

    +121 d 22 h
  4. URLScan

    Malicious · engine verdict · score 54

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.

kimiyawax.com

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 kimiyawax.com)
  • 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/kimiyawax.com"
  title="PhishDestroy threat report for kimiyawax.com"
  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>