dnsprobe v1
cached probe / public landing

DNS & SSL for ahtbzy.com

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

probe.2026082705
probe result / ahtbzy.com cached 2 hours ago · 7411ms
ahtbzy.com → · share:
A record [WARN] partial
STATUSRESOLVERIPVALUELATENCY
[OK] Cloudflare 1.1.1.1
183.136.138.174
257ms
[OK] Cloudflare 2 1.0.0.1
183.136.138.174
0ms
[OK] Google 8.8.8.8
183.136.138.174
0ms
[OK] Google 2 8.8.4.4
183.136.138.174
0ms
[OK] Quad9 9.9.9.9
183.136.138.174
0ms
[OK] OpenDNS 208.67.222.222
183.136.138.174
0ms
[OK] DNS.Watch 84.200.69.80
;; communications error to 84.200.69.80#53: timed out ;; no servers could be reached
2674ms
[OK] Yandex 77.88.8.8
183.136.138.174
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
183.136.138.174
0ms
[OK] Hurricane Electric 74.82.42.42
183.136.138.174
0ms
[OK] AdGuard 94.140.14.14
183.136.138.174
0ms
AAAA 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
[--] 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
7ms
[--] 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
MX 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
[--] 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
[OK] Comodo 8.26.56.26
;; communications error to 8.26.56.26#53: timed out ;; no servers could be reached
11ms
[--] 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
TXT 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
[--] 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
21ms
[--] 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
5ms
[--] 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
NS record [WARN] partial
STATUSRESOLVERIPVALUELATENCY
[OK] Cloudflare 1.1.1.1
ns1.julydns.com. ns2.julydns.com.
0ms
[OK] Cloudflare 2 1.0.0.1
ns1.julydns.com. ns2.julydns.com.
0ms
[OK] Google 8.8.8.8
ns1.julydns.com. ns2.julydns.com.
0ms
[OK] Google 2 8.8.4.4
ns1.julydns.com. ns2.julydns.com.
0ms
[OK] Quad9 9.9.9.9
ns2.julydns.com. ns1.julydns.com.
0ms
[OK] OpenDNS 208.67.222.222
ns1.julydns.com. ns2.julydns.com.
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
ns1.julydns.com. ns2.julydns.com.
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
ns1.julydns.com. ns2.julydns.com.
0ms
[OK] Hurricane Electric 74.82.42.42
ns1.julydns.com. ns2.julydns.com.
0ms
[OK] AdGuard 94.140.14.14
ns1.julydns.com. ns2.julydns.com.
0ms
CNAME 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
[--] 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
1ms
[--] 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
8ms
[--] 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
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
[--] 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
0ms
[--] 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
11ms
[--] 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
SOA record [WARN] partial
STATUSRESOLVERIPVALUELATENCY
[OK] Cloudflare 1.1.1.1
ns1.julydns.com. master.jmdns.com. 1774087901 3600 1200 86400 600
0ms
[OK] Cloudflare 2 1.0.0.1
ns1.julydns.com. master.jmdns.com. 1774087901 3600 1200 86400 600
0ms
[OK] Google 8.8.8.8
ns1.julydns.com. master.jmdns.com. 1774087901 3600 1200 86400 600
0ms
[OK] Google 2 8.8.4.4
ns1.julydns.com. master.jmdns.com. 1774087901 3600 1200 86400 600
0ms
[OK] Quad9 9.9.9.9
ns1.julydns.com. master.jmdns.com. 1774087901 3600 1200 86400 600
0ms
[OK] OpenDNS 208.67.222.222
ns1.julydns.com. master.jmdns.com. 1774087901 3600 1200 86400 600
0ms
[OK] DNS.Watch 84.200.69.80
ns1.julydns.com. master.jmdns.com. 1774087901 3600 1200 86400 600
0ms
[OK] Yandex 77.88.8.8
ns1.julydns.com. master.jmdns.com. 1774087901 3600 1200 86400 600
0ms
[OK] Comodo 8.26.56.26
;; communications error to 8.26.56.26#53: timed out ;; no servers could be reached
1ms
[OK] Verisign 64.6.64.6
ns1.julydns.com. master.jmdns.com. 1774087901 3600 1200 86400 600
0ms
[OK] Hurricane Electric 74.82.42.42
ns1.julydns.com. master.jmdns.com. 1774087901 3600 1200 86400 600
0ms
[OK] AdGuard 94.140.14.14
ns1.julydns.com. master.jmdns.com. 1774087901 3600 1200 86400 600
0ms
PTR record [WARN] partial
STATUSRESOLVERIPVALUELATENCY
[--] Cloudflare 1.1.1.1 — no answer 1893ms
[--] 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 594ms
[--] 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
542ms
[--] 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
9ms
[--] Verisign 64.6.64.6 — no answer 0ms
[--] Hurricane Electric 74.82.42.42 — no answer 0ms
[OK] AdGuard 94.140.14.14
;; communications error to 94.140.14.14#53: timed out ;; no servers could be reached
0ms
TLS / SSL health [OK] 52d left
issuer
C = US, O = Let's Encrypt, CN = YR1
subject
CN = ahtbzy.com
valid from
Jul 20 08:21:35 2026 GMT
valid to
Oct 18 08:21:34 2026 GMT
signature algorithm
sha256WithRSAEncryption
public key
rsaEncryption · 2048 bit
subject alternative names (3)
ahtbzy.com m.ahtbzy.com www.ahtbzy.com
sha256 fingerprint
64:D4:D7:85:96:A4:86:EA:40:74:5B:55:1C:8A:8D:22:79:00:34:E7:98:F1:5D:27:48:5B:41:1F:2C:24:A8:EE
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 / ahtbzy.com
How does the propagation check work for ahtbzy.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.