flocus.io
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 46 days left4 years old
80
flocus.io was registered on 30 Aug 2022 via Cloudflare, Inc and the registry expiry is 30 Aug 2027. WHOIS data came from RDAP at https://rdap.identitydigital.services/rdap/domain/flocus.io.
flocus.io publishes 2 nameservers. DNSSEC is not signed.
flocus.io has 2 IPv4 addresses (104.21.26.3, 172.67.168.52) and 2 IPv6 addresses (2606:4700:3033::ac43:a834, 2606:4700:3035::6815:1a03). The geolocation database places 104.21.26.3 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 46 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Cloudflare Browser Insights, Google Analytics and HSTS. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for flocus.io in the checks that ran.
Domain · RDAP/WHOIS
flocus.io was registered on 30 Aug 2022 via Cloudflare, Inc. The registry returned 1 status value and 2 nameservers from https://rdap.identitydigital.services/rdap/domain/flocus.io.
| Registered | since 30 Aug 2022 |
|---|---|
| Created | 30 August 2022 |
| Updated | 11 August 2026 |
| Expires | 30 August 2027 |
| Registrar | Cloudflare, Inc |
| Status | client transfer prohibited |
| Nameservers | aria.ns.cloudflare.com, major.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.identitydigital.services/rdap/domain/flocus.io |
flocus.io 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 aria.ns.cloudflare.com is published for flocus.io in the registration record from https://rdap.identitydigital.services/rdap/domain/flocus.io.
Nameserver major.ns.cloudflare.com is published for flocus.io in the registration record from https://rdap.identitydigital.services/rdap/domain/flocus.io.
DNS
flocus.io has 4 address records, 5 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.26.3, 172.67.168.52 |
|---|---|
| AAAA | 2606:4700:3033::ac43:a834, 2606:4700:3035::6815:1a03 |
| NS | aria.ns.cloudflare.com, major.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 | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at flocus.io is "v=spf1 include:_spf.google.com include:helpscoutemail.com ip4:158.69.0.21 -all".
The DMARC text record at _dmarc.flocus.io is "v=DMARC1; p=none; pct=100; rua=mailto:[email protected];".
IPv4 address 104.21.26.3 answers for flocus.io at resolver 1.1.1.1:53.
IPv4 address 172.67.168.52 answers for flocus.io at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3033::ac43:a834 answers for flocus.io at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3035::6815:1a03 answers for flocus.io 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
flocus.io is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.26.3 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for flocus.io is valid, with 46 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | flocus.io |
| Valid from | 17 September 2026 |
| Valid until | 16 December 2026 |
| Days left | 46 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.flocus.io, flocus.io.
Tech stack
Tech detection checked the fetched homepage and named 4 products. Source: wappalyzergo.
- Cloudflare · CDN
- Cloudflare Browser Insights · Analytics, RUM
- Google Analytics · Analytics
- HSTS · Security
Cloudflare is filed under CDN.
Cloudflare Browser Insights is filed under Analytics, RUM.
Google Analytics is filed under Analytics.
HSTS is filed under Security.
On-page checks
The homepage returned HTTP 200 in 44 ms. The target title is 42 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 44 ms |
| Title length | 42 yes |
| Quoted title | "Flocus™ | A beautiful way to get more done" |
| Meta description | "Loved by over 1 million professionals and students. Plan your day, run focus sessions, and build a streak with soundscapes, stats, and beautiful themes." yes |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | en |
| Links | 51 |
| Images | 31 |
| 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 flocus.io 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 | yes |
| 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 10 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 2022-08-30T19:59:14Z to 2022-08-30T19:59:14.272Z.
- October 2026: rdap dnssec changed from unknown to no.
- October 2026: rdap expires changed from 2027-08-30T19:59:14Z to 2027-08-30T19:59:14.272Z.
- October 2026: rdap statuses changed from clienttransferprohibited to client transfer prohibited.
- October 2026: rdap updated changed from 2026-08-11T23:37:09Z to 2026-08-11T23:37:09.649Z.
Questions
Is flocus.io 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 flocus.io?
flocus.io is placed in Toronto, Canada.
When does flocus.io expire?
flocus.io expires on 30 August 2027 according to https://rdap.identitydigital.services/rdap/domain/flocus.io.
Who owns flocus.io?
The registry did not return a person or a company for flocus.io. RDAP often redacts the registrant. The registrar on file is Cloudflare, Inc.
Sources
- RDAP source https://rdap.identitydigital.services/rdap/domain/flocus.io at 2026-10-30T14:33:56Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:33:56Z
- TLS source tls:443 at 2026-10-30T14:33:56Z
- HTTP source https://flocus.io/ at 2026-10-30T14:33:56Z
- Tech source wappalyzergo at 2026-10-30T14:33:56Z
- Geo source db-ip at 2026-10-30T14:33:56Z
- Safety source family DNS and local lists at 2026-10-30T14:33:56Z
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.