This domain is flagged as an elevated-risk brand impersonation threat targeting X.com users. Analysis indicates the infrastructure was configured to deceive victims into disclosing login credentials or other sensitive information by mimicking the authentic platform. The domain is currently offline but was operational long enough to establish malicious intent and technical indicators of compromise. Infrastructure analysis reveals vertexneobase.digital resolved to IP address 104.21.5.116, hosted on Cloudflare's network (AS13335) in the United States. The domain was registered through Cloudflare, Inc., a common tactic to obscure ownership and leverage proxy services. The page title 'Welcome to nginx!' suggests a default server configuration, often used in phishing kits to quickly deploy fraudulent login portals. VirusTotal reports 11 out of 95 security vendors flagged this domain as malicious, while it appears on one security blocklist. The SSL certificate, issued by Google Trust Services (WE1), provides a false sense of legitimacy to unsuspecting users. The domain is also blocked by PhishDestroy, further confirming its classification as a phishing threat. Mitigation steps for this specific threat type include immediate blacklisting of the domain and its associated IP address (104.21.5.116) across all network security controls. Organizations should update endpoint protection rules to detect and block access to domains with similar naming patterns (e.g., 'neobase,' 'vertex') impersonating X.com. Security teams are advised to monitor for credential reuse attempts, particularly from users who may have interacted with this domain prior to its takedown. Additionally, user awareness training should emphasize the risks of default server pages (e.g., nginx welcome screens) as red flags for phishing sites. Network logs should be reviewed for any prior connections to this domain or its IP to assess potential compromise.
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-13 22:32:44 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 22:32:44 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.
技术 · 2 identified
Cloudflare
CDN
Web infrastructure and security company providing CDN, DDoS mitigation, and DNS services.
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.
VirusTotal Detections Update2026-03-09 02:53:42 UTC
VirusTotal scanner detections updated from 11 to 10. Added scanner alerts: ADMINUSLabs. Resolved alerts: Seclookup, Trustwave.
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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.
(US)
