VirusTotal
4 / 91
“Account disabled by server administrator”
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.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
nginx/1.26.3Scanner note: alive_content: raw=ok; http=200; via=https_proxy; server=nginx/1.26.3
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.
Google PageSpeed Insights — mobile performance audit of mainnetinpinfix-deg.website · checked Apr 27, 2026
13 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.
Reported by 1 community member, first seen Oct 21, 2025
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive