This domain, claims-brevis.network, was identified as part of a phishing infrastructure targeting Discord users through a fraudulent airdrop registration scheme. Registered on February 21, 2026, the domain resolved to IP address 172.67.182.231, hosted on Cloudflare's network (AS13335) in the United States. The site presented itself as a "Brevis Airdrop Registration Portal," a title consistent with social media phishing campaigns designed to harvest credentials or sensitive information. Analysis indicates the domain was flagged by seven security blocklists, including PhishDestroy, MetaMask, ScamSniffer, Polkadot, and SEAL, reflecting broad detection across the security community.
Four of 93 security vendors on VirusTotal marked the domain as malicious, further corroborating its abusive nature. The domain's SSL certificate was issued by WE1, a low-assurance provider often associated with short-lived phishing campaigns. Gridinsoft assigned a trust score of 0/100, reinforcing its classification as high-risk. Infrastructure analysis reveals the use of a known phishing kit labeled "Airdrop Scam," which aligns with the observed page title and scam type.
As of July 24, 2026, the domain has been taken offline, though defenders should monitor for re-emergence under similar naming conventions or hosting patterns. Organizations are advised to block the domain and associated IP at the perimeter, update detection rules for airdrop-themed phishing lures, and alert users to the risks of unsolicited token distribution offers. The exact content of the phishing page remains unanalyzed, but the available evidence confirms its intent to impersonate Discord-related services for fraudulent purposes.
スキャナーに関する注記:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='claims-brevis.network', port=80): Max retries exceeded with url: / (Caused by NewConnectio
DOM Analysisanalyzed 2026年3月24日score 63/1001 brand signal
ページタイトル
Brevis Airdrop Registration Portal
Impersonates
Discord
TLS証明書
Hostname coverage not recorded·
発行者 WE1
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
172.67.182.231
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare
Edge-IP の評判はこのドメインに起因しません。
Location describes the IP network.
TLS証明書
Issuer
WE1
Hostname coverage
Hostname coverage not recorded
Collection source
PhishDestroy collector
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-11 01:08:16 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-05-06 20:13:19 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-05-06 20:13:19 UTC → 2026-09-30 16:14:55 UTC · 3,524.03hmidpoint estimate ≈ 2026-07-19 06:14:07 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.
11 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.
