VirusTotal
4 / 91 engine detections
打开报告“Account disabled by server administrator”
被列入黑名单的域名: mainnetinpinfix-deg.website — 最后已知的活跃状态 (HTTP 200). 证据摘要: VirusTotal 4/91 (alphaMountain.ai, Chong Lua Dao, Gridinsoft, LevelBlue); 3 external…
为保留原始取证记录,下方的 PhishDestroy AI 详细分析仍使用英文。
4 / 91 engine detections
打开报告24 community references
打开报告provider verdict: safe
打开报告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
The domain mainnetinpinfix-deg.website was registered on 21 February 2026 through Global Domain Group LLC. It resolves to the IPv4 address 65.21.174.205, which is advertised as part of the Hetzner Online GmbH network (AS24940) and geolocated in Finland. The authoritative name servers are ns41.link-host.net and ns42.link-host.net, and the site presents a valid Let's Encrypt R13 certificate, indicating recent TLS provisioning.
The web service is front‑ended by Nginx and includes a reference to Liveinternet, suggesting a generic hosting stack. HTTP requests to the root path return a 403 status code, and the page title reported by the scanner is “Account disabled by server administrator”. Such a response is typical of a placeholder or access‑denied page used to mask malicious activity while preserving a legitimate TLS handshake.
Reputation data classifies the domain as a high‑risk account‑takeover campaign. Gridinsoft assigns a trust score of 0 / 100, and VirusTotal records five detections out of ninety‑five scanned security vendors. The domain is listed on four public blocklists—PhishDestroy, Polkadot, Enkrypt, and Codeesura—demonstrating that multiple independent feeds have already flagged it. The combination of a recent registration, low trust score, and multiple detections aligns with the observed “Account Takeover” scam type.
Uncertainties remain regarding the specific payload or credential‑harvesting mechanisms hosted behind the 403 page, as no malicious payload was captured in the current scan. Defenders should treat the domain as hostile: enforce DNS‑level blocking, add the IP address 65.21.174.205 to network deny lists, and monitor TLS logs for connections to the Let's Encrypt certificate. Continuous re‑evaluation is advised in case the site transitions from a placeholder to an active credential‑stealing page.
Last checked
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.
ns42.link-host.netLocation describes the IP network.
bc161114c5fb8fe28754fd1f392d946d185f9637f84ea9f03236793264042334www.mainnetinpinfix-deg.websiteSaved 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.mainnetinpinfix-deg.websiteDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of mainnetinpinfix-deg.website · checked Apr 27, 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.
alive_content: raw=ok; http=200; via=https_proxy; server=Apache
mainnetinpinfix-deg.website
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
未知→live_content
content_served
不可用→可访问
https://radar.cloudflare.com/scan/cbe0b096-103f-40da-a91a-c465ef5fd4c6
https://radar.cloudflare.com/scan/cbe0b096-103f-40da-a91a-c465ef5fd4c6
可访问→不可用
No threat flag
View source24 community references
View source4/91 engine detections
View sourcePage captured
View sourcemainnetinpinfix-deg.website
View source由 1 名社区成员报告;首次发现于 2025年10月21日
Listed 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 ↗
mainnetinpinfix-deg.website)即使你并不了解所有细节—— 不管怎样都要提交报告. 即使信息不完整,对调查仍有帮助。
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.