DNS & SSL for firefly.extinct.cz
Last probed 1 hour ago. Use "re-check now" to refresh.
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
13.140.179.162
|
0ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
13.140.179.162
|
0ms |
| [OK] | 8.8.8.8 |
13.140.179.162
|
0ms | |
| [OK] | Google 2 | 8.8.4.4 |
13.140.179.162
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
13.140.179.162
|
0ms |
| [OK] | OpenDNS | 208.67.222.222 |
13.140.179.162
|
0ms |
| [OK] | DNS.Watch | 84.200.69.80 |
;; communications error to 84.200.69.80#53: timed out
;; no servers could be reached
|
2917ms |
| [OK] | Yandex | 77.88.8.8 |
13.140.179.162
|
0ms |
| [OK] | Comodo | 8.26.56.26 |
;; communications error to 8.26.56.26#53: timed out
;; no servers could be reached
|
0ms |
| [OK] | Verisign | 64.6.64.6 |
185.8.237.6
185.8.237.5
|
0ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
13.140.179.162
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
13.140.179.162
|
0ms |
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [--] | Cloudflare | 1.1.1.1 | — no answer | 0ms |
| [--] | Cloudflare 2 | 1.0.0.1 | — no answer | 0ms |
| [--] | 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
|
28ms |
| [--] | Yandex | 77.88.8.8 | — no answer | 0ms |
| [OK] | Comodo | 8.26.56.26 |
;; communications error to 8.26.56.26#53: timed out
;; no servers could be reached
|
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 |
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [--] | Cloudflare | 1.1.1.1 | — no answer | 0ms |
| [--] | Cloudflare 2 | 1.0.0.1 | — no answer | 0ms |
| [--] | 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
|
4ms |
| [--] | Yandex | 77.88.8.8 | — no answer | 0ms |
| [OK] | Comodo | 8.26.56.26 |
;; communications error to 8.26.56.26#53: timed out
;; no servers could be reached
|
1ms |
| [--] | 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 |
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [--] | Cloudflare | 1.1.1.1 | — no answer | 0ms |
| [--] | Cloudflare 2 | 1.0.0.1 | — no answer | 0ms |
| [--] | 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
|
16ms |
| [--] | Yandex | 77.88.8.8 | — no answer | 0ms |
| [OK] | Comodo | 8.26.56.26 |
;; communications error to 8.26.56.26#53: timed out
;; no servers could be reached
|
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 |
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [--] | Cloudflare | 1.1.1.1 | — no answer | 0ms |
| [--] | Cloudflare 2 | 1.0.0.1 | — no answer | 0ms |
| [--] | 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
|
18ms |
| [--] | Yandex | 77.88.8.8 | — no answer | 0ms |
| [OK] | Comodo | 8.26.56.26 |
;; communications error to 8.26.56.26#53: timed out
;; no servers could be reached
|
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 |
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [--] | Cloudflare | 1.1.1.1 | — no answer | 0ms |
| [--] | Cloudflare 2 | 1.0.0.1 | — no answer | 0ms |
| [--] | 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 |
| [OK] | Comodo | 8.26.56.26 |
;; communications error to 8.26.56.26#53: timed out
;; no servers could be reached
|
16ms |
| [--] | 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 |
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [--] | Cloudflare | 1.1.1.1 | — no answer | 0ms |
| [--] | Cloudflare 2 | 1.0.0.1 | — no answer | 0ms |
| [--] | 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
|
0ms |
| [--] | Yandex | 77.88.8.8 | — no answer | 0ms |
| [OK] | Comodo | 8.26.56.26 |
;; communications error to 8.26.56.26#53: timed out
;; no servers could be reached
|
15ms |
| [--] | 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 |
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [--] | Cloudflare | 1.1.1.1 | — no answer | 0ms |
| [--] | Cloudflare 2 | 1.0.0.1 | — no answer | 0ms |
| [--] | 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 |
| [OK] | Comodo | 8.26.56.26 |
;; communications error to 8.26.56.26#53: timed out
;; no servers could be reached
|
10ms |
| [--] | 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 |
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
vmi3369436.contaboserver.net.
|
45ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
vmi3369436.contaboserver.net.
|
5ms |
| [OK] | 8.8.8.8 |
vmi3369436.contaboserver.net.
|
0ms | |
| [OK] | Google 2 | 8.8.4.4 |
vmi3369436.contaboserver.net.
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
vmi3369436.contaboserver.net.
|
381ms |
| [OK] | OpenDNS | 208.67.222.222 |
vmi3369436.contaboserver.net.
|
0ms |
| [OK] | DNS.Watch | 84.200.69.80 |
vmi3369436.contaboserver.net.
|
0ms |
| [OK] | Yandex | 77.88.8.8 |
vmi3369436.contaboserver.net.
|
0ms |
| [OK] | Comodo | 8.26.56.26 |
;; communications error to 8.26.56.26#53: timed out
;; no servers could be reached
|
2599ms |
| [OK] | Verisign | 64.6.64.6 |
vmi3369436.contaboserver.net.
|
0ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
vmi3369436.contaboserver.net.
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
vmi3369436.contaboserver.net.
|
0ms |
06:8A:C9:82:88:B6:22:AB:95:1D:CE:DB:FD:EA:E5:89:F8:E2:A4:8D:79:7F:85:C2:1A:A3:4F:C5:FB:4A:10:9B
How does the propagation check work for firefly.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.