omni-variational.io-uk.icu returned an HTTP status 502 during a check on 2026-10-01, indicating a recorded server error at that time. This domain was also listed in the PhishDestroy internal catalogue, providing an additional source observation.
Recorded Evidence
A VirusTotal scan on 2026-09-14 reported 9 detections out of 89 scanners for omni-variational.io-uk.icu. The domain was first observed on 2026-09-11, and a PageSpeed check on the same date recorded a performance score of 100. An SSL scan on 2026-09-11 identified the issuer as Google Trust Services / WE1. The domain is listed in the PhishDestroy internal catalogue as of the evidence record.
Interpretation
The recorded HTTP 502 status reflects only the server response observed on 2026-10-01 and does not provide information about other times or content. VirusTotal and PhishDestroy each offer distinct observations, with VirusTotal reporting detections from multiple scanners and PhishDestroy maintaining its own listing. The PageSpeed and SSL scan results are limited to their respective measurement dates and do not indicate ongoing characteristics.
Recommended Actions
For omni-variational.io-uk.icu, retain the VirusTotal scan and PhishDestroy listing records for future comparison. Review subsequent HTTP checks to monitor any change in response status. Keep the PageSpeed and SSL scan records as reference points, and continue to track updates in the domain's catalogue listing status.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='omni-variational.io-uk.icu', port=80): Max retries exceeded with url: / (Caused by NewConn
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
For the registrable domain io-uk.icu behind this subdomain, 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.
Certificate fingerprintf964f07906b83996a033760e01b6e045b3bcab2051a03c69cc7fa062dbea4cc9Certificate names · 1 SANs
io-uk.icu
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:40 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-09-11 10:08:39 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-11 10:08:39 UTC → 2026-09-30 16:14:55 UTC · 462.10hmidpoint estimate ≈ 2026-09-21 01:11:47 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: 9 detections
alphaMountain.ai
BitDefender
CRDF
ESET
G-Data
Gridinsoft
卡巴斯基
LevelBlue
SOCRadar
网站性能分析
Google PageSpeed Insights — mobile performance audit of omni-variational.io-uk.icu· checked Sep 11, 2026
100
Good
Performance
FCP
1.52s
First Contentful Paint
LCP
1.52s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.52s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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-11 22:08:20 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-09-11 14:48:00 UTC
VirusTotal scanner detections updated from 8 to 9. Added scanner alerts: Gridinsoft.
VirusTotal Detections Update2026-09-11 13:45:01 UTC
VirusTotal scanner detections updated from 7 to 8. Added scanner alerts: alphaMountain.ai.
VirusTotal Detections Update2026-09-11 13:14:06 UTC
VirusTotal scanner detections updated from 8 to 7. Resolved alerts: alphaMountain.ai.
VirusTotal Detections Update2026-09-11 11:41:26 UTC
VirusTotal scanner detections updated from 7 to 8. Added scanner alerts: SOCRadar.
Threat First Observed2026-09-11 10:07:31 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 104.21.34.154.
威胁响应 Pipeline
发现
Analysis
Notifications
Monitoring
14 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.
(FR)
