zimbrapatrikaclient.netlify.app was recorded returning HTTP status 404 on 2026-10-01, indicating that the requested resource was not found at that time. The domain was also first observed on 2026-09-17, with a PageSpeed performance score of 100 recorded on the same date.
Recorded Evidence
On 2026-10-01, zimbrapatrikaclient.netlify.app returned an HTTP 404 response. VirusTotal checked the domain on 2026-09-19, recording 13 detections out of 89 scanners. The domain was first observed on 2026-09-17, and a PhishDestroy internal listing is recorded as true. The SSL certificate was issued by DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1 and scanned on 2026-09-17.
Interpretation
The HTTP 404 status recorded on 2026-10-01 reflects only the response to a specific request made on that date. VirusTotal's detection count and the PhishDestroy internal listing are separate observations, each providing distinct information about the domain. The sequence of dated records allows comparison between different types of checks but does not indicate a direct relationship or trend between them.
Recommended Actions
For zimbrapatrikaclient.netlify.app, retain the HTTP status record and VirusTotal detection results for future reference. Review the PhishDestroy internal listing and compare it separately with the VirusTotal findings. Preserve the SSL certificate and PageSpeed performance records to inform any subsequent assessments or checks.
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.
IP ContextNetlify shared edgeorigin IP hiddenEdge-IP reputation is not attributed to this domain.
Platform providerNetlify(US)
HTTP Status404 Not Found
Time to First Unavailability9 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Certificate fingerprintbc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478Certificate names · 1 SANs
netlify.app
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeInactivereason: Http No Content70% confidence
Attributionsource: Current Http Probe
Evidence layersAvailability: Root path has no contentContent: Absent At RootDNS: StaleRegistration: Unknown
Latest HTTP observationInactiveHttp No Content70%2026-10-11 01:31:52 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-25 10:04:48 UTCcurrent episode first observed: 2026-10-01 01:56:07 UTCobserved RIP window: 2026-09-25 10:04:48 UTC → 2026-10-01 01:56:07 UTC · 135.86hmidpoint estimate ≈ 2026-09-28 06:00:27 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.
Technologies · 2 identified
N
Netlify
PaaSCDN
Netlify providers hosting and server-less backend services for web applications and static websites.
Google PageSpeed Insights — mobile performance audit of zimbrapatrikaclient.netlify.app· checked Sep 17, 2026
100
Good
Performance
FCP
0.77s
First Contentful Paint
LCP
0.77s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.77s
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-25 22:04:24 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-09-17 09:41:02 UTC
VirusTotal scanner detections updated from 12 to 13. Added scanner alerts: alphaMountain.ai.
Threat First Observed2026-09-17 03:17:34 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 63.176.8.218.
Threat Response Pipeline
Discovery
Analysis
Monitoring
14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
zimbrapatrikaclient.netlify.app 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 latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 26, 2026
Time to First Unavailability
210 hours elapsed from detection to the first unavailable 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.
4 evidence signal groups linked0 reports recordedContent unavailable
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 →
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 matches8
Same favicon hash or the same page title as this host.
(US)
