View on GitHub
jabber.ru
Updated:
2024-10-11 09:01:12 UTC
(
96 days ago
)
Go to most recent »
« Previous analysis
|
Next analysis »
Tweet
DNSSEC
Responses
Servers
Analyze
DNSSEC options (
hide
)
|?|
RR types:
--All--
A
AAAA
TXT
PTR
MX
NS
SOA
CNAME
SRV
NAPTR
TLSA
NSEC3PARAM
CDNSKEY
CDS
CAA
|?|
DNSSEC algorithms:
--All--
1 - RSA/MD5
3 - DSA/SHA1
5 - RSA/SHA-1
6 - DSA-NSEC3-SHA1
7 - RSASHA1-NSEC3-SHA1
8 - RSA/SHA-256
10 - RSA/SHA-512
12 - GOST R 34.10-2001
13 - ECDSA Curve P-256 with SHA-256
14 - ECDSA Curve P-384 with SHA-384
15 - Ed25519
16 - Ed448
|?|
DS digest algorithms:
--All--
1 - SHA-1
2 - SHA-256
3 - GOST R 34.11-94
4 - SHA-384
|?|
Denial of existence:
|?|
Redundant edges:
|?|
Ignore RFC 8624:
|?|
Ignore RFC 9276:
|?|
Multi-signer:
|?|
Trust anchors:
Root zone KSK
|?|
Additional trusted keys:
Notices
DNSSEC Authentication Chain
RRset status
Secure
(5)
jabber.ru/A
jabber.ru/MX
jabber.ru/NS
jabber.ru/SOA
jabber.ru/TXT
DNSKEY/DS/NSEC status
Secure
(9)
./DNSKEY (alg 8, id 20038)
./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 61050)
jabber.ru/DNSKEY (alg 8, id 38443)
jabber.ru/DNSKEY (alg 8, id 65447)
jabber.ru/DS (alg 8, id 65447)
ru/DNSKEY (alg 8, id 27405)
ru/DNSKEY (alg 8, id 43786)
ru/DS (alg 8, id 43786)
Delegation status
Secure
(2)
. to ru
ru to jabber.ru
Notices
Errors
(16)
jabber.ru zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (139.162.179.224)
jabber.ru zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (139.162.179.224)
jabber.ru/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (139.162.179.224, UDP_-_NOEDNS_)
jabber.ru/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (139.162.179.224, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
jabber.ru/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (139.162.179.224, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
jabber.ru/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (139.162.179.224, UDP_-_NOEDNS_)
jabber.ru/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (139.162.179.224, TCP_-_EDNS0_4096_D_N)
jabber.ru/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (139.162.179.224, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
jabber.ru/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (139.162.179.224, UDP_-_NOEDNS_)
jabber.ru/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
jabber.ru/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
ic8bp.fpdak.jabber.ru/A has errors; select the "Denial of existence" DNSSEC option to see them.
jabber.ru/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
jabber.ru/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
jabber.ru/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
jabber.ru/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
DNSKEY legend
Full legend
SEP bit set
Revoke bit set
Trust anchor
See also
DNSSEC Debugger
by
Verisign Labs
.
Download:
png
|
svg
JavaScript is required to make the graph below interactive.