VirusTotal
checked — no detections recorded
“Nur einen Moment…”
cobaws1.com returned HTTP status 502 on 2026-10-01, a dated response recorded during an HTTP check. The same domain was first observed on 2026-09-02, according to the evidence set.
The HTTP check on 2026-10-01 recorded status 502, while the first observation of cobaws1.com dates to 2026-09-02. VirusTotal, checked on 2026-09-13, reported 0 detections across 89 scanners. OTX, checked on 2026-09-13, showed 3 pulses, and the PhishDestroy internal listing was true. The registrar was recorded as HOSTINGER operations, UAB, and the IP address 188.114.97.3 was associated with CloudFlare, Inc. in CA.
The OTX and VirusTotal checks share the 2026-09-13 date, so their results describe the same point in time, whereas the HTTP check on 2026-10-01 and the first observation on 2026-09-02 fall on different dates. Because these named sources were consulted at different times, a reader can compare the dates but cannot treat the records as simultaneous measurements. The PhishDestroy internal listing and the OTX pulses reflect catalogue entries, not a verdict about the domain.
Anyone reviewing cobaws1.com should retain the dated records from the HTTP check, OTX, VirusTotal and PhishDestroy for later comparison. Subsequent observations of cobaws1.com can be compared against the 2026-09-02 first observation and the 2026-10-01 HTTP status to see how the records change over time. During any review, avoid submitting sensitive information to the domain until the recorded status and listings are independently confirmed.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='cobaws1.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO
Edge-IP reputation is not attributed to this domain.
santino.ns.cloudflare.comLocation describes the IP network.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
10 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.
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