dailyflix.info
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
60
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
60
dailyflix.info was registered on 27 Sep 2022 via NameCheap, Inc. and the registry expiry is 27 Sep 2027. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/dailyflix.info.
dailyflix.info publishes 2 nameservers. DNSSEC is not signed.
dailyflix.info has 2 IPv4 addresses (104.21.81.219, 172.67.165.59) and 2 IPv6 addresses (2606:4700:3031::ac43:a53b, 2606:4700:3032::6815:51db). The geolocation database places 104.21.81.219 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 Cloudflare and Stimulus. The fingerprints ran on the homepage that was already downloaded.
dailyflix.info was registered on 27 Sep 2022 via NameCheap, Inc.. The registry returned 2 status values and 2 nameservers from https://rdap.identitydigital.services/rdap/domain/dailyflix.info.
| Registered | since 27 Sep 2022 |
|---|---|
| Created | 27 September 2022 |
| Updated | 28 September 2026 |
| Expires | 27 September 2027 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited, auto renew period |
| Nameservers | zod.ns.cloudflare.com, meera.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.identitydigital.services/rdap/domain/dailyflix.info |
dailyflix.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 zod.ns.cloudflare.com is published for dailyflix.info in the registration record from https://rdap.identitydigital.services/rdap/domain/dailyflix.info.
Nameserver meera.ns.cloudflare.com is published for dailyflix.info in the registration record from https://rdap.identitydigital.services/rdap/domain/dailyflix.info.
dailyflix.info has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.81.219, 172.67.165.59 |
|---|---|
| AAAA | 2606:4700:3031::ac43:a53b, 2606:4700:3032::6815:51db |
| NS | meera.ns.cloudflare.com, zod.ns.cloudflare.com |
| MX | — |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at dailyflix.info is "v=spf1 -all".
The DMARC text record at _dmarc.dailyflix.info is "v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s;".
IPv4 address 104.21.81.219 answers for dailyflix.info at resolver 1.1.1.1:53.
IPv4 address 172.67.165.59 answers for dailyflix.info at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3031::ac43:a53b answers for dailyflix.info at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3032::6815:51db answers for dailyflix.info at resolver 1.1.1.1:53.
dailyflix.info is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.81.219 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for dailyflix.info is valid, with 55 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | dailyflix.info |
| Valid from | 26 September 2026 |
| Valid until | 25 December 2026 |
| Days left | 55 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.dailyflix.info, dailyflix.info.
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
Cloudflare is filed under CDN.
Stimulus is filed under JavaScript frameworks.
The homepage returned HTTP 200 in 61 ms. The target title is 24 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 61 ms |
| Title length | 24 yes |
| Quoted title | "Forums - DailyFliX Forum" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | https://board.dailyflix.info/index.php?app=forums&module=forums&controller=index |
| Language | en-US |
| Links | 285 |
| Images | 44 |
| 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 dailyflix.info 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 dailyflix.info. 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 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 10 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.
First checked on 30 October 2026; changes will appear here.
Cloudflare family DNS returned a block for dailyflix.info. That resolver covers adult and malware names.
dailyflix.info is placed in Toronto, Canada.
dailyflix.info expires on 27 September 2027 according to https://rdap.identitydigital.services/rdap/domain/dailyflix.info.
The registry did not return a person or a company for dailyflix.info. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
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.