wareumtauschens805.ink returned an HTTP 502 status during an HTTP check on 2026-10-01, a recorded server error at that moment. The same domain was first observed on 2026-09-13, the date also recorded for its registration and an SSL scan.
Recorded Evidence
An HTTP check on 2026-10-01 recorded a 502 status for wareumtauschens805.ink. OTX noted four pulses for this domain on 2026-09-13. VirusTotal, checked on 2026-09-16, reported 12 detections across 89 scanners. The registration date was 2026-09-13, and the SSL scan of that date listed Let's Encrypt / YE1 as issuer. PhishDestroy holds an internal listing for this domain.
Interpretation
The HTTP record documents only the response observed at that check, not the domain's full content or later availability. The OTX pulse count and the VirusTotal detection ratio come from separate platforms measured on different dates, so they describe distinct catalogues rather than one combined signal. The PhishDestroy listing is a publisher-owned record, and the first-observed date marks when this domain entered the collected evidence.
Recommended Actions
Preserve the HTTP check record for wareumtauschens805.ink and the VirusTotal detection record as separate items for later comparison. Retain the OTX pulse entry and the PhishDestroy internal listing alongside them, since each documents a different source's observation. Compare these saved records against future checks of the same domain to see whether new observations appear.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='wareumtauschens805.ink', port=80): Max retries exceeded with url: / (Caused by NewConnecti
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:26:28 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-15 22:18:16 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-15 22:18:16 UTC → 2026-09-30 16:14:55 UTC · 353.94hmidpoint estimate ≈ 2026-09-23 07:16:35 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.
技术 · 2 identified
Cloudflare
CDN
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Last analyzed Previous stored snapshot: 5 detections
Abusix
alphaMountain.ai
CRDF
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
MalwareURL
SOCRadar
VIPRE
Webroot
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-14 22:19:12 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-13 23:03:17 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-13 12:38:59 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 104.21.33.251.
威胁响应 Pipeline
发现
Analysis
Monitoring
13 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.
