1flix.to
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blocked3 years old
5
1flix.to was registered on 26 Aug 2023 via Tonic and the registry expiry is 26 Aug 2026. WHOIS data came from RDAP at https://rdap.tonicregistry.to/rdap/domain/1flix.to.
Domain · RDAP/WHOIS
1flix.to was registered on 26 Aug 2023 via Tonic. The registry returned 6 status values and 2 nameservers from https://rdap.tonicregistry.to/rdap/domain/1flix.to.
| Registered | since 26 Aug 2023 |
|---|---|
| Created | 26 August 2023 |
| Updated | 5 October 2026 |
| Expires | 26 August 2026 |
| Registrar | Tonic |
| Status | server transfer prohibited, client hold, pending delete, server update prohibited, server hold, redemption period |
| Nameservers | jaime.ns.cloudflare.com, love.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.tonicregistry.to/rdap/domain/1flix.to |
1flix.to carries the status "server transfer prohibited". The registry itself is refusing transfers. The name stays at the current registrar while the status remains.
1flix.to carries the status "client hold". The registrar has put the name on hold. Resolvers may stop answering it while the hold lasts.
1flix.to carries the status "pending delete". The name is queued for deletion at the registry. It is not a normal registered name in active use.
1flix.to carries the status "server update prohibited". The registry itself is refusing updates to the domain object.
1flix.to carries the status "server hold". The registry has put the name on hold. Resolvers may stop answering it while the hold lasts.
1flix.to carries the status "redemption period". The name was deleted and is in the redemption window, where a restore may still be possible at the registry.
Nameserver jaime.ns.cloudflare.com is published for 1flix.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/1flix.to.
Nameserver love.ns.cloudflare.com is published for 1flix.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/1flix.to.
DNS
1flix.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 |
Hosting and geo
Geolocation for 1flix.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 |
SSL/TLS
No TLS certificate was read for 1flix.to on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp: lookup 1flix.to on 46.38.252.230:53: no such host
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://1flix.to/": dial tcp: lookup 1flix.to on 46.38.252.230:53: no such host
Security
Family DNS for 1flix.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 1flix.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 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 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 1flix.to safe?
Cloudflare family DNS returned a block for 1flix.to. That resolver covers adult and malware names.
Who hosts 1flix.to?
The host network is not available without a local geolocation database.
When does 1flix.to expire?
1flix.to expires on 26 August 2026 according to https://rdap.tonicregistry.to/rdap/domain/1flix.to.
Who owns 1flix.to?
The registry did not return a person or a company for 1flix.to. RDAP often redacts the registrant. The registrar on file is Tonic.
Sources
- RDAP source https://rdap.tonicregistry.to/rdap/domain/1flix.to at 2026-10-30T15:15:07Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:15:07Z
- TLS source tls:443 at 2026-10-30T15:15:07Z
- HTTP source https://1flix.to/ at 2026-10-30T15:15:07Z
- Tech source not available at 2026-10-30T15:15:07Z
- Geo source db-ip at 2026-10-30T15:15:07Z
- Safety source family DNS and local lists at 2026-10-30T15:15:07Z
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.