VirusTotal
4 / 92
nalewin.com returned an HTTP 301 response on 2026-10-07, documenting a redirection at that time. The domain was first observed on 2026-10-07, establishing a baseline for its recorded activity.
On 2026-10-07, nalewin.com appeared in the PhishDestroy internal listing. VirusTotal recorded 2 detections out of 92 scanners on 2026-10-04. OTX reported 3 pulses for the domain as of 2026-10-07. The registrar was Fewmoretaps OU d/b/a Trustname.com and the SSL certificate was issued by Google Trust Services / WE1, both observed on 2026-10-07.
These dated records show that nalewin.com was monitored by several security sources, each providing a different type of observation. The HTTP 301 code reflects a specific server response, while VirusTotal and OTX document the domain’s presence in their respective security tracking systems. PhishDestroy’s internal listing adds further context to its monitoring history.
Continue to review nalewin.com using the HTTP, VirusTotal, OTX, and PhishDestroy records for ongoing assessment. Preserve each dated source record for reference and comparison in future reviews. Use these findings to guide any next steps or investigations related to the domain.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: redirect: raw=redirect_301; http=301; via=http_proxy; location=https://nalewin.com/; server=cloudflare
Edge-IP reputation is not attributed to this domain.
terry.ns.cloudflare.comLocation describes the IP network.
dcad38b6dcd81390010d4858f27151e4f446f0f768c4530ed1a8f80d37c2e284Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
188.114.96.1. 11 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