qzsp13.com

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

HTTP 404Family DNS blockedSSL: 74 days left7 years old

One re-check per domain each UTC day.

35

qzsp13.com was registered on 16 Jun 2019 via NameSilo, LLC and the registry expiry is 16 Jun 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/qzsp13.com.

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

qzsp13.com has 2 IPv4 addresses (104.21.13.73, 172.67.155.15) and 2 IPv6 addresses (2606:4700:3030::6815:d49, 2606:4700:3034::ac43:9b0f). The geolocation database places 104.21.13.73 in Toronto, Canada.

The TLS certificate from YE2 is valid and has 74 days left (TLS 1.3).

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

Domain · RDAP/WHOIS

qzsp13.com was registered on 16 Jun 2019 via NameSilo, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/qzsp13.com.

Registeredsince 16 Jun 2019
Created16 June 2019
Updated6 June 2026
Expires16 June 2027
RegistrarNameSilo, LLC
Statusclient transfer prohibited
Nameserversbristol.ns.cloudflare.com, hugh.ns.cloudflare.com
DNSSECno
Sourcehttps://rdap.verisign.com/com/v1/domain/qzsp13.com

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

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

DNS

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

A104.21.13.73, 172.67.155.15
AAAA2606:4700:3030::6815:d49, 2606:4700:3034::ac43:9b0f
NSbristol.ns.cloudflare.com, hugh.ns.cloudflare.com
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 104.21.13.73 answers for qzsp13.com at resolver 1.1.1.1:53.

IPv4 address 172.67.155.15 answers for qzsp13.com at resolver 1.1.1.1:53.

IPv6 address 2606:4700:3030::6815:d49 answers for qzsp13.com at resolver 1.1.1.1:53.

IPv6 address 2606:4700:3034::ac43:9b0f answers for qzsp13.com at resolver 1.1.1.1:53.

Hosting and geo

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

Address104.21.13.73
CountryCanada
CityToronto
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

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

IssuerYE2
Subjectqzsp13.com
Valid from16 October 2026
Valid until14 January 2027
Days left74
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: *.qzsp13.com, qzsp13.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 404 in 330 ms. The target title is 13 characters and the page has 0 H1 headings.

Status404
TTFB330 ms
Title length13 yes
Quoted title"404 not found"
Meta descriptionnone no
H1 count0
HSTSno no
CSPno
X-Frame-Options—
Robots meta—
Canonical—
Languageen
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 qzsp13.com is blocked, and URLhaus is clear. Source: family DNS and local lists.

Family DNSblocked
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSno
CSPno

Cloudflare family DNS returned a block for qzsp13.com. That resolver covers adult and malware names.

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 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.

Safety lists 0 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 qzsp13.com safe?

Cloudflare family DNS returned a block for qzsp13.com. That resolver covers adult and malware names.

Who hosts qzsp13.com?

qzsp13.com is placed in Toronto, Canada.

When does qzsp13.com expire?

qzsp13.com expires on 16 June 2027 according to https://rdap.verisign.com/com/v1/domain/qzsp13.com.

Who owns qzsp13.com?

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

Sources

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

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.