torrentz2.xyz

Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .

Online · 200Family DNS blockedSSL: 62 days left6 years old

One re-check per domain each UTC day.

50

torrentz2.xyz was registered on 9 Apr 2020 via NameCheap, Inc. and the registry expiry is 9 Apr 2027. WHOIS data came from RDAP at https://rdap.centralnic.com/xyz/domain/torrentz2.xyz.

torrentz2.xyz publishes 2 nameservers. DNSSEC is not signed.

torrentz2.xyz has 2 IPv4 addresses (188.114.96.4, 188.114.97.4) and 2 IPv6 addresses (2a06:98c1:3120::3, 2a06:98c1:3121::3). The geolocation database places 188.114.96.4 in Toronto, Canada.

The TLS certificate from WE1 is valid and has 62 days left (TLS 1.3). The homepage answered HTTP 200.

Tech detection named Cloudflare and HTTP/3. The fingerprints ran on the homepage that was already downloaded.

Domain · RDAP/WHOIS

torrentz2.xyz was registered on 9 Apr 2020 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.centralnic.com/xyz/domain/torrentz2.xyz.

Registeredsince 9 Apr 2020
Created9 April 2020
Updated1 April 2026
Expires9 April 2027
RegistrarNameCheap, Inc.
Statusclient transfer prohibited
Nameserverskurt.ns.cloudflare.com, nelci.ns.cloudflare.com
DNSSECno
Sourcehttps://rdap.centralnic.com/xyz/domain/torrentz2.xyz

torrentz2.xyz carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.

Nameserver kurt.ns.cloudflare.com is published for torrentz2.xyz in the registration record from https://rdap.centralnic.com/xyz/domain/torrentz2.xyz.

Nameserver nelci.ns.cloudflare.com is published for torrentz2.xyz in the registration record from https://rdap.centralnic.com/xyz/domain/torrentz2.xyz.

DNS

torrentz2.xyz has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A188.114.96.4, 188.114.97.4
AAAA2a06:98c1:3120::3, 2a06:98c1:3121::3
NSkurt.ns.cloudflare.com, nelci.ns.cloudflare.com
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 188.114.96.4 answers for torrentz2.xyz at resolver 1.1.1.1:53.

IPv4 address 188.114.97.4 answers for torrentz2.xyz at resolver 1.1.1.1:53.

IPv6 address 2a06:98c1:3120::3 answers for torrentz2.xyz at resolver 1.1.1.1:53.

IPv6 address 2a06:98c1:3121::3 answers for torrentz2.xyz at resolver 1.1.1.1:53.

Hosting and geo

torrentz2.xyz is placed in Toronto, Canada by the local geolocation database (db-ip).

Address188.114.96.4
CountryCanada
CityToronto
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for torrentz2.xyz is valid, with 62 days left and 2 subject alternative names. Source: tls:443.

IssuerWE1
Subjecttorrentz2.xyz
Valid from4 October 2026
Valid until2 January 2027
Days left62
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: *.torrentz2.xyz, torrentz2.xyz.

Tech stack

Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.

  • Cloudflare · CDN
  • HTTP/3 · Miscellaneous

Cloudflare is filed under CDN.

HTTP/3 is filed under Miscellaneous.

On-page checks

The homepage returned HTTP 200 in 29 ms. The target title is 61 characters and the page has 1 H1 heading.

Status200
TTFB29 ms
Title length61 no
Quoted title"Torrentz2 Search Engine - Fast and Reliable Torrent Downloads"
Meta descriptionnone no
H1 count1
HSTSno no
CSPno
X-Frame-Options—
Robots meta—
Canonicalhttps://www.torrentz2.xyz/
Languageen
Links7
Images1
Faviconyes

The quoted title and meta description are measurements of the other site. They are not this page's title or description.

Security

Family DNS for torrentz2.xyz is blocked, and URLhaus is clear. Source: family DNS and local lists.

Family DNSblocked
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSno
CSPno

Cloudflare family DNS returned a block for torrentz2.xyz. That resolver covers adult and malware names.

Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.

Score breakdown

Availability 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.

TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.

DNS hygiene 0 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.

Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.

Safety lists 0 of 15. Points only when the checks ran and came back clean. Unknown is not clean.

Domain age 5 of 5. Five points at one year, two points at 30 days.

Change history

  • October 2026: dns a changed from 188.114.96.3,188.114.97.3 to 188.114.96.4,188.114.97.4.

Questions

Is torrentz2.xyz safe?

Cloudflare family DNS returned a block for torrentz2.xyz. That resolver covers adult and malware names.

Who hosts torrentz2.xyz?

torrentz2.xyz is placed in Toronto, Canada.

When does torrentz2.xyz expire?

torrentz2.xyz expires on 9 April 2027 according to https://rdap.centralnic.com/xyz/domain/torrentz2.xyz.

Who owns torrentz2.xyz?

The registry did not return a person or a company for torrentz2.xyz. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..

Sources

  • RDAP source https://rdap.centralnic.com/xyz/domain/torrentz2.xyz at 2026-10-30T15:48:54Z
  • DNS source 1.1.1.1:53 at 2026-10-30T15:48:54Z
  • TLS source tls:443 at 2026-10-30T15:48:54Z
  • HTTP source https://torrentz2.xyz/ at 2026-10-30T15:48:54Z
  • Tech source wappalyzergo at 2026-10-30T15:48:54Z
  • Geo source db-ip at 2026-10-30T15:48:54Z
  • Safety source family DNS and local lists at 2026-10-30T15:48:54Z

Methodology

Related reports

No other indexable reports share this TLD, host, or registrar yet.

.xyz NameCheap, Inc.

Owner of this site?

Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.

Removal policy

How to read this report

The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.