torrage.info
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
65
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
65
torrage.info was registered on 16 Apr 2015 via Gransy, s.r.o. and the registry expiry is 16 Apr 2027. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/torrage.info.
torrage.info publishes 2 nameservers. DNSSEC is not signed.
torrage.info has 2 IPv4 addresses (104.21.233.133, 104.21.233.134) and 2 IPv6 addresses (2606:4700:3038::6815:e985, 2606:4700:3038::6815:e986). The geolocation database places 104.21.233.133 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 55 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Bootstrap, Cloudflare, HTTP/3 and jQuery. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for torrage.info in the checks that ran.
torrage.info was registered on 16 Apr 2015 via Gransy, s.r.o.. The registry returned 1 status value and 2 nameservers from https://rdap.identitydigital.services/rdap/domain/torrage.info.
| Registered | since 16 Apr 2015 |
|---|---|
| Created | 16 April 2015 |
| Updated | 12 August 2026 |
| Expires | 16 April 2027 |
| Registrar | Gransy, s.r.o. |
| Status | client transfer prohibited |
| Nameservers | zeus.ns.cloudflare.com, heather.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.identitydigital.services/rdap/domain/torrage.info |
torrage.info 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 zeus.ns.cloudflare.com is published for torrage.info in the registration record from https://rdap.identitydigital.services/rdap/domain/torrage.info.
Nameserver heather.ns.cloudflare.com is published for torrage.info in the registration record from https://rdap.identitydigital.services/rdap/domain/torrage.info.
torrage.info has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.233.133, 104.21.233.134 |
|---|---|
| AAAA | 2606:4700:3038::6815:e985, 2606:4700:3038::6815:e986 |
| NS | heather.ns.cloudflare.com, zeus.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.233.133 answers for torrage.info at resolver 1.1.1.1:53.
IPv4 address 104.21.233.134 answers for torrage.info at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3038::6815:e985 answers for torrage.info at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3038::6815:e986 answers for torrage.info at resolver 1.1.1.1:53.
torrage.info is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.233.133 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for torrage.info is valid, with 55 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | torrage.info |
| Valid from | 26 September 2026 |
| Valid until | 26 December 2026 |
| Days left | 55 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.torrage.info, torrage.info.
Tech detection checked the fetched homepage and named 4 products. Source: wappalyzergo.
Bootstrap is filed under UI frameworks.
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
jQuery is filed under JavaScript libraries.
The homepage returned HTTP 200 in 265 ms. The target title is 35 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 265 ms |
| Title length | 35 yes |
| Quoted title | "Torrage- Free Torrent Storage Cache" |
| Meta description | "ADD SITE DESCRIPTION" yes |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | index, follow |
| Canonical | — |
| Language | en |
| Links | 5 |
| Images | 0 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for torrage.info is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
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 15 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.
First checked on 30 October 2026; changes will appear here.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
torrage.info is placed in Toronto, Canada.
torrage.info expires on 16 April 2027 according to https://rdap.identitydigital.services/rdap/domain/torrage.info.
The registry did not return a person or a company for torrage.info. RDAP often redacts the registrant. The registrar on file is Gransy, s.r.o..
No other indexable reports share this TLD, host, or registrar yet.
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.
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.