dnsprobe v1
cached probe / public landing

DNS & SSL for rbglaboratory.com

Last probed 20 hours ago. Use "re-check now" to refresh.

probe.2026100403
probe result / rbglaboratory.com cached 20 hours ago · 4544ms
rbglaboratory.com → · share:
A record [WARN] partial
STATUSRESOLVERIPVALUELATENCY
[OK] Cloudflare 1.1.1.1
216.198.79.1
2189ms
[OK] Cloudflare 2 1.0.0.1
216.198.79.1
0ms
[OK] Google 8.8.8.8
;; communications error to 8.8.8.8#53: timed out ;; no servers could be reached
728ms
[OK] Google 2 8.8.4.4
216.198.79.1 64.29.17.1
0ms
[OK] Quad9 9.9.9.9
;; communications error to 9.9.9.9#53: timed out ;; no servers could be reached
6ms
[OK] OpenDNS 208.67.222.222
;; communications error to 208.67.222.222#53: timed out ;; no servers could be reached
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
;; communications error to 77.88.8.8#53: timed out ;; no servers could be reached
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
;; communications error to 64.6.64.6#53: timed out ;; no servers could be reached
0ms
[OK] Hurricane Electric 74.82.42.42
;; communications error to 74.82.42.42#53: timed out ;; no servers could be reached
0ms
[OK] AdGuard 94.140.14.14
216.198.79.1
0ms
AAAA record [WARN] partial
STATUSRESOLVERIPVALUELATENCY
[--] Cloudflare 1.1.1.1 — no answer 0ms
[--] Cloudflare 2 1.0.0.1 — no answer 0ms
[OK] Google 8.8.8.8
;; communications error to 8.8.8.8#53: timed out ;; no servers could be reached
0ms
[--] Google 2 8.8.4.4 — no answer 0ms
[OK] Quad9 9.9.9.9
;; communications error to 9.9.9.9#53: timed out ;; no servers could be reached
0ms
[OK] OpenDNS 208.67.222.222
;; communications error to 208.67.222.222#53: timed out ;; no servers could be reached
0ms
[OK] DNS.Watch 84.200.69.80
;; communications error to 84.200.69.80#53: timed out ;; no servers could be reached
0ms
[OK] Yandex 77.88.8.8
;; communications error to 77.88.8.8#53: timed out ;; no servers could be reached
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
;; communications error to 64.6.64.6#53: timed out ;; no servers could be reached
0ms
[OK] Hurricane Electric 74.82.42.42
;; communications error to 74.82.42.42#53: timed out ;; no servers could be reached
3ms
[OK] AdGuard 94.140.14.14
;; communications error to 94.140.14.14#53: timed out ;; no servers could be reached
8ms
MX record [WARN] partial
STATUSRESOLVERIPVALUELATENCY
[OK] Cloudflare 1.1.1.1
0 rbglaboratory-com.mail.protection.outlook.com.
0ms
[OK] Cloudflare 2 1.0.0.1
0 rbglaboratory-com.mail.protection.outlook.com.
0ms
[OK] Google 8.8.8.8
0 rbglaboratory-com.mail.protection.outlook.com.
0ms
[OK] Google 2 8.8.4.4
0 rbglaboratory-com.mail.protection.outlook.com.
0ms
[OK] Quad9 9.9.9.9
0 rbglaboratory-com.mail.protection.outlook.com.
0ms
[OK] OpenDNS 208.67.222.222
;; communications error to 208.67.222.222#53: timed out ;; no servers could be reached
0ms
[OK] DNS.Watch 84.200.69.80
;; communications error to 84.200.69.80#53: timed out ;; no servers could be reached
0ms
[OK] Yandex 77.88.8.8
;; communications error to 77.88.8.8#53: timed out ;; no servers could be reached
3ms
[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
;; communications error to 64.6.64.6#53: timed out ;; no servers could be reached
0ms
[OK] Hurricane Electric 74.82.42.42
;; communications error to 74.82.42.42#53: timed out ;; no servers could be reached
6ms
[OK] AdGuard 94.140.14.14
;; communications error to 94.140.14.14#53: timed out ;; no servers could be reached
1ms
TXT record [WARN] partial
STATUSRESOLVERIPVALUELATENCY
[OK] Cloudflare 1.1.1.1
"v=spf1 ip4:148.113.20.237 ip4:168.119.142.170 include:spf.protection.outlook.com -all" "MS=ms73275167"
0ms
[OK] Cloudflare 2 1.0.0.1
"v=spf1 ip4:148.113.20.237 ip4:168.119.142.170 include:spf.protection.outlook.com -all" "MS=ms73275167"
0ms
[OK] Google 8.8.8.8
;; communications error to 8.8.8.8#53: timed out ;; no servers could be reached
0ms
[OK] Google 2 8.8.4.4
"MS=ms73275167" "v=spf1 ip4:148.113.20.237 ip4:168.119.142.170 include:spf.protection.outlook.com -all"
0ms
[OK] Quad9 9.9.9.9
;; communications error to 9.9.9.9#53: timed out ;; no servers could be reached
3ms
[OK] OpenDNS 208.67.222.222
;; communications error to 208.67.222.222#53: timed out ;; no servers could be reached
0ms
[OK] DNS.Watch 84.200.69.80
;; communications error to 84.200.69.80#53: timed out ;; no servers could be reached
0ms
[OK] Yandex 77.88.8.8
;; communications error to 77.88.8.8#53: timed out ;; no servers could be reached
3ms
[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
;; communications error to 64.6.64.6#53: timed out ;; no servers could be reached
3ms
[OK] Hurricane Electric 74.82.42.42
;; communications error to 74.82.42.42#53: timed out ;; no servers could be reached
0ms
[OK] AdGuard 94.140.14.14
"v=spf1 ip4:148.113.20.237 ip4:168.119.142.170 include:spf.protection.outlook.com -all" "MS=ms73275167"
0ms
NS record [WARN] partial
STATUSRESOLVERIPVALUELATENCY
[OK] Cloudflare 1.1.1.1
ns101.hostinservers.com. ns102.hostinservers.com. dns1.hostinservers.com. dns2.hostinservers.com.
0ms
[OK] Cloudflare 2 1.0.0.1
ns101.hostinservers.com. ns102.hostinservers.com. dns1.hostinservers.com. dns2.hostinservers.com.
0ms
[OK] Google 8.8.8.8
;; communications error to 8.8.8.8#53: timed out ;; no servers could be reached
4ms
[OK] Google 2 8.8.4.4
ns102.hostinservers.com. dns1.hostinservers.com. ns101.hostinservers.com. dns2.hostinservers.com.
0ms
[OK] Quad9 9.9.9.9
;; communications error to 9.9.9.9#53: timed out ;; no servers could be reached
1ms
[OK] OpenDNS 208.67.222.222
;; communications error to 208.67.222.222#53: timed out ;; no servers could be reached
0ms
[OK] DNS.Watch 84.200.69.80
;; communications error to 84.200.69.80#53: timed out ;; no servers could be reached
5ms
[OK] Yandex 77.88.8.8
;; communications error to 77.88.8.8#53: timed out ;; no servers could be reached
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
ns102.hostinservers.com. ns101.hostinservers.com. dns2.hostinservers.com. dns1.hostinservers.com.
0ms
[OK] Hurricane Electric 74.82.42.42
;; communications error to 74.82.42.42#53: timed out ;; no servers could be reached
3ms
[OK] AdGuard 94.140.14.14
;; communications error to 94.140.14.14#53: timed out ;; no servers could be reached
0ms
CNAME record [WARN] partial
STATUSRESOLVERIPVALUELATENCY
[--] Cloudflare 1.1.1.1 — no answer 0ms
[--] Cloudflare 2 1.0.0.1 — no answer 0ms
[OK] Google 8.8.8.8
;; communications error to 8.8.8.8#53: timed out ;; no servers could be reached
0ms
[OK] Google 2 8.8.4.4
;; communications error to 8.8.4.4#53: timed out ;; no servers could be reached
0ms
[OK] Quad9 9.9.9.9
;; communications error to 9.9.9.9#53: timed out ;; no servers could be reached
1ms
[OK] OpenDNS 208.67.222.222
;; communications error to 208.67.222.222#53: timed out ;; no servers could be reached
0ms
[OK] DNS.Watch 84.200.69.80
;; communications error to 84.200.69.80#53: timed out ;; no servers could be reached
3ms
[OK] Yandex 77.88.8.8
;; communications error to 77.88.8.8#53: timed out ;; no servers could be reached
4ms
[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
[OK] Hurricane Electric 74.82.42.42
;; communications error to 74.82.42.42#53: timed out ;; no servers could be reached
6ms
[OK] AdGuard 94.140.14.14
;; communications error to 94.140.14.14#53: timed out ;; no servers could be reached
0ms
CAA record [WARN] partial
STATUSRESOLVERIPVALUELATENCY
[--] Cloudflare 1.1.1.1 — no answer 0ms
[--] Cloudflare 2 1.0.0.1 — no answer 0ms
[--] Google 8.8.8.8 — no answer 0ms
[--] Google 2 8.8.4.4 — no answer 0ms
[--] Quad9 9.9.9.9 — no answer 0ms
[OK] OpenDNS 208.67.222.222
;; communications error to 208.67.222.222#53: timed out ;; no servers could be reached
3ms
[OK] DNS.Watch 84.200.69.80
;; communications error to 84.200.69.80#53: timed out ;; no servers could be reached
0ms
[OK] Yandex 77.88.8.8
;; communications error to 77.88.8.8#53: timed out ;; no servers could be reached
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
;; communications error to 64.6.64.6#53: timed out ;; no servers could be reached
4ms
[OK] Hurricane Electric 74.82.42.42
;; communications error to 74.82.42.42#53: timed out ;; no servers could be reached
0ms
[OK] AdGuard 94.140.14.14
;; communications error to 94.140.14.14#53: timed out ;; no servers could be reached
0ms
SOA record [WARN] partial
STATUSRESOLVERIPVALUELATENCY
[OK] Cloudflare 1.1.1.1
dns1.hostinservers.com. root.kitemum.hostinservers.com. 2026092914 3600 1800 1209600 86400
0ms
[OK] Cloudflare 2 1.0.0.1
dns1.hostinservers.com. root.kitemum.hostinservers.com. 2026092914 3600 1800 1209600 86400
0ms
[OK] Google 8.8.8.8
dns1.hostinservers.com. root.kitemum.hostinservers.com. 2026092914 3600 1800 1209600 86400
0ms
[OK] Google 2 8.8.4.4
dns1.hostinservers.com. root.kitemum.hostinservers.com. 2026092914 3600 1800 1209600 86400
0ms
[OK] Quad9 9.9.9.9
dns1.hostinservers.com. root.kitemum.hostinservers.com. 2026092914 3600 1800 1209600 86400
0ms
[OK] OpenDNS 208.67.222.222
;; communications error to 208.67.222.222#53: timed out ;; no servers could be reached
0ms
[OK] DNS.Watch 84.200.69.80
;; communications error to 84.200.69.80#53: timed out ;; no servers could be reached
0ms
[OK] Yandex 77.88.8.8
;; communications error to 77.88.8.8#53: timed out ;; no servers could be reached
1ms
[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
;; communications error to 64.6.64.6#53: timed out ;; no servers could be reached
8ms
[OK] Hurricane Electric 74.82.42.42
;; communications error to 74.82.42.42#53: timed out ;; no servers could be reached
0ms
[OK] AdGuard 94.140.14.14
;; communications error to 94.140.14.14#53: timed out ;; no servers could be reached
0ms
PTR record [FAIL] missing
STATUSRESOLVERIPVALUELATENCY
[--] Cloudflare 1.1.1.1 — no answer 40ms
[--] Cloudflare 2 1.0.0.1 — no answer 0ms
[--] Google 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 1ms
[--] DNS.Watch 84.200.69.80 — no answer 28ms
[--] Yandex 77.88.8.8 — no answer 33ms
[--] Comodo 8.26.56.26 — no answer 46ms
[--] 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
TLS / SSL health [OK] 63d left
issuer
C = US, O = Let's Encrypt, CN = YR2
subject
CN = *.rbglaboratory.com
valid from
Sep 7 06:54:52 2026 GMT
valid to
Dec 6 06:54:51 2026 GMT
signature algorithm
sha256WithRSAEncryption
public key
rsaEncryption · 2048 bit
subject alternative names (3)
*.rbglaboratory.com rbglaboratory.com www.new.rbglaboratory.com
sha256 fingerprint
C4:DC:67:DA:BB:81:91:44:1F:DE:28:9F:00:6A:BF:32:71:0E:02:63:79:64:79:6B:12:27:52:96:8F:66:A3:F2
TLS 1.0
[OK] disabled
TLS 1.1
[OK] disabled
TLS 1.2
[OK] supported
TLS 1.3
[OK] supported
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 / rbglaboratory.com
How does the propagation check work for rbglaboratory.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.