On 2026-10-01, sharepoint.process.o9219dsdk.passkeypoint052skljj43auth04.phnia.com returned an HTTP 502 status. returned HTTP status 502 on 2026-10-01, a recorded response from that day's HTTP check. The same domain, written in full as sharepoint.process.o9219dsdk.passkeypoint052skljj43auth04.phnia.com, was first observed on 2026-09-11, the earliest date in this evidence set.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 502, while the first observation of the domain is dated 2026-09-11. VirusTotal recorded 17 detections across 89 scanners on 2026-09-11. The SSL scan on 2026-09-11 identified the issuer as Let's Encrypt / YE2. The IP address 79.133.56.155 is recorded in Germany under UltaHost Inc. The publisher-owned PhishDestroy catalogue listed the domain, and the blocklist check is dated 2026-10-01.
Interpretation
The PhishDestroy listing and the VirusTotal detection count are separate source records, and neither should be combined into a single verdict. The HTTP 502 response describes only the reply recorded on that date, not the domain's content or its present availability. Because the first observation and the VirusTotal and SSL scans share the 2026-09-11 date, they are contemporaneous records, but a shared date does not make their measurements directly comparable.
Recommended Actions
Preserve the PhishDestroy listing and the VirusTotal record for sharepoint.process.o9219dsdk.passkeypoint052skljj43auth04.phnia.com as separate source records. Compare the HTTP response record with the first-observation record to document how the domain appeared across the evidence set. Retain the SSL scan record alongside these sources so the certificate observation remains available for later review.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='sharepoint.process.o9219dsdk.passkeypoint052skljj43auth04.phnia.com', port=80): Max retrie
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:44 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-11 04:15:13 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-11 04:15:13 UTC → 2026-09-30 16:14:55 UTC · 468.00hmidpoint estimate ≈ 2026-09-20 22:15:04 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.
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-11 23:01:55 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-11 03:39:20 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 79.133.56.155.
威胁响应 Pipeline
发现
Analysis
Monitoring
9 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)
