lufix.to
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafe2 years old
20
lufix.to was registered on 24 Mar 2024 via Tonic and the registry expiry is 24 Mar 2028. WHOIS data came from RDAP at https://rdap.tonicregistry.to/rdap/domain/lufix.to.
No safety warning was recorded for lufix.to in the checks that ran.
Domain · RDAP/WHOIS
lufix.to was registered on 24 Mar 2024 via Tonic. The registry returned 1 status value and 2 nameservers from https://rdap.tonicregistry.to/rdap/domain/lufix.to.
| Registered | since 24 Mar 2024 |
|---|---|
| Created | 24 March 2024 |
| Updated | 3 March 2026 |
| Expires | 24 March 2028 |
| Registrar | Tonic |
| Status | client hold |
| Nameservers | jo.ns.cloudflare.com, syeef.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.tonicregistry.to/rdap/domain/lufix.to |
lufix.to carries the status "client hold". The registrar has put the name on hold. Resolvers may stop answering it while the hold lasts.
Nameserver jo.ns.cloudflare.com is published for lufix.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/lufix.to.
Nameserver syeef.ns.cloudflare.com is published for lufix.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/lufix.to.
DNS
lufix.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 lufix.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 lufix.to on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp: lookup lufix.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://lufix.to/": dial tcp: lookup lufix.to on 46.38.252.230:53: no such host
Security
Family DNS for lufix.to 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.
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 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.
Change history
First checked on 30 October 2026; changes will appear here.
Questions
Is lufix.to safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts lufix.to?
The host network is not available without a local geolocation database.
When does lufix.to expire?
lufix.to expires on 24 March 2028 according to https://rdap.tonicregistry.to/rdap/domain/lufix.to.
Who owns lufix.to?
The registry did not return a person or a company for lufix.to. RDAP often redacts the registrant. The registrar on file is Tonic.
Sources
- RDAP source https://rdap.tonicregistry.to/rdap/domain/lufix.to at 2026-10-30T15:16:14Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:16:14Z
- TLS source tls:443 at 2026-10-30T15:16:14Z
- HTTP source https://lufix.to/ at 2026-10-30T15:16:14Z
- Tech source not available at 2026-10-30T15:16:14Z
- Geo source db-ip at 2026-10-30T15:16:14Z
- Safety source family DNS and local lists at 2026-10-30T15:16:14Z
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.