VirusTotal
15 / 91
“Zamek Łeba – butikowy obiekt nad morzem | SPA, restauracja, widok na Bałtyk”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@dynadot.com.
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.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DigiCert UltraDNS | zamekleba.live |
malicious | Sinkholed |
| Quad9 DNS | zamekleba.live |
malicious | Sinkholed |
| OpenDNS | zamekleba.live |
phishing | Phishing Block |
| DNS4EU | zamekleba.live |
malicious | Sinkholed |
| Cloudflare DNS | zamekleba.live |
malicious | Sinkholed |
zamekleba.live returned HTTP status 200 on 2026-10-01, a dated response recorded during an HTTP check. A separate PhishDestroy internal listing for the domain is also recorded as true, and the domain appears in four OTX pulses dated 2026-09-22.
The domain zamekleba.live was first observed on 2026-09-20, the same date as its PageSpeed performance score of 66 and its SSL scan. VirusTotal recorded 15 detections across 91 scanners on 2026-09-30. OTX recorded 4 pulses on 2026-09-22, and the PhishDestroy internal listing was recorded as true. The domain was registered on 2026-07-09 with registrar Dynadot Inc, and its SSL certificate was issued by Google Trust Services / WE1. The HTTP check on 2026-10-01 returned status 200, while the IP address 188.114.96.3 is associated with Cloudflare, Inc. in CA.
The named sources describe different aspects of zamekleba.live: an HTTP response, a PageSpeed score, an SSL scan, VirusTotal detections, OTX pulses, and a PhishDestroy internal listing. These records were captured on different dates, so they should be compared as separate observations rather than combined into a single judgment. The chronology from first observation to the HTTP check spans several days, but the records do not establish what changed or why.
Preserve the PhishDestroy internal listing, the OTX pulse record, and the VirusTotal detection record for zamekleba.live so they can be reviewed together. Compare the HTTP response record with the PageSpeed and SSL scan records in separate reviews, since each captures a different measurement. Recheck the domain's recorded status periodically and retain each new dated observation alongside the existing source records.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
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.
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.
Edge-IP reputation is not attributed to this domain.
peter.ns.cloudflare.comrihana.ns.cloudflare.comLocation describes the IP network.
bff73672e1c567b74bf4195f48d8970ba65d7454928d578d88596938d9635f17Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of zamekleba.live · checked Sep 20, 2026
104.21.70.220. 12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
PD-20260920-EB80A7 Recipient: abuse@dynadot.com Registrar: Dynadot LLC / Dynadot Inc (United States) Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive