On 2026-10-01, elfcesnaticsd.shop returned an HTTP 502 status code in a recorded check. The same record set shows the domain first observed on 2026-08-27, giving a span of recorded observations rather than a single point.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 502 for elfcesnaticsd.shop. A first observation date of 2026-08-27 is also recorded for this domain. VirusTotal recorded 8 detections across 90 scanners on 2026-09-06. OTX recorded 4 pulses on 2026-09-04. The publisher-owned PhishDestroy catalogue carried an internal listing for this domain. The registrar recorded is Spaceship, Inc., and the IP organization recorded is Shopify, Inc.
Interpretation
The OTX count of 2026-09-04 and the VirusTotal count of 2026-09-06 were captured on different days, so they reflect separate snapshots rather than one synchronized view. The HTTP response of 2026-10-01 is later than both, meaning the status code and the detection counts describe different moments. The PhishDestroy listing and the first observation of 2026-08-27 also sit at different points, so a reader can compare dates without treating any single record as current.
Recommended Actions
Anyone reviewing elfcesnaticsd.shop should retain the dated records exactly as captured, including the 2026-10-01 HTTP status and the 2026-09-06 VirusTotal figures. Subsequent checks should be logged with their own dates so they can be compared against the 2026-08-27 first observation and the 2026-09-04 OTX entry. During review, avoid submitting passwords, payment details or other sensitive information to the domain.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='elfcesnaticsd.shop', port=80): Max retries exceeded with url: / (Caused by NewConnectionEr
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.
Primary outcomeDNS 非活动reason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 01:14:21 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-08-27 05:28:14 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-08-27 05:28:14 UTC → 2026-09-30 16:14:55 UTC · 826.78hmidpoint estimate ≈ 2026-09-13 10:51:34 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.
Last analyzed First positive detection Previous stored snapshot: 2 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Gridinsoft
LevelBlue
PhishFort
SOCRadar
VIPRE
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
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.
Domain Status Transition2026-09-08 22:00:25 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-04 18:43:10 UTC
Domain ingestion complete. Initial state is marked as alive.
威胁响应 Pipeline
发现
Analysis
Monitoring
10 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.
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)
