countwordsworth.com

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

HTTP 403SafeSSL: 80 days left13 years old

One re-check per domain each UTC day.

55

countwordsworth.com was registered on 15 Feb 2013 via NameCheap, Inc. and the registry expiry is 15 Feb 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/countwordsworth.com.

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

countwordsworth.com has 2 IPv4 addresses (104.21.58.119, 172.67.159.107) and 2 IPv6 addresses (2606:4700:3033::6815:3a77, 2606:4700:3037::ac43:9f6b). The geolocation database places 104.21.58.119 in Toronto, Canada.

The TLS certificate from WE1 is valid and has 80 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 countwordsworth.com in the checks that ran.

Domain · RDAP/WHOIS

countwordsworth.com was registered on 15 Feb 2013 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/countwordsworth.com.

Registeredsince 15 Feb 2013
Created15 February 2013
Updated16 January 2026
Expires15 February 2027
RegistrarNameCheap, Inc.
Statusclient transfer prohibited
Nameserverscash.ns.cloudflare.com, dara.ns.cloudflare.com
DNSSECno
Sourcehttps://rdap.verisign.com/com/v1/domain/countwordsworth.com

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

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

DNS

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

A104.21.58.119, 172.67.159.107
AAAA2606:4700:3033::6815:3a77, 2606:4700:3037::ac43:9f6b
NScash.ns.cloudflare.com, dara.ns.cloudflare.com
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 104.21.58.119 answers for countwordsworth.com at resolver 1.1.1.1:53.

IPv4 address 172.67.159.107 answers for countwordsworth.com at resolver 1.1.1.1:53.

IPv6 address 2606:4700:3033::6815:3a77 answers for countwordsworth.com at resolver 1.1.1.1:53.

IPv6 address 2606:4700:3037::ac43:9f6b answers for countwordsworth.com at resolver 1.1.1.1:53.

Hosting and geo

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

Address104.21.58.119
CountryCanada
CityToronto
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

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

IssuerWE1
Subjectcountwordsworth.com
Valid from21 October 2026
Valid until19 January 2027
Days left80
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: *.countwordsworth.com, countwordsworth.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 34 ms. The target title is 36 characters and the page has 1 H1 heading.

Status403
TTFB34 ms
Title length36 yes
Quoted title"CNAME Cross-User Banned | Cloudflare"
Meta descriptionnone no
H1 count1
HSTSno no
CSPno
X-Frame-OptionsSAMEORIGIN
Robots metanoindex, nofollow
Canonical—
Languageen-US
Links5
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 countwordsworth.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
CSPno

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 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 countwordsworth.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 countwordsworth.com?

countwordsworth.com is placed in Toronto, Canada.

When does countwordsworth.com expire?

countwordsworth.com expires on 15 February 2027 according to https://rdap.verisign.com/com/v1/domain/countwordsworth.com.

Who owns countwordsworth.com?

The registry did not return a person or a company for countwordsworth.com. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..

Sources

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

Methodology

Related reports

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

.com NameCheap, Inc.

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.