Analysis of leocopilot.online indicates active credential-harvesting phishing infrastructure as of July 12, 2026. The domain, registered on March 24, 2026, through a hosting provider, resolves to 104.21.86.22, a Cloudflare IP address located in Canada. Infrastructure analysis reveals Cloudflare nameservers (arnold.ns.cloudflare.com, meg.ns.cloudflare.com) and an SSL certificate issued by Let's Encrypt, suggesting a deliberate attempt to appear legitimate while masking the true origin. The domain is flagged by two security vendors and appears on one blocklist, with a trust score of 9/100 from independent assessment tools, reinforcing its classification as high-risk. The page title 'Leo' provides limited insight into the specific target or brand impersonation, though the domain name may suggest an attempt to mimic a legitimate service or platform. No confirmed phishing kit or brand association is currently identified in available intelligence. The HTTP 200 status confirms the site is operational, and Cloudflare Browser Insights detection implies active user interaction tracking. Defenders should treat this domain as an active threat, blocking resolution at the DNS level and monitoring for related indicators, including the IP address and nameserver pairings. Further analysis of captured payloads or user reports may clarify the exact phishing methodology or targeted entities.
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.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-13 22:27:16 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 22:29:29 UTClast content: 2026-10-13 22:27:16 UTC
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.
技术 · 3 identified
Cloudflare Browser Insights
AnalyticsRUM
Performance monitoring tool that measures website speed from real users.
Last analyzed Previous stored snapshot: 4 detections
alphaMountain.ai
Chong Lua Dao
Gridinsoft
Seclookup
网站性能分析
Google PageSpeed Insights — mobile performance audit of leocopilot.online· checked Apr 22, 2026
100
Good
Performance
FCP
0.77s
First Contentful Paint
LCP
1.53s
Largest Contentful Paint
CLS
0.01
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.77s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
威胁响应 Pipeline
发现
Analysis
Monitoring
8 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
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.
(LT)
