DNS & SSL for sexystepdad.app
Last probed 2 hours ago. Use "re-check now" to refresh.
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
185.111.111.156
|
0ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
185.111.111.157
|
0ms |
| [OK] | 8.8.8.8 |
185.111.111.158
|
0ms | |
| [OK] | Google 2 | 8.8.4.4 |
185.111.111.157
|
20ms |
| [OK] | Quad9 | 9.9.9.9 |
185.111.111.158
|
0ms |
| [OK] | OpenDNS | 208.67.222.222 |
185.111.111.154
|
0ms |
| [OK] | DNS.Watch | 84.200.69.80 |
185.111.111.155
|
0ms |
| [OK] | Yandex | 77.88.8.8 |
138.199.46.65
|
0ms |
| [OK] | Comodo | 8.26.56.26 |
185.111.111.155
|
0ms |
| [OK] | Verisign | 64.6.64.6 |
185.93.3.244
|
6ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
107.150.176.1
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
79.127.237.132
|
0ms |
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [--] | Cloudflare | 1.1.1.1 | — no answer | 0ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
2400:52e0:1e00:2::1329:1
|
0ms |
| [OK] | 8.8.8.8 |
2400:52e0:1e00:2::1330:1
|
0ms | |
| [OK] | Google 2 | 8.8.4.4 |
2400:52e0:1e00:2::1332:1
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
2400:52e0:1e00:2::1331:1
|
0ms |
| [OK] | OpenDNS | 208.67.222.222 |
2400:52e0:1e00:2::1330:1
|
0ms |
| [OK] | DNS.Watch | 84.200.69.80 |
2400:52e0:1e00:2::1328:1
|
0ms |
| [OK] | Yandex | 77.88.8.8 |
2400:52e0:1500::868:1
|
0ms |
| [OK] | Comodo | 8.26.56.26 |
2400:52e0:1e00:2::1330:1
|
0ms |
| [OK] | Verisign | 64.6.64.6 |
2400:52e0:1e06::1446:1
|
0ms |
| [--] | Hurricane Electric | 74.82.42.42 | — no answer | 0ms |
| [OK] | AdGuard | 94.140.14.14 |
2400:52e0:1e03::1205:1
|
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 | 51ms |
| [--] | 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 |
| [--] | 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 |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
kiki.bunny.net.
coco.bunny.net.
|
0ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
kiki.bunny.net.
coco.bunny.net.
|
0ms |
| [OK] | 8.8.8.8 |
coco.bunny.net.
kiki.bunny.net.
|
0ms | |
| [OK] | Google 2 | 8.8.4.4 |
coco.bunny.net.
kiki.bunny.net.
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
kiki.bunny.net.
coco.bunny.net.
|
0ms |
| [OK] | OpenDNS | 208.67.222.222 |
coco.bunny.net.
kiki.bunny.net.
|
0ms |
| [OK] | DNS.Watch | 84.200.69.80 |
coco.bunny.net.
kiki.bunny.net.
|
0ms |
| [OK] | Yandex | 77.88.8.8 |
kiki.bunny.net.
coco.bunny.net.
|
40ms |
| [OK] | Comodo | 8.26.56.26 |
kiki.bunny.net.
coco.bunny.net.
|
0ms |
| [OK] | Verisign | 64.6.64.6 |
kiki.bunny.net.
coco.bunny.net.
|
0ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
coco.bunny.net.
kiki.bunny.net.
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
coco.bunny.net.
kiki.bunny.net.
|
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 |
| [--] | 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 |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
kiki.bunny.net. hostmaster.bunny.net. 2022030928 7200 900 1209600 86400
|
0ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
kiki.bunny.net. hostmaster.bunny.net. 2022030928 7200 900 1209600 86400
|
0ms |
| [OK] | 8.8.8.8 |
kiki.bunny.net. hostmaster.bunny.net. 2022030928 7200 900 1209600 86400
|
0ms | |
| [OK] | Google 2 | 8.8.4.4 |
kiki.bunny.net. hostmaster.bunny.net. 2022030928 7200 900 1209600 86400
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
kiki.bunny.net. hostmaster.bunny.net. 2022030928 7200 900 1209600 86400
|
0ms |
| [OK] | OpenDNS | 208.67.222.222 |
kiki.bunny.net. hostmaster.bunny.net. 2022030928 7200 900 1209600 86400
|
0ms |
| [OK] | DNS.Watch | 84.200.69.80 |
kiki.bunny.net. hostmaster.bunny.net. 2022030928 7200 900 1209600 86400
|
0ms |
| [OK] | Yandex | 77.88.8.8 |
kiki.bunny.net. hostmaster.bunny.net. 2022030928 7200 900 1209600 86400
|
7ms |
| [OK] | Comodo | 8.26.56.26 |
kiki.bunny.net. hostmaster.bunny.net. 2022030928 7200 900 1209600 86400
|
0ms |
| [OK] | Verisign | 64.6.64.6 |
kiki.bunny.net. hostmaster.bunny.net. 2022030928 7200 900 1209600 86400
|
0ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
kiki.bunny.net. hostmaster.bunny.net. 2022030928 7200 900 1209600 86400
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
kiki.bunny.net. hostmaster.bunny.net. 2022030928 7200 900 1209600 86400
|
9ms |
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
185-111-111-156.bunnyinfra.net.
|
28ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
185-111-111-156.bunnyinfra.net.
|
0ms |
| [OK] | 8.8.8.8 |
185-111-111-156.bunnyinfra.net.
|
9ms | |
| [OK] | Google 2 | 8.8.4.4 |
185-111-111-156.bunnyinfra.net.
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
185-111-111-156.bunnyinfra.net.
|
2ms |
| [OK] | OpenDNS | 208.67.222.222 |
185-111-111-156.bunnyinfra.net.
|
36ms |
| [OK] | DNS.Watch | 84.200.69.80 |
;; communications error to 84.200.69.80#53: timed out
;; no servers could be reached
|
2959ms |
| [OK] | Yandex | 77.88.8.8 |
185-111-111-156.bunnyinfra.net.
|
0ms |
| [OK] | Comodo | 8.26.56.26 |
185-111-111-156.bunnyinfra.net.
|
0ms |
| [OK] | Verisign | 64.6.64.6 |
185-111-111-156.bunnyinfra.net.
|
0ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
185-111-111-156.bunnyinfra.net.
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
185-111-111-156.bunnyinfra.net.
|
0ms |
C6:90:A3:5C:BF:45:B9:17:96:23:9F:DE:0D:95:CE:05:0B:37:49:5A:B7:7E:87:8D:C4:5C:5C:A5:81:62:CC:75
How does the propagation check work for sexystepdad.app? →
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.