cromvoxs.org returned HTTP status 502 in an observation recorded on 2026-10-01, according to the HTTP check captured that day. The domain's registration date is listed as 2026-03-02 with Spaceship, Inc. as registrar.
Recorded Evidence
The earliest observation in this dataset is 2026-09-17, when the domain was first observed. On 2026-09-23, an SSL certificate issued by Let's Encrypt / YE2 was scanned. OTX recorded 5 pulses on 2026-09-25, and VirusTotal recorded 6 detections across 91 scanners on 2026-09-25. A publisher-owned PhishDestroy catalogue listing was also recorded, and the blocklist check occurred on 2026-10-01.
Interpretation
The OTX and VirusTotal observations share the 2026-09-25 date, while the SSL scan on 2026-09-23 and the HTTP check on 2026-10-01 fall on different days, so these records reflect separate points in time rather than one synchronized snapshot. The PhishDestroy listing is publisher-owned, and the first-observed date of 2026-09-17 precedes the other dated checks.
Recommended Actions
Retain the dated records for cromvoxs.org, including the HTTP 502 observation and the OTX and VirusTotal results, so later checks can be compared against them. When reviewing cromvoxs.org, avoid submitting passwords, payment details or other sensitive information, and compare any new observation with the dates already recorded.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='cromvoxs.org', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("S
Certificate fingerprint1ddf3176300d1dd5536d534e41005f0a018e2268a94ff74d9afea6f8b4321638Certificate names · 1 SANs
www.cromvoxs.org
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:32:57 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-24 10:00:27 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-24 10:00:27 UTC → 2026-09-30 16:14:55 UTC · 150.24hmidpoint estimate ≈ 2026-09-27 13:07:41 UTC · precision 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: 6 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Fortinet
Netcraft
SOCRadar
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.
VirusTotal Detections Update2026-09-25 10:33:06 UTC
VirusTotal scanner detections updated from 2 to 6. Added scanner alerts: Forcepoint ThreatSeeker, Fortinet, SOCRadar, alphaMountain.ai.
Domain Status Transition2026-09-24 22:00:46 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-23 15:53:11 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.
已捕获威胁
cromvoxs.org 已检测到并排入队，待进行全面分析
2026年9月17日
Spamhaus DBL
Spamhaus DBL recorded DBL_SPAM
2026年9月23日
Cloudflare Radar Report
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)
