cached probe / public landing
DNS & SSL for bhs.researchchemhq.com
Last probed 1 hour ago. Use "re-check now" to refresh.
probe.2026081318
probe result
/
bhs.researchchemhq.com
cached 1 hour ago
· 5107ms
A
record
[WARN] partial
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
researchchemhq.com.
67.227.156.148
|
0ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
researchchemhq.com.
67.227.156.148
|
0ms |
| [OK] | 8.8.8.8 |
researchchemhq.com.
67.227.156.148
|
0ms | |
| [OK] | Google 2 | 8.8.4.4 |
researchchemhq.com.
67.227.156.148
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
researchchemhq.com.
67.227.156.148
|
2341ms |
| [OK] | OpenDNS | 208.67.222.222 |
researchchemhq.com.
67.227.156.148
|
0ms |
| [OK] | DNS.Watch | 84.200.69.80 |
;; communications error to 84.200.69.80#53: timed out
;; no servers could be reached
|
585ms |
| [OK] | Yandex | 77.88.8.8 |
researchchemhq.com.
67.227.156.148
|
0ms |
| [OK] | Comodo | 8.26.56.26 |
researchchemhq.com.
67.227.156.148
|
0ms |
| [OK] | Verisign | 64.6.64.6 |
researchchemhq.com.
67.227.156.148
|
0ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
researchchemhq.com.
67.227.156.148
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
researchchemhq.com.
67.227.156.148
|
0ms |
AAAA
record
[WARN] partial
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
researchchemhq.com.
|
0ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
researchchemhq.com.
|
0ms |
| [OK] | 8.8.8.8 |
researchchemhq.com.
|
0ms | |
| [OK] | Google 2 | 8.8.4.4 |
researchchemhq.com.
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
researchchemhq.com.
|
0ms |
| [OK] | OpenDNS | 208.67.222.222 |
researchchemhq.com.
|
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 |
researchchemhq.com.
|
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 |
researchchemhq.com.
|
0ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
researchchemhq.com.
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
researchchemhq.com.
|
0ms |
MX
record
[WARN] partial
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
researchchemhq.com.
0 researchchemhq-com.mail.protection.outlook.com.
|
0ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
researchchemhq.com.
0 researchchemhq-com.mail.protection.outlook.com.
|
0ms |
| [OK] | 8.8.8.8 |
researchchemhq.com.
0 researchchemhq-com.mail.protection.outlook.com.
|
0ms | |
| [OK] | Google 2 | 8.8.4.4 |
researchchemhq.com.
0 researchchemhq-com.mail.protection.outlook.com.
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
researchchemhq.com.
0 researchchemhq-com.mail.protection.outlook.com.
|
0ms |
| [OK] | OpenDNS | 208.67.222.222 |
researchchemhq.com.
0 researchchemhq-com.mail.protection.outlook.com.
|
0ms |
| [OK] | DNS.Watch | 84.200.69.80 |
;; communications error to 84.200.69.80#53: timed out
;; no servers could be reached
|
11ms |
| [OK] | Yandex | 77.88.8.8 |
researchchemhq.com.
0 researchchemhq-com.mail.protection.outlook.com.
|
0ms |
| [OK] | Comodo | 8.26.56.26 |
researchchemhq.com.
0 researchchemhq-com.mail.protection.outlook.com.
|
0ms |
| [OK] | Verisign | 64.6.64.6 |
researchchemhq.com.
0 researchchemhq-com.mail.protection.outlook.com.
|
0ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
researchchemhq.com.
0 researchchemhq-com.mail.protection.outlook.com.
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
researchchemhq.com.
0 researchchemhq-com.mail.protection.outlook.com.
|
0ms |
TXT
record
[OK] propagated
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
researchchemhq.com.
"NETORGFT15737128.onmicrosoft.com"
" v=spf1 include:secureserver.net -all"
|
0ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
researchchemhq.com.
"NETORGFT15737128.onmicrosoft.com"
" v=spf1 include:secureserver.net -all"
|
0ms |
| [OK] | 8.8.8.8 |
researchchemhq.com.
"NETORGFT15737128.onmicrosoft.com"
" v=spf1 include:secureserver.net -all"
|
0ms | |
| [OK] | Google 2 | 8.8.4.4 |
researchchemhq.com.
" v=spf1 include:secureserver.net -all"
"NETORGFT15737128.onmicrosoft.com"
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
researchchemhq.com.
" v=spf1 include:secureserver.net -all"
"NETORGFT15737128.onmicrosoft.com"
|
0ms |
| [OK] | OpenDNS | 208.67.222.222 |
researchchemhq.com.
"NETORGFT15737128.onmicrosoft.com"
" v=spf1 include:secureserver.net -all"
|
0ms |
| [OK] | DNS.Watch | 84.200.69.80 |
researchchemhq.com.
" v=spf1 include:secureserver.net -all"
"NETORGFT15737128.onmicrosoft.com"
|
0ms |
| [OK] | Yandex | 77.88.8.8 |
researchchemhq.com.
" v=spf1 include:secureserver.net -all"
"NETORGFT15737128.onmicrosoft.com"
|
0ms |
| [OK] | Comodo | 8.26.56.26 |
researchchemhq.com.
" v=spf1 include:secureserver.net -all"
"NETORGFT15737128.onmicrosoft.com"
|
0ms |
| [OK] | Verisign | 64.6.64.6 |
researchchemhq.com.
"NETORGFT15737128.onmicrosoft.com"
" v=spf1 include:secureserver.net -all"
|
0ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
researchchemhq.com.
" v=spf1 include:secureserver.net -all"
"NETORGFT15737128.onmicrosoft.com"
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
researchchemhq.com.
" v=spf1 include:secureserver.net -all"
"NETORGFT15737128.onmicrosoft.com"
|
0ms |
NS
record
[WARN] partial
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
researchchemhq.com.
ns1.liquidweb.com.
ns.liquidweb.com.
|
0ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
researchchemhq.com.
ns1.liquidweb.com.
ns.liquidweb.com.
|
0ms |
| [OK] | 8.8.8.8 |
researchchemhq.com.
ns1.liquidweb.com.
ns.liquidweb.com.
|
0ms | |
| [OK] | Google 2 | 8.8.4.4 |
researchchemhq.com.
ns1.liquidweb.com.
ns.liquidweb.com.
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
researchchemhq.com.
ns1.liquidweb.com.
ns.liquidweb.com.
|
0ms |
| [OK] | OpenDNS | 208.67.222.222 |
researchchemhq.com.
ns.liquidweb.com.
ns1.liquidweb.com.
|
0ms |
| [OK] | DNS.Watch | 84.200.69.80 |
;; communications error to 84.200.69.80#53: timed out
;; no servers could be reached
|
32ms |
| [OK] | Yandex | 77.88.8.8 |
researchchemhq.com.
ns.liquidweb.com.
ns1.liquidweb.com.
|
0ms |
| [OK] | Comodo | 8.26.56.26 |
researchchemhq.com.
ns1.liquidweb.com.
ns.liquidweb.com.
|
0ms |
| [OK] | Verisign | 64.6.64.6 |
researchchemhq.com.
ns1.liquidweb.com.
ns.liquidweb.com.
|
0ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
researchchemhq.com.
ns1.liquidweb.com.
ns.liquidweb.com.
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
researchchemhq.com.
ns1.liquidweb.com.
ns.liquidweb.com.
|
0ms |
CNAME
record
[WARN] partial
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
researchchemhq.com.
|
0ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
researchchemhq.com.
|
0ms |
| [OK] | 8.8.8.8 |
researchchemhq.com.
|
0ms | |
| [OK] | Google 2 | 8.8.4.4 |
researchchemhq.com.
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
researchchemhq.com.
|
0ms |
| [OK] | OpenDNS | 208.67.222.222 |
researchchemhq.com.
|
0ms |
| [OK] | DNS.Watch | 84.200.69.80 |
;; communications error to 84.200.69.80#53: timed out
;; no servers could be reached
|
16ms |
| [OK] | Yandex | 77.88.8.8 |
researchchemhq.com.
|
0ms |
| [OK] | Comodo | 8.26.56.26 |
researchchemhq.com.
|
0ms |
| [OK] | Verisign | 64.6.64.6 |
researchchemhq.com.
|
0ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
researchchemhq.com.
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
researchchemhq.com.
|
0ms |
CAA
record
[WARN] partial
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
researchchemhq.com.
|
0ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
researchchemhq.com.
|
0ms |
| [OK] | 8.8.8.8 |
researchchemhq.com.
|
0ms | |
| [OK] | Google 2 | 8.8.4.4 |
researchchemhq.com.
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
researchchemhq.com.
|
0ms |
| [OK] | OpenDNS | 208.67.222.222 |
researchchemhq.com.
|
0ms |
| [OK] | DNS.Watch | 84.200.69.80 |
researchchemhq.com.
|
0ms |
| [OK] | Yandex | 77.88.8.8 |
researchchemhq.com.
|
0ms |
| [OK] | Comodo | 8.26.56.26 |
;; communications error to 8.26.56.26#53: timed out
;; no servers could be reached
|
8ms |
| [OK] | Verisign | 64.6.64.6 |
researchchemhq.com.
|
0ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
researchchemhq.com.
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
researchchemhq.com.
|
0ms |
SOA
record
[WARN] partial
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
researchchemhq.com.
ns.liquidweb.com. admin.liquidweb.com. 2024100616 86400 7200 3600000 14400
|
0ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
researchchemhq.com.
ns.liquidweb.com. admin.liquidweb.com. 2024100616 86400 7200 3600000 14400
|
0ms |
| [OK] | 8.8.8.8 |
researchchemhq.com.
ns.liquidweb.com. admin.liquidweb.com. 2024100616 86400 7200 3600000 14400
|
0ms | |
| [OK] | Google 2 | 8.8.4.4 |
researchchemhq.com.
ns.liquidweb.com. admin.liquidweb.com. 2024100616 86400 7200 3600000 14400
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
researchchemhq.com.
ns.liquidweb.com. admin.liquidweb.com. 2024100616 86400 7200 3600000 14400
|
0ms |
| [OK] | OpenDNS | 208.67.222.222 |
researchchemhq.com.
ns.liquidweb.com. admin.liquidweb.com. 2024100616 86400 7200 3600000 14400
|
0ms |
| [OK] | DNS.Watch | 84.200.69.80 |
;; communications error to 84.200.69.80#53: timed out
;; no servers could be reached
|
11ms |
| [OK] | Yandex | 77.88.8.8 |
researchchemhq.com.
ns.liquidweb.com. admin.liquidweb.com. 2024100616 86400 7200 3600000 14400
|
0ms |
| [OK] | Comodo | 8.26.56.26 |
;; communications error to 8.26.56.26#53: timed out
;; no servers could be reached
|
2ms |
| [OK] | Verisign | 64.6.64.6 |
researchchemhq.com.
ns.liquidweb.com. admin.liquidweb.com. 2024100616 86400 7200 3600000 14400
|
0ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
researchchemhq.com.
ns.liquidweb.com. admin.liquidweb.com. 2024100616 86400 7200 3600000 14400
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
researchchemhq.com.
ns.liquidweb.com. admin.liquidweb.com. 2024100616 86400 7200 3600000 14400
|
0ms |
PTR
record
[FAIL] missing
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [--] | Cloudflare | 1.1.1.1 | — no answer | 15ms |
| [--] | Cloudflare 2 | 1.0.0.1 | — no answer | 1ms |
| [--] | 8.8.8.8 | — no answer | 0ms | |
| [--] | Google 2 | 8.8.4.4 | — no answer | 0ms |
| [--] | Quad9 | 9.9.9.9 | — no answer | 2ms |
| [--] | OpenDNS | 208.67.222.222 | — no answer | 0ms |
| [--] | DNS.Watch | 84.200.69.80 | — no answer | 0ms |
| [--] | Yandex | 77.88.8.8 | — no answer | 3ms |
| [--] | Comodo | 8.26.56.26 | — no answer | 2ms |
| [--] | Verisign | 64.6.64.6 | — no answer | 0ms |
| [--] | Hurricane Electric | 74.82.42.42 | — no answer | 0ms |
| [--] | AdGuard | 94.140.14.14 | — no answer | 3ms |
TLS / SSL health
[OK] 47d left
issuer
C = US, O = Let's Encrypt, CN = YR1
subject
CN = webmail.researchchemhq.com
valid from
Jul 2 06:09:50 2026 GMT
valid to
Sep 30 06:09:49 2026 GMT
signature algorithm
sha256WithRSAEncryption
public key
rsaEncryption · 2048 bit
subject alternative names (22)
autoconfig.researchchemhq.co
autoconfig.researchchemhq.com
autodiscover.researchchemhq.co
autodiscover.researchchemhq.com
cpanel.researchchemhq.co
cpanel.researchchemhq.com
cpcalendars.researchchemhq.co
cpcalendars.researchchemhq.com
cpcontacts.researchchemhq.co
cpcontacts.researchchemhq.com
mail.researchchemhq.co
mail.researchchemhq.com
researchchemhq.co
researchchemhq.com
researchchemhq.com.researchchemhq.co
webdisk.researchchemhq.co
webdisk.researchchemhq.com
webmail.researchchemhq.co
webmail.researchchemhq.com
www.researchchemhq.co
www.researchchemhq.com
www.researchchemhq.com.researchchemhq.co
sha256 fingerprint
1E:B3:82:21:60:E5:D1:5D:0C:5B:A1:7E:80:45:91:1D:1F:14:C8:3B:C0:4C:B3:5F:8C:87:A7:D2:E1:95:E4:8A
TLS 1.0
[OK] disabled
TLS 1.1
[OK] disabled
TLS 1.2
[OK] supported
TLS 1.3
[--] no
HTTP/2
[OK] supported
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 / bhs.researchchemhq.com
How does the propagation check work for bhs.researchchemhq.com? →
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.