DNS & SSL for bhs.researchchemhq.co
Last probed 1 hour ago. Use "re-check now" to refresh.
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
usb.stape.io.
34.72.150.108
|
0ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
usb.stape.io.
34.72.150.108
|
0ms |
| [OK] | 8.8.8.8 |
usb.stape.io.
34.72.150.108
|
0ms | |
| [OK] | Google 2 | 8.8.4.4 |
usb.stape.io.
34.72.150.108
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
usb.stape.io.
34.72.150.108
|
0ms |
| [OK] | OpenDNS | 208.67.222.222 |
usb.stape.io.
34.72.150.108
|
0ms |
| [OK] | DNS.Watch | 84.200.69.80 |
;; communications error to 84.200.69.80#53: timed out
;; no servers could be reached
|
2938ms |
| [OK] | Yandex | 77.88.8.8 |
usb.stape.io.
34.72.150.108
|
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 |
usb.stape.io.
34.72.150.108
|
0ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
usb.stape.io.
34.72.150.108
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
usb.stape.io.
34.72.150.108
|
0ms |
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
usb.stape.io.
2600:1900:4001:323:8000::
|
0ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
usb.stape.io.
2600:1900:4001:323:8000::
|
0ms |
| [OK] | 8.8.8.8 |
usb.stape.io.
2600:1900:4001:323:8000::
|
0ms | |
| [OK] | Google 2 | 8.8.4.4 |
usb.stape.io.
2600:1900:4001:323:8000::
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
usb.stape.io.
2600:1900:4001:323:8000::
|
0ms |
| [OK] | OpenDNS | 208.67.222.222 |
usb.stape.io.
2600:1900:4001:323:8000::
|
0ms |
| [OK] | DNS.Watch | 84.200.69.80 |
;; communications error to 84.200.69.80#53: timed out
;; no servers could be reached
|
6ms |
| [OK] | Yandex | 77.88.8.8 |
usb.stape.io.
2600:1900:4001:323:8000::
|
0ms |
| [OK] | Comodo | 8.26.56.26 |
;; communications error to 8.26.56.26#53: timed out
;; no servers could be reached
|
3ms |
| [OK] | Verisign | 64.6.64.6 |
usb.stape.io.
2600:1900:4001:323:8000::
|
0ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
usb.stape.io.
2600:1900:4001:323:8000::
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
usb.stape.io.
2600:1900:4001:323:8000::
|
0ms |
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
usb.stape.io.
|
0ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
usb.stape.io.
|
0ms |
| [OK] | 8.8.8.8 |
usb.stape.io.
|
0ms | |
| [OK] | Google 2 | 8.8.4.4 |
usb.stape.io.
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
usb.stape.io.
|
0ms |
| [OK] | OpenDNS | 208.67.222.222 |
usb.stape.io.
|
0ms |
| [OK] | DNS.Watch | 84.200.69.80 |
;; communications error to 84.200.69.80#53: timed out
;; no servers could be reached
|
8ms |
| [OK] | Yandex | 77.88.8.8 |
usb.stape.io.
|
0ms |
| [OK] | Comodo | 8.26.56.26 |
usb.stape.io.
|
0ms |
| [OK] | Verisign | 64.6.64.6 |
usb.stape.io.
|
0ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
usb.stape.io.
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
usb.stape.io.
|
0ms |
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
usb.stape.io.
|
0ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
usb.stape.io.
|
0ms |
| [OK] | 8.8.8.8 |
usb.stape.io.
|
0ms | |
| [OK] | Google 2 | 8.8.4.4 |
usb.stape.io.
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
usb.stape.io.
|
0ms |
| [OK] | OpenDNS | 208.67.222.222 |
usb.stape.io.
|
0ms |
| [OK] | DNS.Watch | 84.200.69.80 |
;; communications error to 84.200.69.80#53: timed out
;; no servers could be reached
|
13ms |
| [OK] | Yandex | 77.88.8.8 |
usb.stape.io.
|
0ms |
| [OK] | Comodo | 8.26.56.26 |
;; communications error to 8.26.56.26#53: timed out
;; no servers could be reached
|
5ms |
| [OK] | Verisign | 64.6.64.6 |
usb.stape.io.
|
0ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
usb.stape.io.
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
usb.stape.io.
|
0ms |
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
usb.stape.io.
|
0ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
usb.stape.io.
|
0ms |
| [OK] | 8.8.8.8 |
usb.stape.io.
|
0ms | |
| [OK] | Google 2 | 8.8.4.4 |
usb.stape.io.
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
usb.stape.io.
|
0ms |
| [OK] | OpenDNS | 208.67.222.222 |
usb.stape.io.
|
0ms |
| [OK] | DNS.Watch | 84.200.69.80 |
usb.stape.io.
|
0ms |
| [OK] | Yandex | 77.88.8.8 |
usb.stape.io.
|
0ms |
| [OK] | Comodo | 8.26.56.26 |
;; communications error to 8.26.56.26#53: timed out
;; no servers could be reached
|
13ms |
| [OK] | Verisign | 64.6.64.6 |
usb.stape.io.
|
0ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
usb.stape.io.
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
usb.stape.io.
|
0ms |
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
usb.stape.io.
|
0ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
usb.stape.io.
|
0ms |
| [OK] | 8.8.8.8 |
usb.stape.io.
|
0ms | |
| [OK] | Google 2 | 8.8.4.4 |
usb.stape.io.
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
usb.stape.io.
|
0ms |
| [OK] | OpenDNS | 208.67.222.222 |
usb.stape.io.
|
0ms |
| [OK] | DNS.Watch | 84.200.69.80 |
usb.stape.io.
|
0ms |
| [OK] | Yandex | 77.88.8.8 |
usb.stape.io.
|
0ms |
| [OK] | Comodo | 8.26.56.26 |
usb.stape.io.
|
0ms |
| [OK] | Verisign | 64.6.64.6 |
usb.stape.io.
|
0ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
usb.stape.io.
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
usb.stape.io.
|
0ms |
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
usb.stape.io.
|
0ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
usb.stape.io.
|
0ms |
| [OK] | 8.8.8.8 |
usb.stape.io.
|
0ms | |
| [OK] | Google 2 | 8.8.4.4 |
usb.stape.io.
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
usb.stape.io.
|
0ms |
| [OK] | OpenDNS | 208.67.222.222 |
usb.stape.io.
|
0ms |
| [OK] | DNS.Watch | 84.200.69.80 |
usb.stape.io.
|
0ms |
| [OK] | Yandex | 77.88.8.8 |
usb.stape.io.
|
0ms |
| [OK] | Comodo | 8.26.56.26 |
;; communications error to 8.26.56.26#53: timed out
;; no servers could be reached
|
20ms |
| [OK] | Verisign | 64.6.64.6 |
usb.stape.io.
|
0ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
usb.stape.io.
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
usb.stape.io.
|
0ms |
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
usb.stape.io.
|
0ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
usb.stape.io.
|
0ms |
| [OK] | 8.8.8.8 |
usb.stape.io.
|
0ms | |
| [OK] | Google 2 | 8.8.4.4 |
usb.stape.io.
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
usb.stape.io.
|
0ms |
| [OK] | OpenDNS | 208.67.222.222 |
usb.stape.io.
|
0ms |
| [OK] | DNS.Watch | 84.200.69.80 |
;; communications error to 84.200.69.80#53: timed out
;; no servers could be reached
|
12ms |
| [OK] | Yandex | 77.88.8.8 |
usb.stape.io.
|
0ms |
| [OK] | Comodo | 8.26.56.26 |
usb.stape.io.
|
0ms |
| [OK] | Verisign | 64.6.64.6 |
usb.stape.io.
|
0ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
usb.stape.io.
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
usb.stape.io.
|
0ms |
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [--] | Cloudflare | 1.1.1.1 | — no answer | 15ms |
| [--] | 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 | 1ms |
| [--] | OpenDNS | 208.67.222.222 | — no answer | 0ms |
| [--] | DNS.Watch | 84.200.69.80 | — no answer | 3ms |
| [--] | Yandex | 77.88.8.8 | — no answer | 1ms |
| [--] | Comodo | 8.26.56.26 | — no answer | 1ms |
| [--] | Verisign | 64.6.64.6 | — no answer | 0ms |
| [--] | Hurricane Electric | 74.82.42.42 | — no answer | 2ms |
| [--] | AdGuard | 94.140.14.14 | — no answer | 0ms |
BD:4D:CC:8C:7E:86:72:82:34:AD:8B:D6:6C:DB:23:E4:99:D9:F7:8C:A4:82:11:E9:24:A1:17:11:5D:DD:01:9A
How does the propagation check work for bhs.researchchemhq.co? →
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.