qbtr.cc
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 45 days left5 years oldTranco #76252
70
qbtr.cc was registered on 28 Nov 2020 via NameSilo, LLC and the registry expiry is 28 Nov 2027. WHOIS data came from RDAP at https://tld-rdap.verisign.com/cc/v1/domain/qbtr.cc.
qbtr.cc publishes 2 nameservers. DNSSEC is not signed.
qbtr.cc has 2 IPv4 addresses (104.21.49.191, 172.67.148.243) and 2 IPv6 addresses (2606:4700:3033::6815:31bf, 2606:4700:3034::ac43:94f3). The geolocation database places 104.21.49.191 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 45 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, HSTS and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for qbtr.cc in the checks that ran.
Domain · RDAP/WHOIS
qbtr.cc was registered on 28 Nov 2020 via NameSilo, LLC. The registry returned 1 status value and 2 nameservers from https://tld-rdap.verisign.com/cc/v1/domain/qbtr.cc.
| Registered | since 28 Nov 2020 |
|---|---|
| Created | 28 November 2020 |
| Updated | 5 August 2026 |
| Expires | 28 November 2027 |
| Registrar | NameSilo, LLC |
| Status | client transfer prohibited |
| Nameservers | renan.ns.cloudflare.com, shaz.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://tld-rdap.verisign.com/cc/v1/domain/qbtr.cc |
qbtr.cc 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 renan.ns.cloudflare.com is published for qbtr.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/qbtr.cc.
Nameserver shaz.ns.cloudflare.com is published for qbtr.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/qbtr.cc.
DNS
qbtr.cc has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.49.191, 172.67.148.243 |
|---|---|
| AAAA | 2606:4700:3033::6815:31bf, 2606:4700:3034::ac43:94f3 |
| NS | renan.ns.cloudflare.com, shaz.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.49.191 answers for qbtr.cc at resolver 1.1.1.1:53.
IPv4 address 172.67.148.243 answers for qbtr.cc at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3033::6815:31bf answers for qbtr.cc at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3034::ac43:94f3 answers for qbtr.cc at resolver 1.1.1.1:53.
Hosting and geo
qbtr.cc is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.49.191 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for qbtr.cc is valid, with 45 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | qbtr.cc |
| Valid from | 17 September 2026 |
| Valid until | 16 December 2026 |
| Days left | 45 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.qbtr.cc, qbtr.cc.
Tech stack
Tech detection checked the fetched homepage and named 3 products. Source: wappalyzergo.
- Cloudflare · CDN
- HSTS · Security
- HTTP/3 · Miscellaneous
Cloudflare is filed under CDN.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 200 in 347 ms. The target title is 44 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 347 ms |
| Title length | 44 yes |
| Quoted title | "ȫ��ͬ��С˵��,ȫ��С˵,��УС˵,ͬ��С˵���а�,�ÿ���ͬ��С˵" |
| Meta description | "ȫ��ͬ��С˵���ṩ���źÿ����µ�ͬ��С˵�����Ķ�������,����ȫ��ͬ��С˵�����Ķ������أ�" yes |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 101 |
| Images | 4 |
| 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 qbtr.cc 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 0 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
First checked on 30 October 2026; changes will appear here.
Questions
Is qbtr.cc 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 qbtr.cc?
qbtr.cc is placed in Toronto, Canada.
When does qbtr.cc expire?
qbtr.cc expires on 28 November 2027 according to https://tld-rdap.verisign.com/cc/v1/domain/qbtr.cc.
Who owns qbtr.cc?
The registry did not return a person or a company for qbtr.cc. RDAP often redacts the registrant. The registrar on file is NameSilo, LLC.
Sources
- RDAP source https://tld-rdap.verisign.com/cc/v1/domain/qbtr.cc at 2026-10-30T13:34:51Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:34:51Z
- TLS source tls:443 at 2026-10-30T13:34:51Z
- HTTP source https://qbtr.cc/ at 2026-10-30T13:34:51Z
- Tech source wappalyzergo at 2026-10-30T13:34:51Z
- Geo source db-ip at 2026-10-30T13:34:51Z
- Safety source family DNS and local lists at 2026-10-30T13:34:51Z
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.