VirusTotal
9 / 95
“Azbit Login - Azbit Exchange Login To Account”
duplicate-disabled-385.invalid — 未验证. 品牌冒充:Facebook; 诈骗类型:Credential Phishing. 证据摘要: VirusTotal 9/95 (BitDefender, CyRadar, Fortinet, G-Data, Kaspersky); PhishDestroy score 77/100. 注册商: NiceNIC.
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
This domain, www.azbit-login.com, poses an elevated brand impersonation threat targeting Facebook. The site uses a deceptive page title, 'Azbit Login - Azbit Exchange Login To Account,' to trick users into believing they are accessing a legitimate Facebook login page. If users enter their credentials, they risk having their login information stolen, leading to potential unauthorized access to their accounts.
Analysis indicates that www.azbit-login.com has been flagged by 9 out of 95 security vendors on VirusTotal, suggesting that it is recognized as a potential threat by a significant portion of the security community. The domain was created on September 21, 2024, and is registered through NiceNIC International Group Co., Limited. Infrastructure analysis reveals that the domain resolves to the IP address 185.149.120.107, which is located in Russia (RU) under the AS57724 DDOS-GUARD LTD network. Additionally, the domain appears on one security blocklist and is currently offline.
If a user has visited www.azbit-login.com, they should immediately change their Facebook login credentials and enable two-factor authentication (2FA) to enhance their account security. It is also advisable to monitor their account for any unauthorized activity and report any suspicious incidents to Facebook. Users should be cautious of any links or messages directing them to unfamiliar login pages and verify the URLs before entering any sensitive information.
针对该主机的爬虫与浏览器观察记录,以及针对“Keitaro”式流量分配系统的实时指纹检测。
扫描说明: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-385.invalid', port=80): Max retries exceeded with url: / (Caused by New
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.
pns51.cloudns.netpns52.cloudns.netLocation describes the IP network.
10 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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
如果您输入了帐户凭据、个人或付款信息,或者从此域下载了文件,请立即采取措施。以下资源可帮助您报告事件并保护自己。
选择您所在的国家/地区以获取 官方网络犯罪联系人 或 创建投诉草稿 →。
Template-based draft · optional AI wording assistance requires separate consent