This domain, bgruged.digital, is flagged as a brand impersonation threat targeting Argent, a cryptocurrency wallet service. Registered on October 16, 2025, through Cloudflare, Inc., the domain resolves to IP 104.21.44.38 (AS13335, Cloudflare, US) and was taken offline by the time of this assessment. The page title 'WhatsApp Bot' suggests an attempt to leverage messaging-based social engineering, though the exact content or attack chain remains unconfirmed due to the domain's offline status. No SSL certificate was detected, increasing the likelihood of interception or man-in-the-middle risks had the site remained active. Analysis indicates the domain appeared on one security blocklist (PhishDestroy) and was flagged by 17 of 95 security vendors in VirusTotal scans.
AlienVault OTX records show it was included in 17 threat intelligence pulses, reinforcing its malicious classification. Gridinsoft assigned a trust score of 0/100, further corroborating its high-risk status. Cloudflare nameservers (gwen.ns.cloudflare.com, logan.ns.cloudflare.com) are consistent with the registrar, a common pattern for threat actors leveraging Cloudflare's privacy and proxy services to obscure infrastructure. Defenders should treat this domain as a confirmed malicious resource. Blocklist it at DNS, proxy, and endpoint levels, and monitor for any re-registration or IP shifts.
Given the targeting of Argent users, prioritize alerting cryptocurrency-related teams or customers. While the domain is offline, historical resolutions to 104.21.44.38 should be reviewed for residual connections. No evidence links this domain to other campaigns, but its inclusion in multiple threat intelligence feeds suggests broader distribution. If the domain reactivates, capture forensic artifacts (HTTP headers, scripts, redirect chains) to determine the full attack vector.
DOM Analysisanalyzed 2026年4月23日score 10/1002 brand signals
Submitted URLhttp://bgruged.digital/
ICANN OVERSIGHT
認定と RAA の背景
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.
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-19 01:08:00 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-06-17 10:39:41 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-17 10:39:41 UTC → 2026-09-30 16:14:55 UTC · 2,525.59hmidpoint estimate ≈ 2026-08-09 01:27:18 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.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='bgruged.digital', port=80): Max retries exceeded with url: / (Caused by NewConnectionError
bgruged.digital
保存済みの結果
到達不能
Stored observation history11
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.
(US)
