Security engines reporting a detection: 15. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is report@abuse.bz.
The latest stored availability evidence still shows the domain reachable; 23 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations.
This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
zahabai.shop returned HTTP status 200 in an HTTP check recorded on 2026-10-02, the most recent dated observation in this evidence set. A separate PhishDestroy internal listing for the domain is also recorded, and the earliest observation in the set is dated 2026-09-20.
Recorded Evidence
The HTTP check dated 2026-10-02 recorded status 200 for zahabai.shop. A PhishDestroy internal listing for the domain is recorded as true. VirusTotal recorded 15 detections across 91 scanners in a check dated 2026-10-01. OTX recorded 5 pulses in a check dated 2026-09-21. The domain resolved to IP address 185.62.58.179, associated with country NL and organization Snel. An SSL scan dated 2026-09-20 recorded the issuer as ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2. PageSpeed recorded a performance score of 93 on 2026-09-20.
Interpretation
These records come from different sources with different collection dates, so they describe separate observations rather than a single measurement. The HTTP status, VirusTotal detections, OTX pulses, and PhishDestroy listing each reflect what that named source recorded on its own date. The chronology shows the earliest observation on 2026-09-20 and the latest on 2026-10-02, but the dates alone do not establish a trend or change in the domain's status.
Recommended Actions
Preserve the HTTP check record for zahabai.shop and the PhishDestroy internal listing as separate source records. Preserve the VirusTotal and OTX records in separate files so each can be compared independently. Compare the HTTP check record against the PhishDestroy listing in a later review, and compare the VirusTotal record against the OTX record separately. Retain the PageSpeed and SSL scan records alongside the others for future reference.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
RegistrationCreated May 10, 2026 (156d)—Expires May 10, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedSep 20, 2026
DOM Analysisanalyzed Sep 20, 2026score 98/1001 brand signal
Submitted URLhttp://zahabai.shop/
Favicon Hash
Case ID
ICANN OVERSIGHT
Accreditation and RAA context
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 observationLive contentOrdinary HTTP content served90%2026-10-13 10:21:50 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-13 10:21:50 UTClast content: 2026-10-13 10:21:50 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.
Technologies · 3 identified
J
jsDelivr
CDN
JSDelivr is a free public CDN for open-source projects. It can serve web files directly from the npm registry and GitHub repositories without any configuration.
Google PageSpeed Insights — mobile performance audit of zahabai.shop· checked Sep 20, 2026
93
Good
Performance
FCP
1.81s
First Contentful Paint
LCP
1.81s
Largest Contentful Paint
CLS
0.142
Cumulative Layout Shift
TBT
49ms
Total Blocking Time
SI
1.81s
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-29 01:47:52 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-09-24 22:06:38 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-09-20 13:48:58 UTC
VirusTotal scanner detections updated from 0 to 1. Added scanner alerts: SOCRadar.
Threat First Observed2026-09-20 10:04:46 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 185.62.58.179.
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
15 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
zahabai.shop detected and queued for full analysis
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.
The domain remains reachable or access-restricted; future checks may update this observation.
How we investigate & report
Public scans, evidence and abuse channels
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.
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
6 evidence signal groups linked1 reports recordedLast known active
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · zahabai.shop
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
