VirusTotal
10 / 91
“Link Locked”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@alexhost.com.
The latest stored availability evidence still shows the domain reachable; 6 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
The domain myconnectfile.sbs was recorded in the PhishDestroy internal listing on 2026-10-05, documenting its presence in that publisher's catalogue on that date. OTX also referenced myconnectfile.sbs in four pulses, offering additional context for its mention in security-related sources.
PhishDestroy catalogued myconnectfile.sbs internally on 2026-10-05. OTX included the domain in four separate pulses as of 2026-10-05. The domain was registered through NameSilo, LLC on 2026-08-23, and an SSL certificate from ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2 was scanned on 2026-10-05.
The records from PhishDestroy and OTX indicate that myconnectfile.sbs appeared in both an internal listing and several OTX pulses on the same date. These observations provide a basis for comparing its presence in different security-related catalogues. Registration and SSL scanning details further document the domain's configuration at the time.
To support future reviews of myconnectfile.sbs, retain the PhishDestroy internal listing and OTX pulse records for reference. Compare these sources if new evidence emerges or when assessing any changes in its recorded status.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
nginxScanner note: alive_content: raw=ok; http=200; via=https_proxy; server=nginx
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
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.dnsowl.comns2.dnsowl.comns3.dnsowl.comLocation describes the IP network.
f24fbc2a8951f44f11e5d7228a2a08bed95d0707b8217ac9d7dbcd8cf90a7595www.myconnectfile.sbsSaved 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 myconnectfile.sbs · checked Oct 5, 2026
91.199.133.143. 11 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.
PD-20261005-7B6C9A Recipient: abuse@alexhost.com Policy Violations: Illegal Activities: Active phishing operation targeting victims Fraud & Deception: Impersonation of legitimate services Identity Theft: Collection of credentials under false pretenses Applicable Laws (US): 18 U.S.C. § 1343 - Wire Fraud 18 U.S.C. § 1030 - Computer Fraud and Abuse Act (CFAA) 15 U.S.C. § 45 - FTC Act (Deceptive Practices) Federal laws prohibit wire fraud, computer fraud, and deceptive business practices. Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
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