fairfan.co
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 34 days left4 years old
85
fairfan.co was registered on 6 Jun 2022 via Name.com, Inc. and the registry expiry is 6 Jun 2027. WHOIS data came from RDAP at https://rdap.registry.co/co/domain/fairfan.co.
fairfan.co publishes 2 nameservers. DNSSEC is not signed.
fairfan.co has 2 IPv4 addresses (104.21.51.238, 172.67.191.181) and 2 IPv6 addresses (2606:4700:3034::ac43:bfb5, 2606:4700:3035::6815:33ee). The geolocation database places 104.21.51.238 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 34 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for fairfan.co in the checks that ran.
Domain · RDAP/WHOIS
fairfan.co was registered on 6 Jun 2022 via Name.com, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.registry.co/co/domain/fairfan.co.
| Registered | since 6 Jun 2022 |
|---|---|
| Created | 6 June 2022 |
| Updated | 15 May 2026 |
| Expires | 6 June 2027 |
| Registrar | Name.com, Inc. |
| Status | client transfer prohibited |
| Nameservers | destiny.ns.cloudflare.com, konnor.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.registry.co/co/domain/fairfan.co |
fairfan.co 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 destiny.ns.cloudflare.com is published for fairfan.co in the registration record from https://rdap.registry.co/co/domain/fairfan.co.
Nameserver konnor.ns.cloudflare.com is published for fairfan.co in the registration record from https://rdap.registry.co/co/domain/fairfan.co.
DNS
fairfan.co has 4 address records, 5 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.51.238, 172.67.191.181 |
|---|---|
| AAAA | 2606:4700:3034::ac43:bfb5, 2606:4700:3035::6815:33ee |
| NS | destiny.ns.cloudflare.com, konnor.ns.cloudflare.com |
| MX | aspmx.l.google.com (1) Google, alt1.aspmx.l.google.com (5) Google, alt2.aspmx.l.google.com (5) Google, alt3.aspmx.l.google.com (10) Google, alt4.aspmx.l.google.com (10) Google |
| SPF | present |
| DMARC | present |
| CAA | issue comodoca.com, issue digicert.com; cansignhttpexchanges=yes, issue letsencrypt.org, issue pki.goog; cansignhttpexchanges=yes, issue ssl.com, issuewild comodoca.com, issuewild digicert.com; cansignhttpexchanges=yes, issuewild letsencrypt.org, issuewild pki.goog; cansignhttpexchanges=yes, issuewild ssl.com |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at fairfan.co is "v=spf1 include:_spf.google.com -all".
The DMARC text record at _dmarc.fairfan.co is "v=DMARC1; p=none; sp=none; rua=mailto:re+[email protected]; pct=100".
IPv4 address 104.21.51.238 answers for fairfan.co at resolver 1.1.1.1:53.
IPv4 address 172.67.191.181 answers for fairfan.co at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3034::ac43:bfb5 answers for fairfan.co at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3035::6815:33ee answers for fairfan.co at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 1. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt3.aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger alt4.aspmx.l.google.com has preference 10. The host is recognised as Google.
Hosting and geo
fairfan.co is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.51.238 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for fairfan.co is valid, with 34 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | fairfan.co |
| Valid from | 5 September 2026 |
| Valid until | 4 December 2026 |
| Days left | 34 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.fairfan.co, fairfan.co.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- Cloudflare · CDN
- HTTP/3 · Miscellaneous
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 200 in 238 ms. The target title is 55 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 238 ms |
| Title length | 55 yes |
| Quoted title | "StreamFind - Streaming Made Easy | Movies, TV, & Sports" |
| Meta description | "The new unlimited guide to streaming, Watch, discuss, and review an immense collection of entertainment with any device." yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | index, follow |
| Canonical | https://streamfind.com/ |
| Language | en |
| Links | 143 |
| Images | 268 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for fairfan.co 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 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 15 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 5 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
- October 2026: rdap created changed from empty to 2022-06-06T03:27:19.0Z.
- October 2026: rdap dnssec changed from unknown to no.
- October 2026: rdap expires changed from empty to 2027-06-06T23:59:59.0Z.
- October 2026: rdap nameservers changed from empty to destiny.ns.cloudflare.com,konnor.ns.cloudflare.com.
- October 2026: rdap registered changed from unknown to yes.
- October 2026: rdap registrar changed from empty to Name.com, Inc..
- October 2026: rdap statuses changed from empty to client transfer prohibited.
- October 2026: rdap updated changed from empty to 2026-05-15T16:47:02.0Z.
Questions
Is fairfan.co 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 fairfan.co?
fairfan.co is placed in Toronto, Canada.
When does fairfan.co expire?
fairfan.co expires on 6 June 2027 according to https://rdap.registry.co/co/domain/fairfan.co.
Who owns fairfan.co?
The registry did not return a person or a company for fairfan.co. RDAP often redacts the registrant. The registrar on file is Name.com, Inc..
Sources
- RDAP source https://rdap.registry.co/co/domain/fairfan.co at 2026-10-30T13:38:46Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:38:46Z
- TLS source tls:443 at 2026-10-30T13:38:46Z
- HTTP source https://fairfan.co/ at 2026-10-30T13:38:46Z
- Tech source wappalyzergo at 2026-10-30T13:38:46Z
- Geo source db-ip at 2026-10-30T13:38:46Z
- Safety source family DNS and local lists at 2026-10-30T13:38:46Z
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.