VirusTotal
11 / 91
On 24 July 2026 the domain verify-asterdex.network was flagged as a credential‑phishing infrastructure. An HTTP request to the root URL returns a 403 Forbidden response and the HTML title element contains the text “Just a moment…”. The site is protected by Cloudflare, as indicated by the presence of the nameservers christian.ns.cloudflare.com and novalee.ns.cloudflare.com, and the use of HTTP/3 protocol. DNS resolution points to the address 104.21.34.102, which is owned by AS13335 Cloudflare, Inc. and resides in the United States.
The TLS certificate presented by the server is issued by Google Trust Services and chains to the WE1 root, confirming that a legitimate certificate is being used to lend credibility to the malicious site. Reputation scoring from Gridinsoft assigns a trust score of 0 out of 100, reflecting a high confidence of malicious intent. VirusTotal analysis shows that ten out of ninety‑five scanning engines have identified the domain as malicious, and the domain appears on one public security blocklist. The anti‑phishing service PhishDestroy has already blocked the domain, demonstrating that at least one external mitigation platform has taken action.
No further details about the specific credential‑phishing campaign, such as targeted brand or login page structure, are available from the current evidence set; the only visible artifact is the generic “Just a moment…” title, which may be employed as a placeholder before redirecting victims to a credential‑capture page. The domain remains active, and its registration through Cloudflare, Inc. indicates that the operator is leveraging Cloudflare’s free or low‑cost hosting options. Defensive recommendations include adding verify-asterdex.network to DNS‑based deny lists, configuring web‑proxy and firewall rules to drop traffic to the associated IP address, and updating endpoint detection signatures to flag connections to the domain.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: cloudflare_challenge: raw=cf_challenge; http=403; via=https_proxy; server=cloudflare
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.
Edge-IP reputation is not attributed to this domain.
christian.ns.cloudflare.comnovalee.ns.cloudflare.comLocation describes the IP network.
69a3ebb21a9d21680cd7e0c98511ccb38565625aaf19c3ba99fcc240bfd5270dSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
15 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 Nov 30, 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