Analysis of the domain fix-brevis.network indicates that it was registered on February 21, 2026 and is hosted behind Cloudflare’s network (AS13335) with the IP address 172.67.204.219 located in the United States. The site presented a page titled "Brevis Claim Portal" and was classified as a crypto scam. VirusTotal scans show that four of ninety‑five security vendors flagged the domain as malicious, confirming that at least a subset of scanners identified suspicious behavior.
The domain is listed on five public blocklists—PhishDestroy, ScamSniffer, Polkadot, Enkrypt, and Codeesura—and appears in a single AlienVault OTX pulse, reinforcing the consensus that the infrastructure is being used for illicit activity. An SSL certificate labeled WE1 was observed, but the certificate alone does not mitigate the risk associated with the underlying content. As of the report date, July 24, 2026, the site is reported offline, which may be a temporary takedown or an intentional shutdown by the operators.
Defenders should continue to block the domain at network perimeter devices and update any URL filtering policies to include the listed blocklists. Incident response teams should monitor for related C2 infrastructure that may reuse the same Cloudflare IP range, and threat‑intel analysts should correlate any future sightings of the page title or similar claim‑portal terminology with existing crypto‑scam campaigns. Because the domain’s current offline status prevents real‑time content inspection, further investigation is limited to the observed metadata; any additional indicators—such as payload hashes or phishing kit fingerprints—remain unknown at this time.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='fix-brevis.network', port=80): Max retries exceeded with url: / (Caused by NewConnectionEr
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:09:34 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-04-05 23:55:00 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-04-05 23:55:00 UTC → 2026-09-30 16:14:55 UTC · 4,264.33hmidpoint estimate ≈ 2026-07-03 20:04:57 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.
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
