support-ellipal[.]com
PhishDestroy first observed support-ellipal.com on Aug 18, 2026. The hostname uses “support,” a pattern consistent with a support lure; no target brand is confirmed from stored content. Current evidence score: 66/100 (high).
Positive findings are stored from 4 sources: VirusTotal, MetaMask, SEAL, and Spamhaus DBL. On Aug 18, 2026 at 18:30 UTC, VirusTotal recorded 1 detections among 91 engines: Fortinet; Spamhaus DBL: DBL_PHISH. MetaMask and SEAL listed the hostname in the separate external-blocklist snapshot on Aug 18, 2026 at 18:20 UTC. Non-positive and contextual checks: Google Safe Browsing returned no flag on Aug 18, 2026 at 19:05 UTC. URLScan captured the page on Aug 18, 2026 at 18:24 UTC.
The collector marked the hostname reachable on Aug 18, 2026 at 18:24 UTC, but did not retain the HTTP response code. Registration records for the domain list NameSilo, LLC as the registrar and Aug 1, 2026 as the creation date. Registration preceded first observation by 16 days. At collection time, the hostname resolved to 38.97.56.209 on AS58087 (Florian Kolb). The recorded endpoint location is Frankfurt am Main, DE. The evidence archive retains 2 visual captures from PhishDestroy and URLScan; no page title was retained, so the captures preserve the landing-page appearance. TLS metadata lists Let's Encrypt as the certificate issuer with validity through Nov 9, 2026; checked Aug 18, 2026 at 19:02 UTC.
The content indicators and 4 positive source findings support the current phishing classification. The stored fields do not identify an impersonated brand or victim interaction.
Network Security Intelligence Registrar context
Threat Response Pipeline
Public Blocklist Status
Stored Capture
Domain Intelligence
Technical detailsDNS, SSL SANs, timestamps
ICANN OVERSIGHT
Accreditation and RAA context
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.
Technologies · 3 identified
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
www.rfc-editor.org 100% confidenceHTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
httpwg.org 100% confidenceVirusTotal Analysis
Evidence & External Reports
PD-20260818-0364F8 Recipient: abuse@datalix.de Were You Affected by This Site?
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Report to Your Local Authorities
Select your country to get official cybercrime contacts, or create a complaint draft →.
Check Any Domain
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowReport Phishing
Submit suspicious domains to our threat database — protect the community
ReportLive Threat Feed
Recent phishing reports and observed availability changes
MonitorStay Informed, Stay Safe
Monitor live threats or contest this listing if you believe it's a false positive