zirbankasiai.click returned an HTTP status code 200 during a check on 2026-10-01, indicating a successful server response at that time. The domain was first observed in records on 2026-09-19, providing a reference point for its initial appearance in monitoring systems.
Recorded Evidence
A VirusTotal scan on 2026-09-29 recorded 15 detections out of 91 total scanners for zirbankasiai.click. OTX noted 3 pulses in an observation dated 2026-09-21. The domain is included in the PhishDestroy internal listing. Its registrar is Spaceship, Inc., and the registration date is 2026-06-28.
Interpretation
The HTTP status code 200 documents the server's response on the date of the check, without describing the nature of the content. VirusTotal and OTX provide separate security-related observations, each recorded on different dates, and the PhishDestroy internal listing adds another layer of monitoring. These sources together offer a timeline of how zirbankasiai.click has been tracked by distinct security platforms.
Recommended Actions
Retain the HTTP status record and the VirusTotal detection report for zirbankasiai.click for future reference. Compare the OTX pulse count and the PhishDestroy internal listing with subsequent observations to monitor any changes. Preserve the first observation date as a baseline for ongoing review.
DOM Analysisanalyzed 2026年9月22日score 98/1001 brand signal
Submitted URLhttp://zirbankasiai.click/
Favicon Hash
ICANN OVERSIGHT
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-14 10:28:25 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-14 10:28:25 UTClast content: 2026-10-14 10:28:25 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: 15 detections
alphaMountain.ai
BitDefender
CRDF
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
卡巴斯基
Lionic
Seclookup
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.
Threat First Observed2026-09-19 21:56:39 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 185.62.57.10.
威胁响应 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)
