Notification and current-status evidence
The sent-report ledger records the first outgoing report at . A report was sent to the recorded registrar; contact details remain in Domain Intelligence. The latest stored availability evidence still shows the domain reachable; 15 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
octra[.]org
“octra”
Evidence Summary
Analysis of octra.org as of 27 July 2026 shows that the domain is actively hosted on Cloudflare infrastructure, using the nameservers carla.ns.cloudflare.com and logan.ns.cloudflare.com and resolving to the IPv4 address 104.26.14.236. The domain was registered through GoDaddy.com, LLC on 5 November 2022 and has remained active since creation. VirusTotal records indicate that the domain has been submitted to the service and examined by 91 scanning engines; at the time of review none of the engines reported a detection. The domain appears on a single external blocklist and is listed as blocked by the PhishDestroy service, confirming that at least one security community has identified it as malicious.
No additional public threat intelligence sources such as Google Safe Browsing, OTX, or SSL/TLS reputation services are referenced in the current data set, and no page title or content analysis has been provided. Consequently, the primary evidence for malicious intent derives from its classification as a generic phishing site, its inclusion on a blocklist, and the lack of benign reputation signals. Defenders should consider adding octra.org to outbound URL filtering rules, monitoring DNS queries for the domain, and ensuring that any internal phishing detection tools flag connections to the IP address 104.26.14.236.
Network traffic to the associated Cloudflare nameservers should be logged for anomaly detection. Because the domain is still active, continuous re‑evaluation is advised; periodic rescans on VirusTotal and checks against updated blocklists will help determine whether the threat posture changes. Organizations that employ email security gateways should also verify that messages containing links to octra.org are quarantined or rejected, given the confirmed phishing designation.
Submitted Evidence Snapshot
- Sent
- Ledger records
- 1
- Case ID
PD-20260727-7C0662- PDF artifact
- PDF evidence
Full evidence text
Policy Violations: Universal TOS + Abuse Policy prohibit fraudulent, abusive, malicious, phishing and illegal activity; grants right to terminate or suspend services
Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
Data Coverage
Threat Response Pipeline
Blocklist coverage
10 monitored external feeds · stored snapshot Aug 11, 2026
10 monitored external feeds No match
Detection timeline
-
First recorded
First stored value: Reachable
Financial Infrastructure
Addresses extracted from the phishing page.
Telegram
Stored Capture
Domain Intelligence
Technical detailsDNS, TLS names and timestamps
ICANN OVERSIGHT
Accreditation and RAA context
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.
Technologies
1 high-confidence technology identified
VirusTotal Analysis
Archived Evidence
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of octra.org · checked Jul 27, 2026
Were You Affected by This Site?
If a wallet, seed phrase, or account was exposed, report the incident immediately. Revoke approvals and move remaining assets to a new wallet created on a trusted device.
Report to Your Local Authorities
Select your country to get official cybercrime contacts, or create a complaint draft →.
Check Any Domain
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowReport Phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent phishing reports and observed availability changes
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive
Recommendations & Advice for Victims
An estimated $51 billion flowed to illicit crypto wallets in 2024 (source). If you interacted with octra.org — act now.
What should I do immediately?
Urgent
- Revoke token approvals — use revoke.cash to remove access granted to malicious smart contracts
- Move remaining funds to a brand-new wallet. The compromised wallet is no longer safe
- Change all passwords — email, exchange accounts, anything that shares the same password
- Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
- Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
According to the FBI, the most important details are transaction data:
- Cryptocurrency addresses — scammer's wallet (e.g.,
0x5856...35985) - Amount & crypto type — exact amount (e.g., 1.02345 ETH, 0.5 BTC, 500 USDT)
- Transaction ID (hash) — the unique blockchain transaction identifier
- 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
octra.org) - 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)
- Chainabuse — flag scam wallets across exchanges & platforms
- Your crypto exchange — notify its fraud team immediately; it may be able to preserve records or restrict funds held on its platform
- 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 crypto scams typically work?
- Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
- Malicious approvals — "connect wallet" prompts that grant unlimited token spending to attackers
- 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
- Fake ads & airdrops — Google/social media ads and "free token" offers leading to wallet drainers
- AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
- Use a hardware wallet (Ledger, Trezor). Never store large amounts in browser wallets
- Bookmark official sites — never click links from emails, DMs, or ads
- Read every approval — verify permissions before signing. Reject unlimited approvals
- Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
- "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines