detailednewsreport.com returned HTTP status 502 in an HTTP check dated 2026-10-01, a recorded server response rather than a statement about all content on the domain. The domain was first observed on 2026-09-06, according to the recorded observation timeline.
Recorded Evidence
The domain's registration date is recorded as 2025-07-31 with registrar NameCheap, Inc. An HTTP check dated 2026-10-01 recorded status 502, while the first observation of the domain is dated 2026-09-06. VirusTotal, checked 2026-09-17, recorded 15 detections across 89 scanners. OTX, checked 2026-09-17, recorded 4 pulses, and a PhishDestroy internal listing is also recorded. The IP address 104.219.250.37 is associated with the United States and organization 3402 East University.
Interpretation
The named source records describe different kinds of observation rather than a single unified finding. The HTTP response, VirusTotal detections, OTX pulses and the PhishDestroy internal listing each measure something distinct, so they should be read separately. The recorded dates span from the first observation through the later checks, but a shared or differing calendar date does not by itself establish simultaneous measurement or a trend.
Recommended Actions
Preserve the HTTP check record for detailednewsreport.com and the VirusTotal record as separate source documents for later comparison. Also retain the OTX record and the PhishDestroy internal listing so each can be reviewed on its own terms. Compare these source records against future observations of the same domain, keeping each source's own values distinct rather than merging them into one conclusion.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='detailednewsreport.com', 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:15:53 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-06 20:28:22 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-06 20:28:22 UTC → 2026-09-30 16:14:55 UTC · 571.78hmidpoint estimate ≈ 2026-09-18 18:21:38 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: 15 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
Lionic
SOCRadar
Sophos
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-15 10:00:18 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-15 09:13:12 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)
