cached probe / public landing
DNS & SSL for beget.com
Last probed 2 hours ago. Use "re-check now" to refresh.
A
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 |
| [OK] | 8.8.8.8 |
;; communications error to 8.8.8.8#53: timed out
;; no servers could be reached
|
2895ms | |
| [OK] | Google 2 | 8.8.4.4 |
;; communications error to 8.8.4.4#53: timed out
;; no servers could be reached
|
1ms |
| [OK] | Quad9 | 9.9.9.9 |
;; communications error to 9.9.9.9#53: timed out
;; no servers could be reached
|
22ms |
| [--] | 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 |
| [--] | Comodo | 8.26.56.26 | — no answer | 0ms |
| [OK] | Verisign | 64.6.64.6 |
;; communications error to 64.6.64.6#53: timed out
;; no servers could be reached
|
0ms |
| [--] | Hurricane Electric | 74.82.42.42 | — no answer | 0ms |
| [--] | AdGuard | 94.140.14.14 | — no answer | 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 |
| [OK] | 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
|
2ms |
| [--] | 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
|
2ms |
| [--] | Yandex | 77.88.8.8 | — no answer | 0ms |
| [--] | Comodo | 8.26.56.26 | — no answer | 0ms |
| [OK] | Verisign | 64.6.64.6 |
;; communications error to 64.6.64.6#53: timed out
;; no servers could be reached
|
1ms |
| [--] | 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 |
MX
record
[WARN] partial
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
;; communications error to 1.1.1.1#53: timed out
;; no servers could be reached
|
6ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
;; communications error to 1.0.0.1#53: timed out
;; no servers could be reached
|
0ms |
| [OK] | 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
|
5ms |
| [OK] | Quad9 | 9.9.9.9 |
;; communications error to 9.9.9.9#53: timed out
;; no servers could be reached
|
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
|
5ms |
| [--] | Yandex | 77.88.8.8 | — no answer | 0ms |
| [--] | Comodo | 8.26.56.26 | — no answer | 0ms |
| [OK] | Verisign | 64.6.64.6 |
;; communications error to 64.6.64.6#53: timed out
;; no servers could be reached
|
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
|
5ms |
TXT
record
[WARN] partial
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
;; communications error to 1.1.1.1#53: timed out
;; no servers could be reached
|
0ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
;; communications error to 1.0.0.1#53: timed out
;; no servers could be reached
|
0ms |
| [OK] | 8.8.8.8 |
;; communications error to 8.8.8.8#53: timed out
;; no servers could be reached
|
1ms | |
| [OK] | Google 2 | 8.8.4.4 |
;; communications error to 8.8.4.4#53: timed out
;; no servers could be reached
|
1ms |
| [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
|
4ms |
| [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 |
| [--] | Comodo | 8.26.56.26 | — no answer | 0ms |
| [OK] | Verisign | 64.6.64.6 |
;; communications error to 64.6.64.6#53: timed out
;; no servers could be reached
|
3ms |
| [--] | 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
|
4ms |
NS
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 |
| [OK] | 8.8.8.8 |
;; communications error to 8.8.8.8#53: timed out
;; no servers could be reached
|
10ms | |
| [OK] | Google 2 | 8.8.4.4 |
;; communications error to 8.8.4.4#53: timed out
;; no servers could be reached
|
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 |
| [--] | Comodo | 8.26.56.26 | — no answer | 0ms |
| [OK] | Verisign | 64.6.64.6 |
;; communications error to 64.6.64.6#53: timed out
;; no servers could be reached
|
7ms |
| [--] | 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
|
2ms |
CNAME
record
[WARN] partial
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
;; communications error to 1.1.1.1#53: timed out
;; no servers could be reached
|
0ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
;; communications error to 1.0.0.1#53: timed out
;; no servers could be reached
|
0ms |
| [OK] | 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
|
8ms |
| [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 |
| [--] | Comodo | 8.26.56.26 | — no answer | 0ms |
| [OK] | Verisign | 64.6.64.6 |
;; communications error to 64.6.64.6#53: timed out
;; no servers could be reached
|
4ms |
| [--] | 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
|
3ms |
CAA
record
[WARN] partial
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
;; communications error to 1.1.1.1#53: timed out
;; no servers could be reached
|
1ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
;; communications error to 1.0.0.1#53: timed out
;; no servers could be reached
|
0ms |
| [OK] | 8.8.8.8 |
;; communications error to 8.8.8.8#53: timed out
;; no servers could be reached
|
3ms | |
| [OK] | Google 2 | 8.8.4.4 |
;; communications error to 8.8.4.4#53: timed out
;; no servers could be reached
|
7ms |
| [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 |
| [--] | Yandex | 77.88.8.8 | — no answer | 0ms |
| [--] | Comodo | 8.26.56.26 | — no answer | 0ms |
| [OK] | Verisign | 64.6.64.6 |
;; communications error to 64.6.64.6#53: timed out
;; no servers could be reached
|
4ms |
| [--] | 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
|
1ms |
SOA
record
[WARN] partial
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [OK] | Cloudflare | 1.1.1.1 |
;; communications error to 1.1.1.1#53: timed out
;; no servers could be reached
|
0ms |
| [OK] | Cloudflare 2 | 1.0.0.1 |
;; communications error to 1.0.0.1#53: timed out
;; no servers could be reached
|
0ms |
| [OK] | 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
|
1ms |
| [OK] | Quad9 | 9.9.9.9 |
;; communications error to 9.9.9.9#53: timed out
;; no servers could be reached
|
2ms |
| [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 |
| [--] | Yandex | 77.88.8.8 | — no answer | 0ms |
| [--] | Comodo | 8.26.56.26 | — no answer | 0ms |
| [OK] | Verisign | 64.6.64.6 |
;; communications error to 64.6.64.6#53: timed out
;; no servers could be reached
|
10ms |
| [--] | 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
|
10ms |
PTR
record
[WARN] partial
| STATUS | RESOLVER | IP | VALUE | LATENCY |
|---|---|---|---|---|
| [--] | Cloudflare | 1.1.1.1 | — no answer | 123ms |
| [--] | 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 | 93ms |
| [OK] | DNS.Watch | 84.200.69.80 |
;; communications error to 84.200.69.80#53: timed out
;; no servers could be reached
|
2822ms |
| [--] | 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 |
TLS / SSL health
[OK] 59d left
issuer
C = US, O = Let's Encrypt, CN = YR1
subject
CN = www.beget.com
valid from
Oct 2 23:41:14 2026 GMT
valid to
Dec 31 23:41:13 2026 GMT
signature algorithm
sha256WithRSAEncryption
public key
rsaEncryption · 2048 bit
subject alternative names (2)
beget.com
www.beget.com
sha256 fingerprint
0C:F8:42:B5:FA:06:54:62:06:B5:27:4D:03:AD:C7:99:C2:F0:44:96:C0:EE:6D:B5:EF:3F:CB:D9:58:74:02:41
TLS 1.0
[OK] disabled
TLS 1.1
[OK] disabled
TLS 1.2
[OK] supported
TLS 1.3
[OK] supported
HTTP/2
[--] no
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 / beget.com
How does the propagation check work for beget.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.