cached probe / public landing
DNS & SSL for ajolote.com.ar
Last probed 23 hours ago. Use "re-check now" to refresh.
probe.2026092022
probe result
/
ajolote.com.ar
cached 23 hours ago
· 7291ms
A
record
[WARN] partial
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
186.61.250.187
|
0ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
186.61.250.187
|
0ms |
| [OK] | 8.8.8.8 |
186.61.250.187
|
0ms | |
| [OK] | Google 2 | 8.8.4.4 |
186.61.250.187
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
186.61.250.187
|
0ms |
| [OK] | OpenDNS | 208.67.222.222 |
186.61.250.187
|
0ms |
| [OK] | DNS.Watch | 84.200.69.80 |
186.61.250.187
|
107ms |
| [OK] | Yandex | 77.88.8.8 |
186.61.250.187
|
0ms |
| [OK] | Comodo | 8.26.56.26 |
;; communications error to 8.26.56.26#53: timed out
;; no servers could be reached
|
2826ms |
| [OK] | Verisign | 64.6.64.6 |
186.61.250.187
|
0ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
186.61.250.187
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
186.61.250.187
|
0ms |
AAAA
record
[WARN] partial
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [--] | Cloudflare | 1.1.1.1 | — no answer | 0ms |
| [--] | 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 | 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
|
9ms |
| [--] | 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
|
1ms |
| [--] | 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
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [--] | Cloudflare | 1.1.1.1 | — no answer | 0ms |
| [--] | 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 | 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
|
14ms |
| [--] | 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
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [--] | Cloudflare | 1.1.1.1 | — no answer | 0ms |
| [--] | 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 | 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
|
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 |
NS
record
[WARN] partial
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [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] | 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 |
lindsey.ns.cloudflare.com.
mitchell.ns.cloudflare.com.
|
0ms |
| [OK] | Yandex | 77.88.8.8 |
mitchell.ns.cloudflare.com.
lindsey.ns.cloudflare.com.
|
0ms |
| [OK] | Comodo | 8.26.56.26 |
;; communications error to 8.26.56.26#53: timed out
;; no servers could be reached
|
16ms |
| [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 |
mitchell.ns.cloudflare.com.
lindsey.ns.cloudflare.com.
|
0ms |
CNAME
record
[WARN] partial
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [--] | Cloudflare | 1.1.1.1 | — no answer | 0ms |
| [--] | 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 | 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
|
14ms |
| [--] | 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
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [--] | Cloudflare | 1.1.1.1 | — no answer | 0ms |
| [--] | 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 | 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
|
15ms |
| [--] | 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
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
lindsey.ns.cloudflare.com. dns.cloudflare.com. 2414410257 10000 2400 604800 1800
|
0ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
lindsey.ns.cloudflare.com. dns.cloudflare.com. 2414410257 10000 2400 604800 1800
|
0ms |
| [OK] | 8.8.8.8 |
lindsey.ns.cloudflare.com. dns.cloudflare.com. 2414410257 10000 2400 604800 1800
|
0ms | |
| [OK] | Google 2 | 8.8.4.4 |
lindsey.ns.cloudflare.com. dns.cloudflare.com. 2414410257 10000 2400 604800 1800
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
lindsey.ns.cloudflare.com. dns.cloudflare.com. 2414410257 10000 2400 604800 1800
|
0ms |
| [OK] | OpenDNS | 208.67.222.222 |
lindsey.ns.cloudflare.com. dns.cloudflare.com. 2414410257 10000 2400 604800 1800
|
0ms |
| [OK] | DNS.Watch | 84.200.69.80 |
lindsey.ns.cloudflare.com. dns.cloudflare.com. 2414410257 10000 2400 604800 1800
|
0ms |
| [OK] | Yandex | 77.88.8.8 |
lindsey.ns.cloudflare.com. dns.cloudflare.com. 2414410257 10000 2400 604800 1800
|
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 |
lindsey.ns.cloudflare.com. dns.cloudflare.com. 2414410257 10000 2400 604800 1800
|
0ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
lindsey.ns.cloudflare.com. dns.cloudflare.com. 2414410257 10000 2400 604800 1800
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
lindsey.ns.cloudflare.com. dns.cloudflare.com. 2414410257 10000 2400 604800 1800
|
0ms |
PTR
record
[WARN] partial
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
186-61-250-187.mrse.com.ar.
|
484ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
186-61-250-187.mrse.com.ar.
|
11ms |
| [OK] | 8.8.8.8 |
186-61-250-187.mrse.com.ar.
|
0ms | |
| [OK] | Google 2 | 8.8.4.4 |
186-61-250-187.mrse.com.ar.
|
0ms |
| [OK] | Quad9 | 9.9.9.9 |
186-61-250-187.mrse.com.ar.
|
31ms |
| [OK] | OpenDNS | 208.67.222.222 |
186-61-250-187.mrse.com.ar.
|
825ms |
| [OK] | DNS.Watch | 84.200.69.80 |
;; communications error to 84.200.69.80#53: timed out
;; no servers could be reached
|
1688ms |
| [OK] | Yandex | 77.88.8.8 |
186-61-250-187.mrse.com.ar.
|
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 |
186-61-250-187.mrse.com.ar.
|
0ms |
| [OK] | Hurricane Electric | 74.82.42.42 |
186-61-250-187.mrse.com.ar.
|
0ms |
| [OK] | AdGuard | 94.140.14.14 |
186-61-250-187.mrse.com.ar.
|
0ms |
TLS / SSL health
[OK] 69d 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.