qkan8.com

Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .

HTTP 403SafeSSL: 58 days left8 years old

One re-check per domain each UTC day.

60

qkan8.com was registered on 6 Aug 2018 via NameSilo, LLC and the registry expiry is 6 Aug 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/qkan8.com.

qkan8.com publishes 2 nameservers. DNSSEC is not signed.

qkan8.com has 2 IPv4 addresses (104.21.42.175, 172.67.206.210) and 2 IPv6 addresses (2606:4700:3030::ac43:ced2, 2606:4700:3032::6815:2aaf). The geolocation database places 104.21.42.175 in Toronto, Canada.

The TLS certificate from WE1 is valid and has 58 days left (TLS 1.3).

Tech detection named Cloudflare and HTTP/3. The fingerprints ran on the homepage that was already downloaded.

No safety warning was recorded for qkan8.com in the checks that ran.

Domain · RDAP/WHOIS

qkan8.com was registered on 6 Aug 2018 via NameSilo, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/qkan8.com.

Registeredsince 6 Aug 2018
Created6 August 2018
Updated1 August 2026
Expires6 August 2027
RegistrarNameSilo, LLC
Statusclient transfer prohibited
Nameserversjohnathan.ns.cloudflare.com, norah.ns.cloudflare.com
DNSSECno
Sourcehttps://rdap.verisign.com/com/v1/domain/qkan8.com

qkan8.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 johnathan.ns.cloudflare.com is published for qkan8.com in the registration record from https://rdap.verisign.com/com/v1/domain/qkan8.com.

Nameserver norah.ns.cloudflare.com is published for qkan8.com in the registration record from https://rdap.verisign.com/com/v1/domain/qkan8.com.

DNS

qkan8.com has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A104.21.42.175, 172.67.206.210
AAAA2606:4700:3030::ac43:ced2, 2606:4700:3032::6815:2aaf
NSjohnathan.ns.cloudflare.com, norah.ns.cloudflare.com
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 104.21.42.175 answers for qkan8.com at resolver 1.1.1.1:53.

IPv4 address 172.67.206.210 answers for qkan8.com at resolver 1.1.1.1:53.

IPv6 address 2606:4700:3030::ac43:ced2 answers for qkan8.com at resolver 1.1.1.1:53.

IPv6 address 2606:4700:3032::6815:2aaf answers for qkan8.com at resolver 1.1.1.1:53.

Hosting and geo

qkan8.com is placed in Toronto, Canada by the local geolocation database (db-ip).

Address104.21.42.175
CountryCanada
CityToronto
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for qkan8.com is valid, with 58 days left and 2 subject alternative names. Source: tls:443.

IssuerWE1
Subjectqkan8.com
Valid from30 September 2026
Valid until29 December 2026
Days left58
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: *.qkan8.com, qkan8.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 403 in 31 ms. The target title is 16 characters and the page has 0 H1 headings.

Status403
TTFB31 ms
Title length16 yes
Quoted title"Just a moment..."
Meta descriptionnone no
H1 count0
HSTSno no
CSPyes
X-Frame-OptionsSAMEORIGIN
Robots metanoindex,nofollow
Canonical—
Languageen-US
Links0
Images0
Faviconno

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 qkan8.com is clear, and URLhaus is clear. Source: family DNS and local lists.

Family DNSclear
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSno
CSPyes

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 10 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 10 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 qkan8.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 qkan8.com?

qkan8.com is placed in Toronto, Canada.

When does qkan8.com expire?

qkan8.com expires on 6 August 2027 according to https://rdap.verisign.com/com/v1/domain/qkan8.com.

Who owns qkan8.com?

The registry did not return a person or a company for qkan8.com. RDAP often redacts the registrant. The registrar on file is NameSilo, LLC.

Sources

  • RDAP source https://rdap.verisign.com/com/v1/domain/qkan8.com at 2026-10-30T14:10:56Z
  • DNS source 1.1.1.1:53 at 2026-10-30T14:10:56Z
  • TLS source tls:443 at 2026-10-30T14:10:56Z
  • HTTP source https://qkan8.com/ at 2026-10-30T14:10:56Z
  • Tech source wappalyzergo at 2026-10-30T14:10:56Z
  • Geo source db-ip at 2026-10-30T14:10:56Z
  • Safety source family DNS and local lists at 2026-10-30T14:10:56Z

Methodology

Related reports

No other indexable reports share this TLD, host, or registrar yet.

.com NameSilo, LLC

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.

Removal policy

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.