View on GitHub

DNSViz: A DNS visualization tool

spikar.gr

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Secure (7)
  • spikar.gr/A
  • spikar.gr/AAAA
  • spikar.gr/MX
  • spikar.gr/NS
  • spikar.gr/NSEC3PARAM
  • spikar.gr/SOA
  • spikar.gr/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 9799)
  • gr/DNSKEY (alg 7, id 35136)
  • gr/DNSKEY (alg 7, id 7835)
  • gr/DS (alg 7, id 35136)
  • spikar.gr/DNSKEY (alg 13, id 4329)
  • spikar.gr/DS (alg 13, id 4329)
  • spikar.gr/DS (alg 13, id 4329)

Delegation statusDelegation status

Secure (2)
  • . to gr
  • gr to spikar.gr

NoticesNotices

Errors (1)
  • gr/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (139.91.191.3, UDP_-_EDNS0_512_D_KN)
Warnings (15)
  • RRSIG gr/DNSKEY alg 7, id 35136: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gr/DNSKEY alg 7, id 35136: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gr/DNSKEY alg 7, id 7835: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gr/DNSKEY alg 7, id 7835: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG spikar.gr/DS alg 7, id 7835: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG spikar.gr/DS alg 7, id 7835: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • gr/DNSKEY (alg 7, id 35136): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (139.91.191.3, UDP_-_EDNS0_4096_D_KN)
  • gr/DNSKEY (alg 7, id 7835): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (139.91.191.3, UDP_-_EDNS0_4096_D_KN)
  • spikar.gr/DS (alg 13, id 4329): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • spikar.gr/DS (alg 13, id 4329): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • spikar.gr/DS (alg 13, id 4329): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • spikar.gr/DS (alg 13, id 4329): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • spikar.gr/DS (alg 13, id 4329): In the spirit of RFC 4509, DS records with digest type 1 (SHA-1) might be ignored when DS records with digest type 4 (SHA-384) exist in the same RRset. See RFC 4509, Sec. 3.
  • spikar.gr/DS (alg 13, id 4329): In the spirit of RFC 4509, DS records with digest type 1 (SHA-1) might be ignored when DS records with digest type 4 (SHA-384) exist in the same RRset. See RFC 4509, Sec. 3.
  • spikar.gr/DS has warnings; select the "Denial of existence" DNSSEC option to see them.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph