keep2share.cc

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

Online · 200SafeSSL: 37 days left14 years oldTranco #386722

One re-check per domain each UTC day.

80

keep2share.cc was registered on 1 Aug 2012 via Danesco Trading Ltd. and the registry expiry is 1 Aug 2027. WHOIS data came from RDAP at https://tld-rdap.verisign.com/cc/v1/domain/keep2share.cc.

keep2share.cc publishes 2 nameservers. DNSSEC is not signed.

keep2share.cc has 3 IPv4 addresses (104.26.8.42, 104.26.9.42, 172.67.69.105) and 3 IPv6 addresses (2606:4700:20::681a:82a, 2606:4700:20::681a:92a, 2606:4700:20::ac43:4569). The geolocation database places 104.26.8.42 in Toronto, Canada.

The TLS certificate from YE1 is valid and has 37 days left (TLS 1.3). The homepage answered HTTP 200.

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

No safety warning was recorded for keep2share.cc in the checks that ran.

Domain · RDAP/WHOIS

keep2share.cc was registered on 1 Aug 2012 via Danesco Trading Ltd.. The registry returned 2 status values and 2 nameservers from https://tld-rdap.verisign.com/cc/v1/domain/keep2share.cc.

Registeredsince 1 Aug 2012
Created1 August 2012
Updated1 July 2026
Expires1 August 2027
RegistrarDanesco Trading Ltd.
Statusclient delete prohibited, client transfer prohibited
Nameserversnina.ns.cloudflare.com, theo.ns.cloudflare.com
DNSSECno
Sourcehttps://tld-rdap.verisign.com/cc/v1/domain/keep2share.cc

keep2share.cc carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.

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

Nameserver theo.ns.cloudflare.com is published for keep2share.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/keep2share.cc.

DNS

keep2share.cc has 6 address records, 5 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A104.26.8.42, 104.26.9.42, 172.67.69.105
AAAA2606:4700:20::681a:82a, 2606:4700:20::681a:92a, 2606:4700:20::ac43:4569
NSnina.ns.cloudflare.com, theo.ns.cloudflare.com
MXaspmx.l.google.com (1) Google, alt1.aspmx.l.google.com (5) Google, alt2.aspmx.l.google.com (5) Google, aspmx2.googlemail.com (10) Google, aspmx3.googlemail.com (10) Google
SPFpresent
DMARCpresent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

The SPF text record at keep2share.cc is "v=spf1 mx include:_spf.google.com include:_spf.keep2share.cc ~all".

The DMARC text record at _dmarc.keep2share.cc is "v=DMARC1; p=none; sp=none;".

IPv4 address 104.26.8.42 answers for keep2share.cc at resolver 1.1.1.1:53.

IPv4 address 104.26.9.42 answers for keep2share.cc at resolver 1.1.1.1:53.

IPv4 address 172.67.69.105 answers for keep2share.cc at resolver 1.1.1.1:53.

IPv6 address 2606:4700:20::681a:82a answers for keep2share.cc at resolver 1.1.1.1:53.

IPv6 address 2606:4700:20::681a:92a answers for keep2share.cc at resolver 1.1.1.1:53.

IPv6 address 2606:4700:20::ac43:4569 answers for keep2share.cc at resolver 1.1.1.1:53.

Mail exchanger aspmx.l.google.com has preference 1. The host is recognised as Google.

Mail exchanger alt1.aspmx.l.google.com has preference 5. The host is recognised as Google.

Mail exchanger alt2.aspmx.l.google.com has preference 5. The host is recognised as Google.

Mail exchanger aspmx2.googlemail.com has preference 10. The host is recognised as Google.

Mail exchanger aspmx3.googlemail.com has preference 10. The host is recognised as Google.

Hosting and geo

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

Address104.26.8.42
CountryCanada
CityToronto
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for keep2share.cc is valid, with 37 days left and 2 subject alternative names. Source: tls:443.

IssuerYE1
Subjectkeep2share.cc
Valid from8 September 2026
Valid until7 December 2026
Days left37
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: *.keep2share.cc, keep2share.cc.

Tech stack

Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.

  • Cloudflare · CDN
  • HSTS · Security

Cloudflare is filed under CDN.

HSTS is filed under Security.

On-page checks

The homepage returned HTTP 200 in 0 ms. The target title is 0 characters and the page has 0 H1 headings.

Status200
TTFB0 ms
Title length0 no
Quoted titlenone
Meta descriptionnone no
H1 count0
HSTSyes yes
CSPno
X-Frame-Options—
Robots meta—
Canonical—
Language—
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 keep2share.cc is clear, and URLhaus is clear. Source: family DNS and local lists.

Family DNSclear
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSyes
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 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 10 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 keep2share.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 keep2share.cc?

keep2share.cc is placed in Toronto, Canada.

When does keep2share.cc expire?

keep2share.cc expires on 1 August 2027 according to https://tld-rdap.verisign.com/cc/v1/domain/keep2share.cc.

Who owns keep2share.cc?

The registry did not return a person or a company for keep2share.cc. RDAP often redacts the registrant. The registrar on file is Danesco Trading Ltd..

Sources

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

Methodology

Related reports

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

.cc Danesco Trading Ltd.

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.