VirusTotal
17 / 91
zip-core.com returned HTTP status 200 on 2026-10-01 according to the recorded HTTP check. The same evidence set records a PhishDestroy internal listing for this domain, and a registration date of 2025-10-28 with Dynadot Inc as registrar.
The HTTP check on 2026-10-01 recorded status 200, while the PhishDestroy internal listing was also present in the same evidence set. VirusTotal recorded 17 detections across 91 scanners on 2026-09-30, and OTX recorded 4 pulses on 2026-09-22. The domain was first observed on 2026-09-20, the same date as a PageSpeed performance score of 98.
The VirusTotal and OTX observations fall on different dates, so their counts describe separate snapshots rather than one combined measurement. The PhishDestroy listing and the 2026-10-01 HTTP check are likewise recorded at different points, which limits direct comparison between them. The SSL scan on 2026-09-21 names Google Trust Services / WE1 as issuer.
Reviewers should retain the dated records for zip-core.com so later observations can be compared against the 2026-09-30 VirusTotal result and the 2026-09-22 OTX count. Subsequent checks of zip-core.com should be logged with their own dates rather than merged with earlier entries. During review, avoid submitting sensitive information to zip-core.com until the recorded observations have been assessed.
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
Edge-IP reputation is not attributed to this domain.
lennon.ns.cloudflare.comLocation describes the IP network.
d04f142242b650ff82fd93da40ba7e0fae779e7b6b22ee38a5c5ec4a3d5e782dSaved 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 zip-core.com · checked Sep 20, 2026
104.21.73.57. 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