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.
探测与规避分析
隐身和流量分配检查
未观察到在存储的扫描图像中未观察到遮蔽现象
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
未观察到
伪装评分
0/6
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='gevigu.digital', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
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-13 01:09:53 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.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
12 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.
(US)
