VirusTotal
6 / 92
Interpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“undefined”
Assessment based on the stored source evidence below. Review sources →
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@dynadot.com.
The latest stored availability evidence still shows the domain reachable; 7 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.
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
6 / 92
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
2 det.
Alerts refer to the preserved scan. They do not describe the current state of the site.
no community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
stored report
Report A preserved page image documents what the collector received; a capture is not a safety verdict.
Analysis completed
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Stored narrative · generated . Provider checks below retain their own observation dates.
On 2026-10-07, moon1.bfsx.net returned an HTTP 200 status code, showing that a web server responded to requests on that date. The domain was also recorded in the PhishDestroy internal catalogue, providing an additional source for its observation.
VirusTotal reported 1 detection out of 92 scanners for moon1.bfsx.net on 2026-10-07. The SSL certificate for the domain was issued by Google Trust Services / WE1 and scanned on 2026-10-07. The domain was first observed and checked for HTTP responses on 2026-10-07, and its presence in the PhishDestroy internal listing was recorded the same day.
These records indicate that moon1.bfsx.net was observed by multiple sources on 2026-10-07, including a web server response and a VirusTotal scan. The PhishDestroy catalogue and VirusTotal offer distinct external perspectives on the domain's status as of the recorded date.
Review the VirusTotal and PhishDestroy records for moon1.bfsx.net to track its status across different sources. Preserve the HTTP response and SSL certificate scan details for future reference and comparison with subsequent observations.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
Edge-IP reputation is not attributed to this domain.
mckinley.ns.cloudflare.comyew.ns.cloudflare.comLocation describes the IP network.
81fec4e7816ea4ce213b2662c29297c3fce4b149f7104690f5d71db65b3799fbbfsx.netSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
188.114.97.3.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-20261007-739164 Recipient: abuse@dynadot.com Registrar: Dynadot LLC / Dynadot Inc (United States) Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
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