dnsprobe v1
cached probe / public landing

DNS & SSL for extinct.cz

Last probed 2 hours ago. Use "re-check now" to refresh.

probe.2026093011
probe result / extinct.cz cached 2 hours ago · 3711ms
extinct.cz → · share:
A record [WARN] partial
STATUSRESOLVERIPVALUELATENCY
[--] Cloudflare 1.1.1.1 — no answer 0ms
[--] Cloudflare 2 1.0.0.1 — no answer 0ms
[--] Google 8.8.8.8 — no answer 0ms
[--] Google 2 8.8.4.4 — no answer 0ms
[--] Quad9 9.9.9.9 — no answer 25ms
[--] OpenDNS 208.67.222.222 — no answer 0ms
[OK] DNS.Watch 84.200.69.80
;; communications error to 84.200.69.80#53: timed out ;; no servers could be reached
2885ms
[--] Yandex 77.88.8.8 — no answer 0ms
[--] Comodo 8.26.56.26 — no answer 0ms
[--] Verisign 64.6.64.6 — no answer 0ms
[--] Hurricane Electric 74.82.42.42 — no answer 0ms
[--] AdGuard 94.140.14.14 — no answer 0ms
AAAA record [WARN] partial
STATUSRESOLVERIPVALUELATENCY
[--] Cloudflare 1.1.1.1 — no answer 0ms
[--] Cloudflare 2 1.0.0.1 — no answer 0ms
[--] Google 8.8.8.8 — no answer 0ms
[--] Google 2 8.8.4.4 — no answer 0ms
[--] Quad9 9.9.9.9 — no answer 0ms
[--] OpenDNS 208.67.222.222 — no answer 0ms
[OK] DNS.Watch 84.200.69.80
;; communications error to 84.200.69.80#53: timed out ;; no servers could be reached
15ms
[--] Yandex 77.88.8.8 — no answer 0ms
[--] Comodo 8.26.56.26 — no answer 0ms
[--] Verisign 64.6.64.6 — no answer 0ms
[--] Hurricane Electric 74.82.42.42 — no answer 0ms
[--] AdGuard 94.140.14.14 — no answer 0ms
MX record [WARN] partial
STATUSRESOLVERIPVALUELATENCY
[--] Cloudflare 1.1.1.1 — no answer 0ms
[--] Cloudflare 2 1.0.0.1 — no answer 0ms
[--] Google 8.8.8.8 — no answer 0ms
[--] Google 2 8.8.4.4 — no answer 0ms
[--] Quad9 9.9.9.9 — no answer 0ms
[--] OpenDNS 208.67.222.222 — no answer 0ms
[OK] DNS.Watch 84.200.69.80
;; communications error to 84.200.69.80#53: timed out ;; no servers could be reached
15ms
[--] Yandex 77.88.8.8 — no answer 0ms
[--] Comodo 8.26.56.26 — no answer 0ms
[--] Verisign 64.6.64.6 — no answer 0ms
[--] Hurricane Electric 74.82.42.42 — no answer 0ms
[--] AdGuard 94.140.14.14 — no answer 0ms
TXT record [FAIL] missing
STATUSRESOLVERIPVALUELATENCY
[--] Cloudflare 1.1.1.1 — no answer 0ms
[--] Cloudflare 2 1.0.0.1 — no answer 0ms
[--] Google 8.8.8.8 — no answer 0ms
[--] Google 2 8.8.4.4 — no answer 0ms
[--] Quad9 9.9.9.9 — no answer 0ms
[--] OpenDNS 208.67.222.222 — no answer 0ms
[--] DNS.Watch 84.200.69.80 — no answer 0ms
[--] Yandex 77.88.8.8 — no answer 0ms
[--] Comodo 8.26.56.26 — no answer 0ms
[--] Verisign 64.6.64.6 — no answer 0ms
[--] Hurricane Electric 74.82.42.42 — no answer 0ms
[--] AdGuard 94.140.14.14 — no answer 0ms
NS record [WARN] partial
STATUSRESOLVERIPVALUELATENCY
[--] Cloudflare 1.1.1.1 — no answer 0ms
[--] Cloudflare 2 1.0.0.1 — no answer 0ms
[--] Google 8.8.8.8 — no answer 0ms
[--] Google 2 8.8.4.4 — no answer 0ms
[--] Quad9 9.9.9.9 — no answer 0ms
[--] OpenDNS 208.67.222.222 — no answer 0ms
[OK] DNS.Watch 84.200.69.80
;; communications error to 84.200.69.80#53: timed out ;; no servers could be reached
33ms
[--] Yandex 77.88.8.8 — no answer 0ms
[--] Comodo 8.26.56.26 — no answer 0ms
[--] Verisign 64.6.64.6 — no answer 0ms
[--] Hurricane Electric 74.82.42.42 — no answer 0ms
[--] AdGuard 94.140.14.14 — no answer 0ms
CNAME record [FAIL] missing
STATUSRESOLVERIPVALUELATENCY
[--] Cloudflare 1.1.1.1 — no answer 0ms
[--] Cloudflare 2 1.0.0.1 — no answer 0ms
[--] Google 8.8.8.8 — no answer 0ms
[--] Google 2 8.8.4.4 — no answer 0ms
[--] Quad9 9.9.9.9 — no answer 0ms
[--] OpenDNS 208.67.222.222 — no answer 0ms
[--] DNS.Watch 84.200.69.80 — no answer 0ms
[--] Yandex 77.88.8.8 — no answer 0ms
[--] Comodo 8.26.56.26 — no answer 0ms
[--] Verisign 64.6.64.6 — no answer 0ms
[--] Hurricane Electric 74.82.42.42 — no answer 0ms
[--] AdGuard 94.140.14.14 — no answer 0ms
CAA record [FAIL] missing
STATUSRESOLVERIPVALUELATENCY
[--] Cloudflare 1.1.1.1 — no answer 0ms
[--] Cloudflare 2 1.0.0.1 — no answer 0ms
[--] Google 8.8.8.8 — no answer 0ms
[--] Google 2 8.8.4.4 — no answer 0ms
[--] Quad9 9.9.9.9 — no answer 0ms
[--] OpenDNS 208.67.222.222 — no answer 0ms
[--] DNS.Watch 84.200.69.80 — no answer 0ms
[--] Yandex 77.88.8.8 — no answer 0ms
[--] Comodo 8.26.56.26 — no answer 0ms
[--] Verisign 64.6.64.6 — no answer 0ms
[--] Hurricane Electric 74.82.42.42 — no answer 0ms
[--] AdGuard 94.140.14.14 — no answer 0ms
SOA record [WARN] partial
STATUSRESOLVERIPVALUELATENCY
[--] Cloudflare 1.1.1.1 — no answer 0ms
[--] Cloudflare 2 1.0.0.1 — no answer 0ms
[--] Google 8.8.8.8 — no answer 0ms
[--] Google 2 8.8.4.4 — no answer 0ms
[--] Quad9 9.9.9.9 — no answer 0ms
[--] OpenDNS 208.67.222.222 — no answer 0ms
[OK] DNS.Watch 84.200.69.80
;; communications error to 84.200.69.80#53: timed out ;; no servers could be reached
50ms
[--] Yandex 77.88.8.8 — no answer 0ms
[--] Comodo 8.26.56.26 — no answer 0ms
[--] Verisign 64.6.64.6 — no answer 0ms
[--] Hurricane Electric 74.82.42.42 — no answer 0ms
[--] AdGuard 94.140.14.14 — no answer 0ms
PTR record [FAIL] missing
STATUSRESOLVERIPVALUELATENCY
[--] Cloudflare 1.1.1.1 — no answer 44ms
[--] Cloudflare 2 1.0.0.1 — no answer 0ms
[--] Google 8.8.8.8 — no answer 0ms
[--] Google 2 8.8.4.4 — no answer 0ms
[--] Quad9 9.9.9.9 — no answer 0ms
[--] OpenDNS 208.67.222.222 — no answer 0ms
[--] DNS.Watch 84.200.69.80 — no answer 265ms
[--] Yandex 77.88.8.8 — no answer 0ms
[--] Comodo 8.26.56.26 — no answer 0ms
[--] Verisign 64.6.64.6 — no answer 0ms
[--] Hurricane Electric 74.82.42.42 — no answer 0ms
[--] AdGuard 94.140.14.14 — no answer 141ms
TLS / SSL health [FAIL] no cert

! Could not fetch certificate. The host may not serve TLS on 443 or the handshake failed.

TLS 1.0
[OK] disabled
TLS 1.1
[OK] disabled
TLS 1.2
[--] no
TLS 1.3
[--] no
HTTP/2
[--] no
HTTP/3 (QUIC)
[--] no
HSTS
[--] no
OCSP stapling
[--] no
Need a domain? Register one at Namecheap — cheap registration, free WHOIS privacy. Get it on Namecheap →
Affiliate link — we may earn a commission, at no extra cost to you.
faq / extinct.cz
How does the propagation check work for extinct.cz? →

We query 12 well-known recursive resolvers (Cloudflare, Google, Quad9, OpenDNS and others) in parallel using dig +short with a 3-second per-resolver timeout. The verdict is propagated when every resolver returns the same answer set, partial if any disagree, and missing if none answer.

How accurate is the SSL audit? →

We perform a real TLS handshake against port 443 using openssl s_client for each protocol version, then parse the leaf certificate. HTTP/2 and HTTP/3 are probed with curl. HTTP/3 may be marked as not probeable when our host's libcurl is built without nghttp3.

Why was this result cached? →

Results are cached per hour per domain to be kind to upstream resolvers and to keep this page snappy. Click re-check now to force a fresh probe.