Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
s2hyperfoundation.xyz was observed with multiple security-related records, including a VirusTotal detection on 2026-10-04. The domain was also listed on external blocklists and internally by PhishDestroy, providing additional context for its recent network profile.
Recorded Evidence
VirusTotal checked s2hyperfoundation.xyz on 2026-10-04 and recorded 7 detections out of 92 scanners. On 2026-10-12, the domain appeared on the MetaMask and SEAL external blocklists. PhishDestroy internally listed the domain, and OTX pulses were recorded on 2026-10-12. The domain was registered through NICENIC INTERNATIONAL GROUP CO., LIMITED on 2026-10-03.
Interpretation
PhishDestroy's internal listing contains a record of s2hyperfoundation.xyz relevant to security assessments, while VirusTotal provides a measurement of scanner detections. OTX pulses offer additional context about the domain's network intelligence profile. The evidence covers a short timeline, allowing for a focused review of recent observations.
Recommended Actions
To support ongoing monitoring, retain the VirusTotal, PhishDestroy, and OTX records for s2hyperfoundation.xyz. Compare the external blocklist entries over time to track any changes in listing status. Use these dated records as references for future technical assessments or security reviews.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='s2hyperfoundation.xyz', port=80): Max retries exceeded with url: / (Caused by NewConnectio
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
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:35:37 UTC
RDAP registration未知
Observed timelinecurrent episode first observed: 2026-10-12 08:22:11 UTCfirst terminal observation: 2026-10-12 08:22:11 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.
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.
Threat First Observed2026-10-12 10:33:24 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 104.21.38.46.
威胁响应 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.
(RU)
PhishDestroy Investigation
