The domain zaywka-oon-oshad.lol returned an HTTP 502 status code on 2026-10-03, indicating a server error was observed at that time. Google Safe Browsing also recorded a social engineering flag for the domain on 2026-09-17.
Recorded Evidence
On 2026-09-17, Google Safe Browsing flagged zaywka-oon-oshad.lol for social engineering. VirusTotal, on the same date, recorded 4 detections out of 89 scanners for the domain. OTX included the domain in 4 pulses as of 2026-09-17. PhishDestroy listed the domain internally, and an HTTP check on 2026-10-03 resulted in a 502 status code.
Interpretation
The records from Google Safe Browsing, VirusTotal, and OTX show that zaywka-oon-oshad.lol was noted by multiple sources for different reasons. The HTTP 502 response documents a server error on a specific date, but does not describe any content. The internal listing by PhishDestroy indicates the domain was catalogued for monitoring purposes.
Recommended Actions
Preserve the Google Safe Browsing, VirusTotal, and OTX records for zaywka-oon-oshad.lol for future reference. Compare the HTTP 502 status with subsequent HTTP checks to observe any server changes. Use the PhishDestroy internal listing as a reference for catalogued domains.
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.
Stored cloaking flag
Not yet scanned
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='zaywka-oon-oshad.lol', port=80): Max retries exceeded with url: / (Caused by NewConnection
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Waiting
Domain details
Domain
Google Safe BrowsingFlaggedSocial engineeringchecked Sep 17, 2026
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.
Technical detailsProvenance & timestamps
First DetectedSep 7, 2026
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.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Nameservers 1
rommy.ns.cloudflare.com
Location describes the IP network.
Latest Classified Outcome 2026-10-13 20:21:07 UTC
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 01:15:51 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-07 17:28:10 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-07 17:28:10 UTC → 2026-09-30 16:14:55 UTC · 550.78hmidpoint estimate ≈ 2026-09-19 04:51:32 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: 4 detections
alphaMountain.ai
CRDF
Gridinsoft
SOCRadar
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.
VirusTotal Detections Update2026-09-17 13:03:24 UTC
VirusTotal scanner detections updated from 2 to 4. Added scanner alerts: CRDF, SOCRadar.
Domain Status Transition2026-09-15 22:00:18 UTC
Domain state transitioned from alive to dead.
Status Check2026-09-15 19:40:02 UTC
Telemetry event observed.
Threat First Observed2026-09-15 19:33:12 UTC
Domain ingestion complete. Initial state is marked as alive.
Threat Response Pipeline
Discovery
Analysis
Monitoring
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
zaywka-oon-oshad.lol detected and queued for full analysis
Sep 7, 2026
Cloudflare Radar Report
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 16, 2026
Time to First Unavailability
197 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.
2 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 →
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 · zaywka-oon-oshad.lol
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.
(US)
