kelbrivon.com returned an HTTP status 502 during an HTTP check dated 2026-10-01, a server-side error response recorded on that date. The same domain was first observed on 2026-09-15, according to the recorded observation timeline.
Recorded Evidence
A VirusTotal check dated 2026-09-25 recorded 17 detections across 91 scanners for kelbrivon.com. An OTX check dated 2026-09-17 recorded 5 pulses naming the domain. The PhishDestroy internal listing for kelbrivon.com is recorded as true, and the blocklist check date is 2026-10-01. The domain's registration date is 2026-07-30, with NAMECHEAP INC named as registrar.
Interpretation
The HTTP 502 response describes only the reply recorded on its check date, not the domain's content or its status on other days. The VirusTotal detection count and the OTX pulse count come from separate checks on separate dates, so they measure different things and should not be merged into a single trend. The PhishDestroy listing and the HTTP response likewise originate from distinct sources, and the chronology from first observation through the later checks shows the order in which records were captured.
Recommended Actions
Preserve the HTTP status record, the VirusTotal result, the OTX pulses, and the PhishDestroy listing for kelbrivon.com as separate source records. Compare the VirusTotal record against the OTX record in one review, and compare the PhishDestroy listing against the HTTP record in another. Re-check each source on its own schedule so that later entries can be set beside the earlier ones.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='kelbrivon.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("
Latest HTTP observation未知Probe Inconclusive20%2026-10-13 10:09:36 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-15 18:23:30 UTC
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 Previous stored snapshot: 16 detections
alphaMountain.ai
BitDefender
CRDF
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
Lionic
PREBYTES
SafeToOpen
Seclookup
SOCRadar
Sophos
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-10-13 22:29:41 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-15 18:19:43 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 217.60.196.141.
威胁响应 Pipeline
发现
Analysis
Notifications
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.
(US)
