1337xto.to

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

Online · 200Family DNS blockedSSL: 59 days left8 years oldTranco #751919

One re-check per domain each UTC day.

50

1337xto.to was registered on 26 Jun 2018 via Tonic and the registry expiry is 26 Jun 2027. WHOIS data came from RDAP at https://rdap.tonicregistry.to/rdap/domain/1337xto.to.

1337xto.to publishes 2 nameservers. DNSSEC is not signed.

1337xto.to has 2 IPv4 addresses (104.21.53.30, 172.67.208.78) and 2 IPv6 addresses (2606:4700:3031::6815:351e, 2606:4700:3037::ac43:d04e). The geolocation database places 104.21.53.30 in Toronto, Canada.

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

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

Domain · RDAP/WHOIS

1337xto.to was registered on 26 Jun 2018 via Tonic. The registry returned 1 status value and 2 nameservers from https://rdap.tonicregistry.to/rdap/domain/1337xto.to.

Registeredsince 26 Jun 2018
Created26 June 2018
Updated30 May 2026
Expires26 June 2027
RegistrarTonic
Statusactive
Nameserversshane.ns.cloudflare.com, zariyah.ns.cloudflare.com
DNSSECno
Sourcehttps://rdap.tonicregistry.to/rdap/domain/1337xto.to

Nameserver shane.ns.cloudflare.com is published for 1337xto.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/1337xto.to.

Nameserver zariyah.ns.cloudflare.com is published for 1337xto.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/1337xto.to.

DNS

1337xto.to has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A104.21.53.30, 172.67.208.78
AAAA2606:4700:3031::6815:351e, 2606:4700:3037::ac43:d04e
NSshane.ns.cloudflare.com, zariyah.ns.cloudflare.com
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 104.21.53.30 answers for 1337xto.to at resolver 1.1.1.1:53.

IPv4 address 172.67.208.78 answers for 1337xto.to at resolver 1.1.1.1:53.

IPv6 address 2606:4700:3031::6815:351e answers for 1337xto.to at resolver 1.1.1.1:53.

IPv6 address 2606:4700:3037::ac43:d04e answers for 1337xto.to at resolver 1.1.1.1:53.

Hosting and geo

1337xto.to is placed in Toronto, Canada by the local geolocation database (db-ip).

Address104.21.53.30
CountryCanada
CityToronto
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for 1337xto.to is valid, with 59 days left and 2 subject alternative names. Source: tls:443.

IssuerWE1
Subject1337xto.to
Valid from30 September 2026
Valid until29 December 2026
Days left59
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: *.1337xto.to, 1337xto.to.

Tech stack

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

  • Cloudflare · CDN
  • HTTP/3 · Miscellaneous
  • jQuery · JavaScript libraries

Cloudflare is filed under CDN.

HTTP/3 is filed under Miscellaneous.

jQuery is filed under JavaScript libraries.

On-page checks

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

Status200
TTFB372 ms
Title length38 yes
Quoted title"1337x | 1337x.to Torrent Search Engine"
Meta description"1337x.to: Download music, movies, games, software and much more. 1337x.to is the galaxy's most resilient BitTorrent site." yes
H1 count1
HSTSno no
CSPno
X-Frame-Options—
Robots meta—
Canonical—
Language—
Links29
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 1337xto.to 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 1337xto.to. 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

First checked on 30 October 2026; changes will appear here.

Questions

Is 1337xto.to safe?

Cloudflare family DNS returned a block for 1337xto.to. That resolver covers adult and malware names.

Who hosts 1337xto.to?

1337xto.to is placed in Toronto, Canada.

When does 1337xto.to expire?

1337xto.to expires on 26 June 2027 according to https://rdap.tonicregistry.to/rdap/domain/1337xto.to.

Who owns 1337xto.to?

The registry did not return a person or a company for 1337xto.to. RDAP often redacts the registrant. The registrar on file is Tonic.

Sources

  • RDAP source https://rdap.tonicregistry.to/rdap/domain/1337xto.to at 2026-10-30T15:15:06Z
  • DNS source 1.1.1.1:53 at 2026-10-30T15:15:06Z
  • TLS source tls:443 at 2026-10-30T15:15:06Z
  • HTTP source https://1337xto.to/ at 2026-10-30T15:15:06Z
  • Tech source wappalyzergo at 2026-10-30T15:15:06Z
  • Geo source db-ip at 2026-10-30T15:15:06Z
  • Safety source family DNS and local lists at 2026-10-30T15:15:06Z

Methodology

Related reports

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

.to Tonic

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.