freek.to
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
2
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
2
freek.to was registered on 15 Dec 2025 via NAMECHEAP and the registry expiry is 15 Dec 2026. WHOIS data came from RDAP at https://rdap.tonicregistry.to/rdap/domain/freek.to.
freek.to was registered on 15 Dec 2025 via NAMECHEAP. The registry returned 2 status values and 2 nameservers from https://rdap.tonicregistry.to/rdap/domain/freek.to.
| Registered | since 15 Dec 2025 |
|---|---|
| Created | 15 December 2025 |
| Updated | 22 December 2025 |
| Expires | 15 December 2026 |
| Registrar | NAMECHEAP |
| Status | client transfer prohibited, client hold |
| Nameservers | lunlun.ns.giantpanda.com, yangyang.ns.giantpanda.com |
| DNSSEC | no |
| Source | https://rdap.tonicregistry.to/rdap/domain/freek.to |
freek.to 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.
freek.to carries the status "client hold". The registrar has put the name on hold. Resolvers may stop answering it while the hold lasts.
Nameserver lunlun.ns.giantpanda.com is published for freek.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/freek.to.
Nameserver yangyang.ns.giantpanda.com is published for freek.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/freek.to.
freek.to has 0 address records, 0 mail exchangers and 0 nameservers, measured at 1.1.1.1:53.
| A | — |
|---|---|
| AAAA | — |
| NS | — |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
Geolocation for freek.to is not available. No local city or ASN database is installed, so this report does not guess a country.
| Geolocation | not available |
|---|---|
| Source | maxmind |
No TLS certificate was read for freek.to on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp: lookup freek.to on 46.38.252.230:53: no such host
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://freek.to/": dial tcp: lookup freek.to on 46.38.252.230:53: no such host
Family DNS for freek.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 freek.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.
Availability 0 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 0 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 2 of 5. Five points at one year, two points at 30 days.
First checked on 30 October 2026; changes will appear here.
Cloudflare family DNS returned a block for freek.to. That resolver covers adult and malware names.
The host network is not available without a local geolocation database.
freek.to expires on 15 December 2026 according to https://rdap.tonicregistry.to/rdap/domain/freek.to.
The registry did not return a person or a company for freek.to. RDAP often redacts the registrant. The registrar on file is NAMECHEAP.
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.