Security engines reporting a detection: 2. Public blocklists reporting a match: 3. Exercise extreme caution — do not enter credentials or personal information.
Analysis of onradar.network indicates a brand impersonation campaign aimed at Discord users, specifically targeting wallet or seed information. The domain resolves to IP 188.114.97.3, an address owned by Cloudflare (AS13335) and located in the United States. No SSL/TLS certificate is presented, and the site is currently offline, preventing real‑time content inspection. Public threat feeds list the domain on four blocklists, and it is actively blocked by PhishDestroy, Polkadot, Enkrypt, and Codeesura. VirusTotal scans show two of ninety‑five security vendors flag the domain, reinforcing the suspicion of malicious intent.
Gridinsoft assigns a trust score of zero out of one hundred, and the registrar information confirms registration through Cloudflare, Inc., with authoritative nameservers craig.ns.cloudflare.com and vida.ns.cloudflare.com. The page title captured from the site references "We Didn’t Start the Fire. Gearing up for the launch of Firelight…" and mentions a Firelight Protocol article from September 2025, which does not align with the Discord branding and suggests a possible content repurposing tactic. The declared scam type is wallet/seed phishing, implying that the site likely solicits private seed phrases from Discord users under the guise of a legitimate Discord service.
Uncertainties remain regarding the exact payload delivered to victims, the specific phishing page layout, and whether any credential harvesting succeeded before the domain was taken offline. Defenders should add onradar.network to deny lists, enforce DNS filtering, and monitor Cloudflare‑hosted subdomains for similar impersonation patterns. User education campaigns should warn Discord communities about unsolicited requests for seed phrases and advise verification of URLs before entering any sensitive data. Continuous threat‑intel collection is recommended to capture any re‑hosting attempts or related infrastructure that may emerge.
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='onradar.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
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 DetectedOct 17, 2025
DOM Analysisanalyzed Apr 23, 2026score 65/1004 brand signals
Submitted URLhttps://onradar.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:09:24 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-06-17 22:12:48 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-17 22:12:48 UTC → 2026-09-30 16:14:55 UTC · 2,514.04hmidpoint estimate ≈ 2026-08-09 07:13:51 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
onradar.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 14, 2026
Time to First Unavailability
5020 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 · onradar.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.
(US)
