The domain moltevent.network was registered on February 27, 2026 through PDR Ltd. d/b/a PublicDomainRegistry.com and is hosted on Cloudflare’s network (AS13335) with the address 172.67.211.207 located in the United States. It resolves to two Cloudflare nameservers (jule.ns.cloudflare.com, martin.ns.cloudflare.com) and does not present an SSL certificate, indicating that any traffic to the site would be unencrypted. The observed page title is “x.com/”, suggesting the site attempts to impersonate the X platform.
No content beyond the title has been captured, and the site is presently taken offline. VirusTotal reports a single positive detection out of 93 scanned vendors, and the domain is listed on three public blocklists, including PhishDestroy, MetaMask, and SEAL. These listings corroborate the classification of the site as a generic phishing operation.
Given the limited infrastructure footprint—a single Cloudflare IP and no TLS—the threat’s exposure is constrained, but the presence on multiple blocklists indicates active abuse. Defenders should add moltevent.network to URL filtering policies, enforce blocking of the associated IP address, and monitor Cloudflare edge nodes for any re‑use of the address. Continuous re‑scanning of the domain and its IP is advised in case the site is re‑hosted or the certificate status changes.
RegistrationCreated Feb 27, 2026 (234d)—Expires Feb 26, 2027
Time to First Unavailability30h
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.
Technical detailsProvenance & timestamps
First DetectedFeb 27, 2026
DOM Analysisanalyzed Jul 29, 2026score 56/100
Submitted URLhttp://moltevent.network/
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
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.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
172.67.211.207
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
envoy
Edge-IP reputation is not attributed to this domain.
Nameservers 2
jule.ns.cloudflare.com
martin.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
E7
Valid until
2026-05-27 00:00:00
Validity
Stored certificate expired
Collection time
2026-03-15 05:52:36 UTC
Collection source
PhishDestroy collector
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-19 01:09:10 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-02-27 18:45:07 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-02-27 18:45:07 UTC → 2026-09-30 16:14:55 UTC · 5,157.50hmidpoint estimate ≈ 2026-06-15 05:30:01 UTC · precision very low · basis bounded
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.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · moltevent.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.
5 evidence signal groups linked1 stored notification recordsContent 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
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including moltevent.network)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
About this reportSources, observation dates and corrections
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.
(IN)
