turbo-zec.icu

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

Online · 200SafeSSL: 88 days leftUnder 1 year old

One re-check per domain each UTC day.

62

turbo-zec.icu was registered on 3 Dec 2025 via Dynadot Inc and the registry expiry is 3 Dec 2026. WHOIS data came from RDAP at https://rdap.centralnic.com/icu/domain/turbo-zec.icu.

turbo-zec.icu publishes 2 nameservers. DNSSEC is not signed.

turbo-zec.icu has 1 IPv4 address (213.199.63.58). The geolocation database places 213.199.63.58 in London, United Kingdom.

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

Tech detection named Nginx and Ubuntu. The fingerprints ran on the homepage that was already downloaded.

No safety warning was recorded for turbo-zec.icu in the checks that ran.

Domain · RDAP/WHOIS

turbo-zec.icu was registered on 3 Dec 2025 via Dynadot Inc. The registry returned 1 status value and 2 nameservers from https://rdap.centralnic.com/icu/domain/turbo-zec.icu.

Registeredsince 3 Dec 2025
Created3 December 2025
Updated22 January 2026
Expires3 December 2026
RegistrarDynadot Inc
Statusclient transfer prohibited
Nameserversns1.dnsservice.xyz, ns2.dnsservice.xyz
DNSSECno
Sourcehttps://rdap.centralnic.com/icu/domain/turbo-zec.icu

turbo-zec.icu 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 ns1.dnsservice.xyz is published for turbo-zec.icu in the registration record from https://rdap.centralnic.com/icu/domain/turbo-zec.icu.

Nameserver ns2.dnsservice.xyz is published for turbo-zec.icu in the registration record from https://rdap.centralnic.com/icu/domain/turbo-zec.icu.

DNS

turbo-zec.icu has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.

A213.199.63.58
AAAA—
NSns1.dnsservice.xyz, ns2.dnsservice.xyz
MXmail.turbo-zec.icu (10)
SPFabsent
DMARCabsent
CAA—
Wildcardon
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 213.199.63.58 answers for turbo-zec.icu at resolver 1.1.1.1:53.

Mail exchanger mail.turbo-zec.icu has preference 10.

A random label under turbo-zec.icu also resolved, which means wildcard DNS is on.

Hosting and geo

turbo-zec.icu is placed in London, United Kingdom by the local geolocation database (db-ip).

Address213.199.63.58
CountryUnited Kingdom
CityLondon
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for turbo-zec.icu is valid, with 88 days left and 2 subject alternative names. Source: tls:443.

IssuerYE2
Subjectturbo-zec.icu
Valid from30 October 2026
Valid until28 January 2027
Days left88
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: turbo-zec.icu, www.turbo-zec.icu.

Tech stack

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

  • Nginx · Web servers, Reverse proxies
  • Ubuntu · Operating systems

Nginx is filed under Web servers, Reverse proxies.

Ubuntu is filed under Operating systems.

On-page checks

The homepage returned HTTP 200 in 10 ms. The target title is 13 characters and the page has 1 H1 heading.

Status200
TTFB10 ms
Title length13 yes
Quoted title"turbo-zec.icu"
Meta descriptionnone no
H1 count1
HSTSno no
CSPno
X-Frame-Options—
Robots meta—
Canonical—
Languageen
Links534
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 turbo-zec.icu 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 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 0 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 2 of 5. Five points at one year, two points at 30 days.

Change history

  • October 2026: geo city changed from empty to London.
  • October 2026: geo country changed from empty to United Kingdom.

Questions

Is turbo-zec.icu 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 turbo-zec.icu?

turbo-zec.icu is placed in London, United Kingdom.

When does turbo-zec.icu expire?

turbo-zec.icu expires on 3 December 2026 according to https://rdap.centralnic.com/icu/domain/turbo-zec.icu.

Who owns turbo-zec.icu?

The registry did not return a person or a company for turbo-zec.icu. RDAP often redacts the registrant. The registrar on file is Dynadot Inc.

Sources

  • RDAP source https://rdap.centralnic.com/icu/domain/turbo-zec.icu at 2026-10-30T14:32:19Z
  • DNS source 1.1.1.1:53 at 2026-10-30T14:32:19Z
  • TLS source tls:443 at 2026-10-30T14:32:19Z
  • HTTP source https://turbo-zec.icu/ at 2026-10-30T14:32:19Z
  • Tech source wappalyzergo at 2026-10-30T14:32:19Z
  • Geo source db-ip at 2026-10-30T14:32:19Z
  • Safety source family DNS and local lists at 2026-10-30T14:32:19Z

Methodology

Related reports

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

.icu Dynadot 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.