dnsprobe v1
cached probe / public landing

DNS & SSL for monafricaonlinejobs.xyz

Last probed 1 hour ago. Use "re-check now" to refresh.

probe.2026100606
probe result / monafricaonlinejobs.xyz cached 1 hour ago · 6701ms
monafricaonlinejobs.xyz → · share:
A record [WARN] partial
STATUSRESOLVERIPVALUELATENCY
[OK] Cloudflare 1.1.1.1
163.61.188.5
110ms
[OK] Cloudflare 2 1.0.0.1
163.61.188.5
0ms
[OK] Google 8.8.8.8
163.61.188.5
0ms
[OK] Google 2 8.8.4.4
163.61.188.5
0ms
[OK] Quad9 9.9.9.9
163.61.188.5
0ms
[OK] OpenDNS 208.67.222.222
163.61.188.5
0ms
[OK] DNS.Watch 84.200.69.80
;; communications error to 84.200.69.80#53: timed out ;; no servers could be reached
2813ms
[OK] Yandex 77.88.8.8
163.61.188.5
0ms
[OK] Comodo 8.26.56.26
;; communications error to 8.26.56.26#53: timed out ;; no servers could be reached
6ms
[OK] Verisign 64.6.64.6
163.61.188.5
0ms
[OK] Hurricane Electric 74.82.42.42
163.61.188.5
0ms
[OK] AdGuard 94.140.14.14
163.61.188.5
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
4ms
[--] 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
4ms
[--] 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
[OK] Cloudflare 1.1.1.1
0 monafricaonlinejobs.xyz.
0ms
[OK] Cloudflare 2 1.0.0.1
0 monafricaonlinejobs.xyz.
0ms
[OK] Google 8.8.8.8
0 monafricaonlinejobs.xyz.
0ms
[OK] Google 2 8.8.4.4
0 monafricaonlinejobs.xyz.
0ms
[OK] Quad9 9.9.9.9
0 monafricaonlinejobs.xyz.
0ms
[OK] OpenDNS 208.67.222.222
0 monafricaonlinejobs.xyz.
0ms
[OK] DNS.Watch 84.200.69.80
;; communications error to 84.200.69.80#53: timed out ;; no servers could be reached
18ms
[OK] Yandex 77.88.8.8
0 monafricaonlinejobs.xyz.
0ms
[OK] Comodo 8.26.56.26
0 monafricaonlinejobs.xyz.
0ms
[OK] Verisign 64.6.64.6
0 monafricaonlinejobs.xyz.
0ms
[OK] Hurricane Electric 74.82.42.42
0 monafricaonlinejobs.xyz.
0ms
[OK] AdGuard 94.140.14.14
0 monafricaonlinejobs.xyz.
0ms
TXT record [WARN] partial
STATUSRESOLVERIPVALUELATENCY
[OK] Cloudflare 1.1.1.1
"v=spf1 +a +mx +ip4:163.61.188.5 include:relay.serverfoundation.com ~all"
0ms
[OK] Cloudflare 2 1.0.0.1
"v=spf1 +a +mx +ip4:163.61.188.5 include:relay.serverfoundation.com ~all"
0ms
[OK] Google 8.8.8.8
"v=spf1 +a +mx +ip4:163.61.188.5 include:relay.serverfoundation.com ~all"
0ms
[OK] Google 2 8.8.4.4
"v=spf1 +a +mx +ip4:163.61.188.5 include:relay.serverfoundation.com ~all"
0ms
[OK] Quad9 9.9.9.9
"v=spf1 +a +mx +ip4:163.61.188.5 include:relay.serverfoundation.com ~all"
0ms
[OK] OpenDNS 208.67.222.222
"v=spf1 +a +mx +ip4:163.61.188.5 include:relay.serverfoundation.com ~all"
0ms
[OK] DNS.Watch 84.200.69.80
;; communications error to 84.200.69.80#53: timed out ;; no servers could be reached
8ms
[OK] Yandex 77.88.8.8
"v=spf1 +a +mx +ip4:163.61.188.5 include:relay.serverfoundation.com ~all"
0ms
[OK] Comodo 8.26.56.26
"v=spf1 +a +mx +ip4:163.61.188.5 include:relay.serverfoundation.com ~all"
0ms
[OK] Verisign 64.6.64.6
"v=spf1 +a +mx +ip4:163.61.188.5 include:relay.serverfoundation.com ~all"
0ms
[OK] Hurricane Electric 74.82.42.42
"v=spf1 +a +mx +ip4:163.61.188.5 include:relay.serverfoundation.com ~all"
0ms
[OK] AdGuard 94.140.14.14
"v=spf1 +a +mx +ip4:163.61.188.5 include:relay.serverfoundation.com ~all"
0ms
NS record [WARN] partial
STATUSRESOLVERIPVALUELATENCY
[OK] Cloudflare 1.1.1.1
dns3.lytehosting.com. dns1.lytehosting.com. dns4.lytehosting.com. dns2.lytehosting.com.
0ms
[OK] Cloudflare 2 1.0.0.1
dns3.lytehosting.com. dns1.lytehosting.com. dns4.lytehosting.com. dns2.lytehosting.com.
0ms
[OK] Google 8.8.8.8
dns1.lytehosting.com. dns3.lytehosting.com. dns4.lytehosting.com. dns2.lytehosting.com.
0ms
[OK] Google 2 8.8.4.4
dns2.lytehosting.com. dns3.lytehosting.com. dns1.lytehosting.com. dns4.lytehosting.com.
0ms
[OK] Quad9 9.9.9.9
dns4.lytehosting.com. dns3.lytehosting.com. dns2.lytehosting.com. dns1.lytehosting.com.
0ms
[OK] OpenDNS 208.67.222.222
dns1.lytehosting.com. dns2.lytehosting.com. dns3.lytehosting.com. dns4.lytehosting.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
dns2.lytehosting.com. dns1.lytehosting.com. dns3.lytehosting.com. dns4.lytehosting.com.
0ms
[OK] Comodo 8.26.56.26
dns3.lytehosting.com. dns2.lytehosting.com. dns4.lytehosting.com. dns1.lytehosting.com.
0ms
[OK] Verisign 64.6.64.6
dns3.lytehosting.com. dns2.lytehosting.com. dns1.lytehosting.com. dns4.lytehosting.com.
0ms
[OK] Hurricane Electric 74.82.42.42
dns2.lytehosting.com. dns3.lytehosting.com. dns1.lytehosting.com. dns4.lytehosting.com.
0ms
[OK] AdGuard 94.140.14.14
dns3.lytehosting.com. dns2.lytehosting.com. dns1.lytehosting.com. dns4.lytehosting.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
14ms
[--] 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
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
20ms
[--] 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
dns1.lytehosting.com. atalha.lytehosting.net. 2026100404 3600 1800 1209600 86400
0ms
[OK] Cloudflare 2 1.0.0.1
dns1.lytehosting.com. atalha.lytehosting.net. 2026100404 3600 1800 1209600 86400
0ms
[OK] Google 8.8.8.8
dns1.lytehosting.com. atalha.lytehosting.net. 2026100404 3600 1800 1209600 86400
0ms
[OK] Google 2 8.8.4.4
dns1.lytehosting.com. atalha.lytehosting.net. 2026100404 3600 1800 1209600 86400
0ms
[OK] Quad9 9.9.9.9
dns1.lytehosting.com. atalha.lytehosting.net. 2026100404 3600 1800 1209600 86400
0ms
[OK] OpenDNS 208.67.222.222
dns1.lytehosting.com. atalha.lytehosting.net. 2026100404 3600 1800 1209600 86400
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
dns1.lytehosting.com. atalha.lytehosting.net. 2026100404 3600 1800 1209600 86400
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
dns1.lytehosting.com. atalha.lytehosting.net. 2026100404 3600 1800 1209600 86400
0ms
[OK] Hurricane Electric 74.82.42.42
dns1.lytehosting.com. atalha.lytehosting.net. 2026100404 3600 1800 1209600 86400
0ms
[OK] AdGuard 94.140.14.14
dns1.lytehosting.com. atalha.lytehosting.net. 2026100404 3600 1800 1209600 86400
0ms
PTR record [WARN] partial
STATUSRESOLVERIPVALUELATENCY
[OK] Cloudflare 1.1.1.1
s4.whitelabelclouds.com.
346ms
[OK] Cloudflare 2 1.0.0.1
s4.whitelabelclouds.com.
0ms
[OK] Google 8.8.8.8
s4.whitelabelclouds.com.
91ms
[OK] Google 2 8.8.4.4
s4.whitelabelclouds.com.
0ms
[OK] Quad9 9.9.9.9
s4.whitelabelclouds.com.
0ms
[OK] OpenDNS 208.67.222.222
s4.whitelabelclouds.com.
0ms
[OK] DNS.Watch 84.200.69.80
s4.whitelabelclouds.com.
645ms
[OK] Yandex 77.88.8.8
s4.whitelabelclouds.com.
0ms
[OK] Comodo 8.26.56.26
;; communications error to 8.26.56.26#53: timed out ;; no servers could be reached
1938ms
[OK] Verisign 64.6.64.6
s4.whitelabelclouds.com.
0ms
[OK] Hurricane Electric 74.82.42.42
s4.whitelabelclouds.com.
0ms
[OK] AdGuard 94.140.14.14
s4.whitelabelclouds.com.
0ms
TLS / SSL health [OK] 88d left
issuer
C = US, O = Let's Encrypt, CN = YR2
subject
CN = monafricaonlinejobs.xyz
valid from
Oct 4 09:33:49 2026 GMT
valid to
Jan 2 09:33:48 2027 GMT
signature algorithm
sha256WithRSAEncryption
public key
rsaEncryption · 2048 bit
subject alternative names (2)
*.monafricaonlinejobs.xyz monafricaonlinejobs.xyz
sha256 fingerprint
D0:09:88:3B:AB:25:C6:50:FA:D6:38:53:AA:AC:7F:DE:0A:49:72:E8:FF:23:E6:AB:0B:3F:68:80:D3:90:94:62
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 / monafricaonlinejobs.xyz
How does the propagation check work for monafricaonlinejobs.xyz? →

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.