cbhours.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 72 days left8 years oldTranco #141713
80
cbhours.com was registered on 9 Jun 2018 via NameCheap, Inc. and the registry expiry is 9 Jun 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/cbhours.com.
cbhours.com publishes 2 nameservers. DNSSEC is not signed.
cbhours.com has 3 IPv4 addresses (104.26.2.184, 104.26.3.184, 172.67.75.16) and 3 IPv6 addresses (2606:4700:20::681a:2b8, 2606:4700:20::681a:3b8, 2606:4700:20::ac43:4b10). The geolocation database places 104.26.2.184 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 72 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Cloudflare Browser Insights, HTTP/3, Infinite Scroll, LiteSpeed, LiteSpeed Cache, Litespeed Cache and jQuery. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for cbhours.com in the checks that ran.
Domain · RDAP/WHOIS
cbhours.com was registered on 9 Jun 2018 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/cbhours.com.
| Registered | since 9 Jun 2018 |
|---|---|
| Created | 9 June 2018 |
| Updated | 10 May 2026 |
| Expires | 9 June 2027 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | donna.ns.cloudflare.com, logan.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/cbhours.com |
cbhours.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.
Nameserver donna.ns.cloudflare.com is published for cbhours.com in the registration record from https://rdap.verisign.com/com/v1/domain/cbhours.com.
Nameserver logan.ns.cloudflare.com is published for cbhours.com in the registration record from https://rdap.verisign.com/com/v1/domain/cbhours.com.
DNS
cbhours.com has 6 address records, 2 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.26.2.184, 104.26.3.184, 172.67.75.16 |
|---|---|
| AAAA | 2606:4700:20::681a:2b8, 2606:4700:20::681a:3b8, 2606:4700:20::ac43:4b10 |
| NS | donna.ns.cloudflare.com, logan.ns.cloudflare.com |
| MX | mx1.simplelogin.co (10), mx2.simplelogin.co (20) |
| 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 cbhours.com is "v=spf1 include:simplelogin.co ~all".
The DMARC text record at _dmarc.cbhours.com is "v=DMARC1; p=quarantine; pct=100; adkim=s; aspf=s".
IPv4 address 104.26.2.184 answers for cbhours.com at resolver 1.1.1.1:53.
IPv4 address 104.26.3.184 answers for cbhours.com at resolver 1.1.1.1:53.
IPv4 address 172.67.75.16 answers for cbhours.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:2b8 answers for cbhours.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:3b8 answers for cbhours.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::ac43:4b10 answers for cbhours.com at resolver 1.1.1.1:53.
Mail exchanger mx1.simplelogin.co has preference 10.
Mail exchanger mx2.simplelogin.co has preference 20.
Hosting and geo
cbhours.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.26.2.184 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for cbhours.com is valid, with 72 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | cbhours.com |
| Valid from | 14 October 2026 |
| Valid until | 12 January 2027 |
| Days left | 72 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.cbhours.com, cbhours.com.
Tech stack
Tech detection checked the fetched homepage and named 8 products. Source: wappalyzergo.
- Cloudflare · CDN
- Cloudflare Browser Insights · Analytics, RUM
- HTTP/3 · Miscellaneous
- Infinite Scroll · JavaScript libraries
- LiteSpeed · Web servers
- LiteSpeed Cache · Caching, WordPress plugins
- Litespeed Cache · Caching, WordPress plugins
- jQuery · JavaScript libraries
Cloudflare is filed under CDN.
Cloudflare Browser Insights is filed under Analytics, RUM.
HTTP/3 is filed under Miscellaneous.
Infinite Scroll is filed under JavaScript libraries.
LiteSpeed is filed under Web servers.
LiteSpeed Cache is filed under Caching, WordPress plugins.
Litespeed Cache is filed under Caching, WordPress plugins.
jQuery is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 480 ms. The target title is 54 characters and the page has 3 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 480 ms |
| Title length | 54 yes |
| Quoted title | "CB Hours | Chaturbate Model Statistics & Time Tracking" |
| Meta description | none no |
| H1 count | 3 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | https://www.cbhours.com/ |
| Language | en |
| Links | 653 |
| Images | 8 |
| 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 cbhours.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 15 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 cbhours.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 cbhours.com?
cbhours.com is placed in Toronto, Canada.
When does cbhours.com expire?
cbhours.com expires on 9 June 2027 according to https://rdap.verisign.com/com/v1/domain/cbhours.com.
Who owns cbhours.com?
The registry did not return a person or a company for cbhours.com. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/cbhours.com at 2026-10-30T13:48:59Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:48:59Z
- TLS source tls:443 at 2026-10-30T13:48:59Z
- HTTP source https://cbhours.com/ at 2026-10-30T13:48:59Z
- Tech source wappalyzergo at 2026-10-30T13:48:59Z
- Geo source db-ip at 2026-10-30T13:48:59Z
- Safety source family DNS and local lists at 2026-10-30T13:48:59Z
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.