bitsearch.to
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200Family DNS blockedSSL: 77 days left5 years oldTranco #32645
50
bitsearch.to was registered on 21 Mar 2021 via Tonic and the registry expiry is 21 Mar 2028. WHOIS data came from RDAP at https://rdap.tonicregistry.to/rdap/domain/bitsearch.to.
bitsearch.to publishes 2 nameservers. DNSSEC is not signed.
bitsearch.to 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 77 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Express, HTTP/3 and Node.js. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
bitsearch.to was registered on 21 Mar 2021 via Tonic. The registry returned 1 status value and 2 nameservers from https://rdap.tonicregistry.to/rdap/domain/bitsearch.to.
| Registered | since 21 Mar 2021 |
|---|---|
| Created | 21 March 2021 |
| Updated | 5 April 2026 |
| Expires | 21 March 2028 |
| Registrar | Tonic |
| Status | active |
| Nameservers | emely.ns.cloudflare.com, fred.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.tonicregistry.to/rdap/domain/bitsearch.to |
Nameserver emely.ns.cloudflare.com is published for bitsearch.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/bitsearch.to.
Nameserver fred.ns.cloudflare.com is published for bitsearch.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/bitsearch.to.
DNS
bitsearch.to has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.4, 188.114.97.4 |
|---|---|
| AAAA | 2a06:98c1:3120::3, 2a06:98c1:3121::3 |
| NS | emely.ns.cloudflare.com, fred.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 188.114.96.4 answers for bitsearch.to at resolver 1.1.1.1:53.
IPv4 address 188.114.97.4 answers for bitsearch.to at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::3 answers for bitsearch.to at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::3 answers for bitsearch.to at resolver 1.1.1.1:53.
Hosting and geo
bitsearch.to is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.4 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for bitsearch.to is valid, with 77 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | bitsearch.to |
| Valid from | 18 October 2026 |
| Valid until | 16 January 2027 |
| Days left | 77 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.bitsearch.to, bitsearch.to.
Tech stack
Tech detection checked the fetched homepage and named 4 products. Source: wappalyzergo.
- Cloudflare · CDN
- Express · Web frameworks, Web servers
- HTTP/3 · Miscellaneous
- Node.js · Programming languages
Cloudflare is filed under CDN.
Express is filed under Web frameworks, Web servers.
HTTP/3 is filed under Miscellaneous.
Node.js is filed under Programming languages.
On-page checks
The homepage returned HTTP 200 in 248 ms. The target title is 16 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 248 ms |
| Title length | 16 yes |
| Quoted title | "Home | Bitsearch" |
| Meta description | "Bitsearch is #1 Torrent Index ever." yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | https://bitsearch.to/ |
| Language | en |
| Links | 34 |
| Images | 2 |
| Favicon | yes |
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 bitsearch.to is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for bitsearch.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
- 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 bitsearch.to safe?
Cloudflare family DNS returned a block for bitsearch.to. That resolver covers adult and malware names.
Who hosts bitsearch.to?
bitsearch.to is placed in Toronto, Canada.
When does bitsearch.to expire?
bitsearch.to expires on 21 March 2028 according to https://rdap.tonicregistry.to/rdap/domain/bitsearch.to.
Who owns bitsearch.to?
The registry did not return a person or a company for bitsearch.to. RDAP often redacts the registrant. The registrar on file is Tonic.
Sources
- RDAP source https://rdap.tonicregistry.to/rdap/domain/bitsearch.to at 2026-10-30T15:15:28Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:15:28Z
- TLS source tls:443 at 2026-10-30T15:15:28Z
- HTTP source https://bitsearch.to/ at 2026-10-30T15:15:28Z
- Tech source wappalyzergo at 2026-10-30T15:15:28Z
- Geo source db-ip at 2026-10-30T15:15:28Z
- Safety source family DNS and local lists at 2026-10-30T15:15:28Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
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.
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.