e.me - URL scan, 21 Aug 2026
MalwareAnalyzer by Cyble scanned e.me and returned a unknown verdict (score -12). The page resolved to 159.89.90.207 on DigitalOcean, LLC in US. 11 domains and 1 IP were contacted, over 4 HTTP requests. 1 malware sample communicates with this URL. This is a point-in-time observation from 21 Aug 2026; the page may have changed since.
Scan result
- Verdict: unknown (score -12) · Confidence 15%
- Scanned URL:
https://e.me/ - Domain: e.me · IP: 159.89.90.207 · AS14061 · US
- Server: Caddy
- Page title: Need ideas? Try our free AI for name inspiration.
- HTTP status: 200 · text/html; charset=utf-8
- TLS issuer: C=US, O=Let's Encrypt, CN=YE1 · valid to Sep 25 03: · subject CN=e.me
- HTTP requests captured: 4
- Scan tier: fast · observed 2026-08-21 22:30:20 UTC
Malware communicating with this URL (1)
These samples were observed contacting or being served from e.me. Each links to its full analysis.
- c3a9a848a694ed52090673170ce33477e38adb02c1085cd90193e47e57f5014a - referenced ·
c3a9a848a694ed52090673170ce33477· first seen 2026-08-21
Antivirus & YARA (0 of 48 engines)
No engine flagged this page's content.
Why this verdict
- Valid TLS, no impersonation or off-origin credential post
Detected technologies
- Caddy
- Google Analytics
- jQuery
- Bootstrap
Contacted infrastructure
- 159.89.90.207 - AS14061 DigitalOcean, LLC (United States)
Observed indicators
- e.me
- cdn.jsdelivr.net
- ajax.googleapis.com
- www.googletagmanager.com
- domain.me
- www.facebook.com
- www.youtube.com
- www.instagram.com
- www.linkedin.com
- www.tiktok.com
- twitter.com
- 159.89.90.207
- https://e.me/
- https://e.me/images/DotMe-32x32.png
- https://e.me/images/DotMe-192x192.png
- https://e.me/images/DotMe-180x180.png
- https://e.me/css/style.css
- https://e.me/css/namegenie.css
- https://cdn.jsdelivr.net/npm/bootstrap@5.0.2/dist/css/bootstrap.min.css
- https://ajax.googleapis.com/ajax/libs/jquery/3.7.1/jquery.min.js
Questions about e.me
- Is e.me safe?
- The scan of e.me on 21 Aug 2026 reached no verdict either way (score -12). Too little was captured to judge it, which is an unknown rather than a pass.
- What malware is associated with e.me?
- 1 analysed samples communicate with this URL.
- How was e.me checked?
- A static pass resolved DNS, captured TLS and headers and followed the redirect chain, and where the fast tier allows, a headless browser rendered the page and recorded every request. Egress is SSRF-locked. Signatures that matched only page text are weighted far below one that matched a served file, because a page documenting malware matches the same rules.
Scanned at the fast tier - see how URL scanning works.
Scan another URL · Latest analyzed threats · All scans of e.me
Scanned on MalwareAnalyzer by Cyble · Open interactive scan