VirusTotal
13 / 91
“katana”
13 / 91
checked — no detections recorded
Reportchecked — no match recorded
no community references
Reportprovider verdict: suspicious
Reportstored report
Report Analysis completed
ReportChecked; no threat flag recorded
ReportThe domain proposal-katana.network was registered on March 08, 2026 through PDR Ltd. d/b/a PublicDomainRegistry.com and is currently taken offline. DNS resolution points to the Cloudflare‑owned address 104.21.70.250, hosted in the United States under ASN 13335. The site presents a TLS certificate issued by Let’s Encrypt (E7) and negotiates HTTP/3, but HTTP requests return a 403 status code. Automated analysis assigns a Gridinsoft trust score of 0 / 100, indicating a high likelihood of malicious intent.
The page title returned by the server is “katana”, and the domain is associated with a brand‑impersonation campaign targeting Discord users, specifically employing wallet or seed phishing techniques. Three independent blocklists have listed the domain, and it is actively blocked by PhishDestroy, MetaMask, and SEAL. VirusTotal logs show that one of ninety‑four scanning engines flagged the domain, reinforcing the suspicion. The infrastructure relies on Cloudflare’s edge network, which masks the true origin server and complicates takedown efforts.
Defenders should add 104.21.70.250 to network deny lists, enforce DNS filtering for proposal‑katana.network, and monitor for any resurgence of the domain or related sub‑domains. Continuous observation of the associated blocklists and periodic re‑scans on VirusTotal are recommended to capture any changes in detection status. Because the site is already offline, immediate containment is limited to preventing future re‑registration or reuse of the same name.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: cloudflare_ban: raw=cf_phishing_block; http=403; via=https_proxy; server=cloudflare; provider_error=cloudflare_phishing_interstitial
Provider response during scan: cloudflare_phishing_interstitial
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.
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.
Edge-IP reputation is not attributed to this domain.
malavika.ns.cloudflare.comLocation describes the IP network.
ebe4066ea0d3d354722971ef9f871eb5a32cac27ce636ba2a2d1a7b7b3122dc3Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
Reported by 1 community member, first seen Mar 8, 2026
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
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