34img.cc

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

Online · 200Family DNS blockedSSL: 76 days left5 years old

One re-check per domain each UTC day.

55

34img.cc was registered on 2 Sep 2021 via NameCheap, Inc. and the registry expiry is 2 Sep 2027. WHOIS data came from RDAP at https://tld-rdap.verisign.com/cc/v1/domain/34img.cc.

34img.cc publishes 2 nameservers. DNSSEC is not signed.

34img.cc has 2 IPv4 addresses (104.21.27.227, 172.67.169.203) and 2 IPv6 addresses (2606:4700:3033::6815:1be3, 2606:4700:3036::ac43:a9cb). The geolocation database places 104.21.27.227 in Toronto, Canada.

The TLS certificate from WE1 is valid and has 76 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.

Domain · RDAP/WHOIS

34img.cc was registered on 2 Sep 2021 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://tld-rdap.verisign.com/cc/v1/domain/34img.cc.

Registeredsince 2 Sep 2021
Created2 September 2021
Updated4 August 2026
Expires2 September 2027
RegistrarNameCheap, Inc.
Statusclient transfer prohibited
Nameserversdecker.ns.cloudflare.com, kay.ns.cloudflare.com
DNSSECno
Sourcehttps://tld-rdap.verisign.com/cc/v1/domain/34img.cc

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

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

DNS

34img.cc has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A104.21.27.227, 172.67.169.203
AAAA2606:4700:3033::6815:1be3, 2606:4700:3036::ac43:a9cb
NSdecker.ns.cloudflare.com, kay.ns.cloudflare.com
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 104.21.27.227 answers for 34img.cc at resolver 1.1.1.1:53.

IPv4 address 172.67.169.203 answers for 34img.cc at resolver 1.1.1.1:53.

IPv6 address 2606:4700:3033::6815:1be3 answers for 34img.cc at resolver 1.1.1.1:53.

IPv6 address 2606:4700:3036::ac43:a9cb answers for 34img.cc at resolver 1.1.1.1:53.

Hosting and geo

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

Address104.21.27.227
CountryCanada
CityToronto
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

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

IssuerWE1
Subject34img.cc
Valid from17 October 2026
Valid until15 January 2027
Days left76
SAN count2
ProtocolTLS 1.3
Sourcetls:443

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

Status200
TTFB466 ms
Title length8 yes
Quoted title"三四娱乐最新地址"
Meta descriptionnone no
H1 count1
HSTSyes yes
CSPno
X-Frame-Options—
Robots meta—
Canonical—
Language—
Links7
Images1
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 34img.cc is blocked, and URLhaus is clear. Source: family DNS and local lists.

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

Cloudflare family DNS returned a block for 34img.cc. 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 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 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 34img.cc safe?

Cloudflare family DNS returned a block for 34img.cc. That resolver covers adult and malware names.

Who hosts 34img.cc?

34img.cc is placed in Toronto, Canada.

When does 34img.cc expire?

34img.cc expires on 2 September 2027 according to https://tld-rdap.verisign.com/cc/v1/domain/34img.cc.

Who owns 34img.cc?

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

Sources

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

Methodology

Related reports

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

.cc 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.