watchflx.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 30 days left7 years old
65
watchflx.com was registered on 4 Dec 2018 via Tucows Domains Inc. and the registry expiry is 4 Dec 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/watchflx.com.
watchflx.com publishes 2 nameservers. DNSSEC is not signed.
watchflx.com has 2 IPv4 addresses (188.114.96.3, 188.114.97.3). The geolocation database places 188.114.96.3 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 30 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 watchflx.com in the checks that ran.
Domain · RDAP/WHOIS
watchflx.com was registered on 4 Dec 2018 via Tucows Domains Inc.. The registry returned 2 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/watchflx.com.
| Registered | since 4 Dec 2018 |
|---|---|
| Created | 4 December 2018 |
| Updated | 23 July 2026 |
| Expires | 4 December 2027 |
| Registrar | Tucows Domains Inc. |
| Status | client transfer prohibited, client update prohibited |
| Nameservers | kim.ns.cloudflare.com, merlin.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/watchflx.com |
watchflx.com 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.
watchflx.com carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver kim.ns.cloudflare.com is published for watchflx.com in the registration record from https://rdap.verisign.com/com/v1/domain/watchflx.com.
Nameserver merlin.ns.cloudflare.com is published for watchflx.com in the registration record from https://rdap.verisign.com/com/v1/domain/watchflx.com.
DNS
watchflx.com has 2 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.3, 188.114.97.3 |
|---|---|
| AAAA | — |
| NS | kim.ns.cloudflare.com, merlin.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 188.114.96.3 answers for watchflx.com at resolver 1.1.1.1:53.
IPv4 address 188.114.97.3 answers for watchflx.com at resolver 1.1.1.1:53.
Hosting and geo
watchflx.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.3 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for watchflx.com is valid, with 30 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | watchflx.com |
| Valid from | 2 September 2026 |
| Valid until | 1 December 2026 |
| Days left | 30 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.watchflx.com, watchflx.com.
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 70 ms. The target title is 5 characters and the page has 2 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 70 ms |
| Title length | 5 yes |
| Quoted title | "Login" |
| Meta description | none no |
| H1 count | 2 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 1 |
| Images | 1 |
| Favicon | no |
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 watchflx.com 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 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
- October 2026: dns a changed from 188.114.96.4,188.114.97.4 to 188.114.96.3,188.114.97.3.
Questions
Is watchflx.com 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 watchflx.com?
watchflx.com is placed in Toronto, Canada.
When does watchflx.com expire?
watchflx.com expires on 4 December 2027 according to https://rdap.verisign.com/com/v1/domain/watchflx.com.
Who owns watchflx.com?
The registry did not return a person or a company for watchflx.com. RDAP often redacts the registrant. The registrar on file is Tucows Domains Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/watchflx.com at 2026-10-30T14:19:39Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:19:39Z
- TLS source tls:443 at 2026-10-30T14:19:39Z
- HTTP source https://watchflx.com/ at 2026-10-30T14:19:39Z
- Tech source wappalyzergo at 2026-10-30T14:19:39Z
- Geo source db-ip at 2026-10-30T14:19:39Z
- Safety source family DNS and local lists at 2026-10-30T14:19:39Z
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.