VirusTotal
13 / 89 engine detections
打开报告“Вход”
钓鱼: glavniyadmi.digital — 最后已知的活跃状态 (HTTP 302). 证据摘要: VirusTotal 13/89 (alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar); Spamhaus DBL_SPAM…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
13 / 89 engine detections
打开报告DBL_SPAM
4 community references
打开报告provider verdict: clean
打开报告No threat flag
打开报告No malicious flag
打开报告Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
Analysis of glavniyadmi.digital indicates that the domain is currently listed as active and associated with a generic phishing campaign. The domain was submitted to VirusTotal where 91 antivirus and URL scanners evaluated the content; none returned a positive detection. The report explicitly notes that the lack of detections does not constitute evidence of legitimacy, and the domain should remain under observation. Independent threat‑intelligence feeds have flagged the domain: PhishDestroy has added it to its blocklist, and it is present on one additional security blocklist.
No public safe‑browsing verdicts, Open Threat Exchange (OTX) sightings, or registrar‑level abuse records have been disclosed for this host. The hosting infrastructure, IP address, ASN, and SSL certificate details have not been released in the available data, limiting infrastructure‑level attribution. The page title and any brand‑specific cues have not been published, so the exact lure or credential‑harvesting technique cannot be confirmed at this time. Given the limited observable evidence, the confidence level for a phishing classification remains moderate, and further monitoring is recommended.
Defenders should block the domain at perimeter firewalls, DNS resolvers, and proxy layers, and incorporate the hash of the URL into URL filtering solutions. Continuous re‑scanning with VirusTotal or similar services is advisable to capture any future payload changes. Organizations that receive suspicious emails referencing glavniyadmi.digital should advise users not to click any links and to report the messages to their security operations center for additional context.
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.
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.
ns1.anycastdns.czns2.anycastdns.czLocation describes the IP network.
e513563b47469eec620149a3f9dbf26e9359e912dbc52585cbc60ecc8eb4cbbewww.glavniyadmi.digitalSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.glavniyadmi.digitalDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of glavniyadmi.digital · checked Aug 3, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
glavniyadmi.digital
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
未知→redirected
http_redirect
4 community references
View source13/89 engine detections
View sourcePage captured
View sourceNo threat flag
View sourceglavniyadmi.digital
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
glavniyadmi.digital)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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.