Security engines reporting a detection: 14. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
The domain share-moonshot.network was registered on June 07, 2026 through PDR Ltd. d/b/a PublicDomainRegistry.com. Automated resolution points to the IPv4 address 69.46.46.62, which is currently associated with active hosting. VirusTotal reports that 14 out of 91 scanned security vendors have flagged the domain as malicious, indicating a consensus of moderate detection confidence. Independent blocklist aggregators list the domain on three separate blocklists, and it is explicitly blocked by PhishDestroy, MetaMask, and SEAL, reinforcing its classification as a high‑risk phishing infrastructure. The threat intelligence profile assigns the domain a generic phishing label and a high risk rating, and its status remains active as of the report date, July 29, 2026.
Observations are limited to infrastructural metadata; no public page title, SSL certificate details, HTTP response codes, or content snapshots have been disclosed. Consequently, the specific phishing lure, target brand, or credential‑capture technique employed by the site cannot be confirmed at this time. The absence of such content analysis introduces uncertainty regarding the precise victim‑facing tactics and the potential for additional malicious payloads. Defenders should prioritize immediate containment actions.
Network perimeter devices and DNS resolvers ought to deny queries for share‑moonshot.network and its resolved IP address 69.46.46.62. Inclusion of the domain in local and cloud‑based URL filtering policies, as well as subscription to the blocklists that already list it, will reduce exposure. Continuous monitoring of outbound connections to the IP and correlation with endpoint logs can help identify compromised hosts. Finally, security teams should periodically re‑query VirusTotal and other sandbox services for updated behavioural indicators should the site become publicly reachable.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='share-moonshot.network', port=80): Max retries exceeded with url: / (Caused by NewConnecti
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Waiting
Domain details
Domain
IP Reputationabuse score 0/1000 reportschecked Jul 29, 2026
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
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.
Accreditation is a contract, not a safety certification.
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.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 01:12:50 UTC
RDAP registrationUnknown
Observed timelinecurrent episode first observed: 2026-09-30 16:14:55 UTCfirst terminal observation: 2026-09-30 16:14:55 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-08-05 23:05:48 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-07-29 08:27:18 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 69.46.46.62.
Threat Response Pipeline
Discovery
Analysis
Monitoring
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
share-moonshot.network detected and queued for full analysis
Jun 8, 2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Aug 6, 2026
Time to First Unavailability
1398 hours elapsed from detection to the first unavailable observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
2 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · share-moonshot.network
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
(US)
