The scan of n.to on 16 Aug 2026 reached no verdict either way (score -12). Too little was captured to judge it, which is an unknown rather than a pass.

What malware is associated with n.to?

7 analysed samples communicate with this URL.

How was n.to checked?

A static pass resolved DNS, captured TLS and headers and followed the redirect chain, and where the fast tier allows, a headless browser rendered the page and recorded every request. Egress is SSRF-locked. Signatures that matched only page text are weighted far below one that matched a served file, because a page documenting malware matches the same rules.

n.to - URL scan, 16 Aug 2026

MalwareAnalyzer by Cyble scanned n.to and returned a unknown verdict (score -12). The page resolved to 172.67.200.5 on Cloudflare, Inc. in US. The domain was registered 60 days ago through NAMECHEAP. 3 domains and 1 IP were contacted, over 2 HTTP requests. 7 malware samples communicate with this URL. This is a point-in-time observation from 16 Aug 2026; the page may have changed since.

Scan result

Verdict: unknown (score -12) · Confidence 15%
Scanned URL: https://n.to/
Domain: n.to · IP: 172.67.200.5 · AS13335 · US
Server: cloudflare
HTTP status: 200 · text/html
Registrar: NAMECHEAP · domain age 60 days · created 2026-06-16
TLS issuer: C=US, O=Google Trust Services, CN=WE1 · valid to Sep 17 00: · subject CN=n.to
HTTP requests captured: 2
Scan tier: fast · observed 2026-08-16 07:30:34 UTC

Malware communicating with this URL (7)

These samples were observed contacting or being served from n.to. Each links to its full analysis.

fb17303d9ff2f65626155051a193940b0fd1c717d1ba8a9074a0b2d94f1eea6a - referenced · fb17303d9ff2f65626155051a193940b · first seen 2026-08-16
f3a91608f3336e83a2227b52afff45f9ec390a3145032052a4cbbb5ca1a3de3c - referenced · f3a91608f3336e83a2227b52afff45f9 · first seen 2026-08-15
codeMirror.plugin.min.js - referenced · c87f083330dda171b3a1c1b912c21859 · first seen 2026-08-12
codeMirror.bundle.min.js - referenced · 7b5277fff495c8fc86f70c16bec5efaa · first seen 2026-08-12
636f8b858f681acb7bfa6f583a96630a.js - referenced · e6edf834c5900d2354164a41917cd276 · first seen 2026-08-12
bootstrap.min.js - referenced · a4555d8dee9f8adc976e84a97dfe87e6 · first seen 2026-08-11
4edd6e0bd9a145346a9777c16a62a2e20e0dbbf07e4e8db43417a62ee96ab0b7 - referenced · 4edd6e0bd9a145346a9777c16a62a2e2 · first seen 2026-08-11

Antivirus & YARA (0 of 47 engines)

No engine flagged this page's content.

Why this verdict

Valid TLS, no impersonation or off-origin credential post

Detected technologies

Cloudflare
Cloudflare Insights

Contacted infrastructure

172.67.200.5 - AS13335 Cloudflare, Inc. (United States)

Observed indicators

n.to
8.la
static.cloudflareinsights.com
172.67.200.5
https://n.to/
http://8.la/
https://n.to/cdn-cgi/l/email-protection#96aed6aeb8faf7
https://n.to/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
https://static.cloudflareinsights.com/beacon.min.js/v4513226cdae34746b4dedf0b4dfa099e1781791509496

Other scans of n.to (3)

This host has been scanned before. Each scan is a separate observation, so a verdict here does not carry over to the others.

20 Aug 2026 - unknown
12 Aug 2026 - unknown
11 Aug 2026 - unknown

Questions about n.to

Is n.to safe?: The scan of n.to on 16 Aug 2026 reached no verdict either way (score -12). Too little was captured to judge it, which is an unknown rather than a pass.
What malware is associated with n.to?: 7 analysed samples communicate with this URL.
How was n.to checked?: A static pass resolved DNS, captured TLS and headers and followed the redirect chain, and where the fast tier allows, a headless browser rendered the page and recorded every request. Egress is SSRF-locked. Signatures that matched only page text are weighted far below one that matched a served file, because a page documenting malware matches the same rules.

Scanned at the fast tier - see how URL scanning works.

Scan another URL · Latest analyzed threats · All scans of n.to

Scanned on MalwareAnalyzer by Cyble · Open interactive scan