DNS & SSL for sun.mnode.net
Last probed 6 days ago. Use "re-check now" to refresh.
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
47.18.221.127
|
992ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
47.18.221.127
|
0ms |
| [OK] | 8.8.8.8 |
47.18.221.127
|
1104ms | |
| [OK] | Google 2 | 8.8.4.4 |
47.18.221.127
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
47.18.221.127
|
0ms |
| [OK] | OpenDNS | 208.67.222.222 |
47.18.221.127
|
0ms |
| [OK] | DNS.Watch | 84.200.69.80 |
;; communications error to 84.200.69.80#53: timed out
;; no servers could be reached
|
836ms |
| [OK] | Yandex | 77.88.8.8 |
47.18.221.127
|
0ms |
| [OK] | Comodo | 8.26.56.26 |
47.18.221.127
|
0ms |
| [OK] | Verisign | 64.6.64.6 |
47.18.221.127
|
0ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
47.18.221.127
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
47.18.221.127
|
0ms |
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [--] | Cloudflare | 1.1.1.1 | — no answer | 0ms |
| [--] | Cloudflare 2 | 1.0.0.1 | — no answer | 2ms |
| [--] | 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
|
4ms |
| [--] | 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
|
2ms |
| [--] | 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
|
6ms |
| [--] | 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
|
5ms |
| [--] | 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 |
| [--] | 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 |
| 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
|
27ms |
| [--] | 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 |
| [--] | 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 |
| 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 |
| [--] | 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 |
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
ool-2f12dd7f.dyn.optonline.net.
|
121ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
ool-2f12dd7f.dyn.optonline.net.
|
1ms |
| [OK] | 8.8.8.8 |
ool-2f12dd7f.dyn.optonline.net.
|
1ms | |
| [OK] | Google 2 | 8.8.4.4 |
ool-2f12dd7f.dyn.optonline.net.
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
ool-2f12dd7f.dyn.optonline.net.
|
1375ms |
| [OK] | OpenDNS | 208.67.222.222 |
ool-2f12dd7f.dyn.optonline.net.
|
0ms |
| [OK] | DNS.Watch | 84.200.69.80 |
ool-2f12dd7f.dyn.optonline.net.
|
0ms |
| [OK] | Yandex | 77.88.8.8 |
ool-2f12dd7f.dyn.optonline.net.
|
0ms |
| [OK] | Comodo | 8.26.56.26 |
ool-2f12dd7f.dyn.optonline.net.
|
0ms |
| [OK] | Verisign | 64.6.64.6 |
ool-2f12dd7f.dyn.optonline.net.
|
0ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
ool-2f12dd7f.dyn.optonline.net.
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
ool-2f12dd7f.dyn.optonline.net.
|
0ms |
FB:10:20:44:0A:F2:1C:57:35:EC:22:8B:2B:19:AE:9B:B1:18:39:98:4B:D0:A6:4F:7D:06:B2:54:63:F0:7D:E1
How does the propagation check work for sun.mnode.net? →
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.