Security engines reporting a detection: 10. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
On July 24, 2026 analysts observed that the domain jito-claim.network was registered through Cloudflare, Inc. and delegated to the Cloudflare nameservers kyle.ns.cloudflare.com and pat.ns.cloudflare.com. The domain resolves to the IP address 104.21.25.21, which is owned by AS13335 Cloudflare, Inc. and geolocated to the United States. No TLS certificate is presented, indicating that the site does not serve HTTPS traffic. An HTTP request to the domain returned the page title "Plesk Obsidian 18.0.71," a default administrative interface title that suggests the server is running a Plesk control panel rather than a purpose‑built phishing landing page. The infrastructure analysis therefore points to a misconfigured or abandoned hosting environment rather than a actively maintained malicious site.
The domain is currently offline, but historical scans show it was flagged by ten of ninety‑five VirusTotal scanners, and it appears on three security blocklists. Specifically, PhishDestroy, ScamSniffer, and Enkrypt have listed the domain as malicious. Gridinsoft assigned a trust score of 0 out of 100, reinforcing the assessment of high risk. The threat type is recorded as a crypto scam that impersonates the brand Jito, indicating that any prior content likely attempted to lure victims into a cryptocurrency‑related fraud.
Given the absence of a valid SSL certificate, the low trust score, and multiple vendor detections, defenders should treat jito-claim.network as a high‑risk indicator. Recommended mitigations include adding the domain to DNS‑level blocklists, updating firewall deny rules, and monitoring the associated IP address for re‑hosting activity. Continuous observation of the Cloudflare nameservers for new subdomains is advised, as the attacker may redeploy the campaign on a different hostname within the same account.
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='jito-claim.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionEr
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
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 DetectedNov 30, 2025
DOM Analysisanalyzed Apr 23, 2026score 85/1001 brand signal
Submitted URLhttps://jito-claim.network/
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.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:08:56 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-06-17 10:34:03 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-17 10:34:03 UTC → 2026-09-30 16:14:55 UTC · 2,525.68hmidpoint estimate ≈ 2026-08-09 01:24:29 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.
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.
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
jito-claim.network detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
May 12, 2026
Time to First Unavailability
3903 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.
4 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 · jito-claim.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.
Content matches4
Same favicon hash or the same page title as this host.
(US)
