SSL certificate is invalid or expired. Issuer: Let's Encrypt / E8
Evidence Summary
High
VirusTotal
3/92
OTX
1 community ref
This domain, allocation-katana.network, is currently flagged as an active phishing threat targeting cryptocurrency users. Registered on May 9, 2026, through PDR Ltd. d/b/a PublicDomainRegistry.com, the domain resolves to 104.21.31.193, an IP address hosted by Cloudflare in Canada. Analysis indicates the site is configured to return an HTTP 403 status, suggesting either a cloaking mechanism to evade detection or a temporary misconfiguration. The nameservers damon.ns.cloudflare.com and maya.ns.cloudflare.com further confirm the use of Cloudflare infrastructure, a common tactic among phishing operators to obscure hosting origins and leverage the provider's SSL certificates for legitimacy. Security vendors have detected malicious activity associated with allocation-katana.network, with 3 out of 95 engines on VirusTotal flagging the domain as phishing-related. Additionally, the domain appears on one security blocklist and has been documented in a single threat intelligence pulse on AlienVault OTX, reinforcing its classification as a high-risk threat. The Gridinsoft trust score of 0/100 further corroborates the domain's malicious intent. The SSL certificate, issued by Let's Encrypt, is consistent with phishing campaigns that aim to appear secure while harvesting credentials. While the specific phishing kit or targeted brand remains unconfirmed, the domain name suggests an attempt to impersonate cryptocurrency wallet services, a common tactic in financial phishing schemes. Defenders should treat this domain as actively malicious and prioritize blocking it at the DNS or network level. Organizations are advised to monitor for connections to 104.21.31.193 and review logs for any interactions with allocation-katana.network, particularly from endpoints handling cryptocurrency transactions. Given the domain's recent registration and low detection counts, continued vigilance is warranted as the campaign may still be evolving.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not observedNo cloaking was observed in the stored scan
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not observed
Cloaking score
0/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='allocation-katana.network', port=80): Max retries exceeded with url: / (Caused by NewConne
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Waiting
Domain details
Domain
IP ContextCloudflare shared edgeorigin IP hiddenEdge-IP reputation is not attributed to this domain.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedJun 15, 2026
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
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.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 01:12:42 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-07-20 10:11:39 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-07-20 10:11:39 UTC → 2026-09-30 16:14:55 UTC · 1,734.05hmidpoint estimate ≈ 2026-08-25 13:13:17 UTC · precision very low · basis bounded
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.
Last analyzed First positive detection Previous stored snapshot: 0 detections
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-08-05 22:52:27 UTC
Domain state transitioned from alive to dead.
Threat Response Pipeline
Discovery
Analysis
Monitoring
7 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
allocation-katana.network detected and queued for full analysis
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Aug 6, 2026
Time to First Unavailability
1242 hours elapsed from detection to the first unavailable observation.
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+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
2 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
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 →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · allocation-katana.network
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Same registrar: PDR6
Registered through the same registrar. A registrar serves millions of unrelated customers, so this groups reports rather than proving a link.
(US)
