On 28 May 2025 the domain gevigu.digital was registered through Cloudflare, Inc. and delegated to the Cloudflare name servers abby.ns.cloudflare.com and seth.ns.cloudflare.com. The domain resolves to the IPv6 address 2606:4700:3036::6815:557b, which belongs to AS13335 operated by Cloudflare in the United States. No TLS certificate is presented, indicating that HTTPS connections are not established. The only visible HTML element reported is the page title “WhatsApp Bot”, and the domain is listed as impersonating the brand argent. Threat intelligence sources have identified the domain in eighteen AlienVault OTX pulses, and it is currently flagged by one external blocklist and by the PhishDestroy protection service.
VirusTotal analysis shows that seventeen of ninety‑five scanning engines have raised detections against the domain, reflecting a mixed security assessment. Gridinsoft assigns a trust score of zero out of one hundred, reinforcing the malicious classification. The domain has been taken offline as of the report date, July 23 2026, but its recent activity and infrastructure remain relevant for correlation with other incidents. Defenders should update internal blocklists to include gevigu.digital and monitor for any future resurrection of the host on Cloudflare’s network, particularly the associated IPv6 address.
Network traffic to the Cloudflare IP range should be inspected for anomalous patterns, and DNS logs should be queried for recent resolutions of gevigu.digital. Because the site lacks a valid SSL certificate, any attempted HTTPS connections will fail, which can be used as an indicator of compromise in endpoint monitoring. Analysts should also reference the eighteen OTX pulses for context on related campaigns targeting argent users and consider sharing the indicator set with upstream threat sharing communities. Until further forensic analysis is performed, the domain should be treated as an active impersonation risk.
DOM Analysisanalyzed 2026年4月23日score 83/1002 brand signals
Submitted URLhttp://gevigu.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:45 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-05-11 21:58:29 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-05-11 21:58:29 UTC → 2026-09-30 16:14:55 UTC · 3,402.27hmidpoint estimate ≈ 2026-07-21 19:06:42 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='gevigu.digital', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
gevigu.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)
