dnsprobe v1
cached probe / public landing

DNS & SSL for ajolote.com.ar

Result is fresh (cached within the last hour).

probe.2026101608
probe result / ajolote.com.ar cached 0 seconds ago · 7256ms
ajolote.com.ar → · share:
A record [WARN] partial
STATUSRESOLVERIPVALUELATENCY
[OK] Cloudflare 1.1.1.1
179.36.249.185
0ms
[OK] Cloudflare 2 1.0.0.1
179.36.249.185
0ms
[OK] Google 8.8.8.8
179.36.249.185
0ms
[OK] Google 2 8.8.4.4
179.36.249.185
0ms
[OK] Quad9 9.9.9.9
179.36.249.185
0ms
[OK] OpenDNS 208.67.222.222
179.36.249.185
0ms
[OK] DNS.Watch 84.200.69.80
;; communications error to 84.200.69.80#53: timed out ;; no servers could be reached
2923ms
[OK] Yandex 77.88.8.8
179.36.249.185
0ms
[OK] Comodo 8.26.56.26
179.36.249.185
0ms
[OK] Verisign 64.6.64.6
179.36.249.185
0ms
[OK] Hurricane Electric 74.82.42.42
179.36.249.185
0ms
[OK] AdGuard 94.140.14.14
179.36.249.185
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
8ms
[--] 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 [FAIL] missing
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
[--] 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
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
33ms
[--] 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
NS record [WARN] partial
STATUSRESOLVERIPVALUELATENCY
[OK] Cloudflare 1.1.1.1
lindsey.ns.cloudflare.com. mitchell.ns.cloudflare.com.
0ms
[OK] Cloudflare 2 1.0.0.1
lindsey.ns.cloudflare.com. mitchell.ns.cloudflare.com.
0ms
[OK] Google 8.8.8.8
mitchell.ns.cloudflare.com. lindsey.ns.cloudflare.com.
0ms
[OK] Google 2 8.8.4.4
mitchell.ns.cloudflare.com. lindsey.ns.cloudflare.com.
0ms
[OK] Quad9 9.9.9.9
lindsey.ns.cloudflare.com. mitchell.ns.cloudflare.com.
0ms
[OK] OpenDNS 208.67.222.222
lindsey.ns.cloudflare.com. mitchell.ns.cloudflare.com.
0ms
[OK] DNS.Watch 84.200.69.80
;; communications error to 84.200.69.80#53: timed out ;; no servers could be reached
10ms
[OK] Yandex 77.88.8.8
lindsey.ns.cloudflare.com. mitchell.ns.cloudflare.com.
0ms
[OK] Comodo 8.26.56.26
mitchell.ns.cloudflare.com. lindsey.ns.cloudflare.com.
0ms
[OK] Verisign 64.6.64.6
lindsey.ns.cloudflare.com. mitchell.ns.cloudflare.com.
0ms
[OK] Hurricane Electric 74.82.42.42
mitchell.ns.cloudflare.com. lindsey.ns.cloudflare.com.
0ms
[OK] AdGuard 94.140.14.14
lindsey.ns.cloudflare.com. mitchell.ns.cloudflare.com.
0ms
CNAME record [FAIL] missing
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
[--] 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
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
31ms
[--] 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
SOA record [WARN] partial
STATUSRESOLVERIPVALUELATENCY
[OK] Cloudflare 1.1.1.1
lindsey.ns.cloudflare.com. dns.cloudflare.com. 2417435262 10000 2400 604800 1800
0ms
[OK] Cloudflare 2 1.0.0.1
lindsey.ns.cloudflare.com. dns.cloudflare.com. 2417435262 10000 2400 604800 1800
0ms
[OK] Google 8.8.8.8
lindsey.ns.cloudflare.com. dns.cloudflare.com. 2417435262 10000 2400 604800 1800
0ms
[OK] Google 2 8.8.4.4
lindsey.ns.cloudflare.com. dns.cloudflare.com. 2417435262 10000 2400 604800 1800
0ms
[OK] Quad9 9.9.9.9
lindsey.ns.cloudflare.com. dns.cloudflare.com. 2417435262 10000 2400 604800 1800
0ms
[OK] OpenDNS 208.67.222.222
lindsey.ns.cloudflare.com. dns.cloudflare.com. 2417435262 10000 2400 604800 1800
0ms
[OK] DNS.Watch 84.200.69.80
;; communications error to 84.200.69.80#53: timed out ;; no servers could be reached
17ms
[OK] Yandex 77.88.8.8
lindsey.ns.cloudflare.com. dns.cloudflare.com. 2417435262 10000 2400 604800 1800
0ms
[OK] Comodo 8.26.56.26
lindsey.ns.cloudflare.com. dns.cloudflare.com. 2417435262 10000 2400 604800 1800
0ms
[OK] Verisign 64.6.64.6
lindsey.ns.cloudflare.com. dns.cloudflare.com. 2417435262 10000 2400 604800 1800
0ms
[OK] Hurricane Electric 74.82.42.42
lindsey.ns.cloudflare.com. dns.cloudflare.com. 2417435262 10000 2400 604800 1800
0ms
[OK] AdGuard 94.140.14.14
lindsey.ns.cloudflare.com. dns.cloudflare.com. 2417435262 10000 2400 604800 1800
0ms
PTR record [WARN] partial
STATUSRESOLVERIPVALUELATENCY
[OK] Cloudflare 1.1.1.1
179-36-249-185.mrse.com.ar.
493ms
[OK] Cloudflare 2 1.0.0.1
179-36-249-185.mrse.com.ar.
0ms
[OK] Google 8.8.8.8
179-36-249-185.mrse.com.ar.
0ms
[OK] Google 2 8.8.4.4
179-36-249-185.mrse.com.ar.
0ms
[OK] Quad9 9.9.9.9
179-36-249-185.mrse.com.ar.
284ms
[OK] OpenDNS 208.67.222.222
179-36-249-185.mrse.com.ar.
537ms
[OK] DNS.Watch 84.200.69.80
;; communications error to 84.200.69.80#53: timed out ;; no servers could be reached
1714ms
[OK] Yandex 77.88.8.8
179-36-249-185.mrse.com.ar.
0ms
[OK] Comodo 8.26.56.26
179-36-249-185.mrse.com.ar.
0ms
[OK] Verisign 64.6.64.6
179-36-249-185.mrse.com.ar.
0ms
[OK] Hurricane Electric 74.82.42.42
179-36-249-185.mrse.com.ar.
0ms
[OK] AdGuard 94.140.14.14
179-36-249-185.mrse.com.ar.
0ms
TLS / SSL health [OK] 43d left
issuer
C = US, O = Let's Encrypt, CN = YE1
subject
CN = ajolote.com.ar
valid from
Aug 31 00:52:21 2026 GMT
valid to
Nov 29 00:52:20 2026 GMT
signature algorithm
ecdsa-with-SHA384
public key
id-ecPublicKey · 256 bit
subject alternative names (1)
ajolote.com.ar
sha256 fingerprint
D6:27:36:1B:90:BC:45:69:38:D0:7A:E7:46:FA:D4:19:9C:75:90:02:1A:77:41:BC:79:34:07:5E:AB:E5:25:6D
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 / ajolote.com.ar
How does the propagation check work for ajolote.com.ar? →

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.