View on GitHub

DNSViz: A DNS visualization tool

gov.gr

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

RRset statusRRset status

Secure (5)
  • gov.gr/A
  • gov.gr/NS
  • gov.gr/NSEC3PARAM
  • gov.gr/SOA
  • gov.gr/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 47671)
  • gov.gr/DNSKEY (alg 7, id 41609)
  • gov.gr/DNSKEY (alg 7, id 61908)
  • gov.gr/DNSKEY (alg 8, id 23361)
  • gov.gr/DNSKEY (alg 8, id 30022)
  • gov.gr/DS (alg 7, id 61908)
  • gov.gr/DS (alg 7, id 61908)
  • gov.gr/DS (alg 8, id 30022)
  • gr/DNSKEY (alg 8, id 13987)
  • gr/DNSKEY (alg 8, id 45264)
  • gr/DS (alg 8, id 13987)

Delegation statusDelegation status

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

NoticesNotices

Errors (7)
  • gov.gr/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:648:2c30::191:3, UDP_-_NOEDNS_)
  • gov.gr/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:648:2c30::191:3, UDP_-_NOEDNS__0x20)
  • gr/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2001:648:2c30::191:3, UDP_-_EDNS0_512_D_KN)
  • gov.gr/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.gr/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • knhfwt1q3m.gov.gr/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.gr/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (38)
  • RRSIG gov.gr/A alg 7, id 41609: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.gr/DNSKEY alg 7, id 41609: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.gr/DNSKEY alg 7, id 41609: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.gr/DNSKEY alg 7, id 41609: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.gr/DNSKEY alg 7, id 41609: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.gr/DNSKEY alg 7, id 61908: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.gr/DNSKEY alg 7, id 61908: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.gr/DNSKEY alg 7, id 61908: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.gr/DNSKEY alg 7, id 61908: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.gr/NS alg 7, id 41609: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.gr/NSEC3PARAM alg 7, id 41609: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.gr/SOA alg 7, id 41609: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.gr/TXT alg 7, id 41609: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • gov.gr/DNSKEY (alg 7, id 41609): 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)
  • gov.gr/DNSKEY (alg 7, id 61908): 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)
  • gov.gr/DNSKEY (alg 8, id 23361): 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)
  • gov.gr/DNSKEY (alg 8, id 30022): 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)
  • gov.gr/DS (alg 7, id 61908): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov.gr/DS (alg 7, id 61908): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov.gr/DS (alg 7, id 61908): 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.
  • gov.gr/DS (alg 7, id 61908): 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.
  • gov.gr/DS (alg 7, id 61908): 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, 2001:648:2c30::191:3, UDP_-_EDNS0_4096_D_KN)
  • gov.gr/DS (alg 7, id 61908): 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, 2001:648:2c30::191:3, UDP_-_EDNS0_4096_D_KN)
  • gov.gr/DS (alg 7, id 61908): 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, 2001:648:2c30::191:3, UDP_-_EDNS0_4096_D_KN)
  • gov.gr/DS (alg 7, id 61908): 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, 2001:648:2c30::191:3, UDP_-_EDNS0_4096_D_KN)
  • gov.gr/DS (alg 8, id 30022): 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, 2001:648:2c30::191:3, UDP_-_EDNS0_4096_D_KN)
  • gov.gr/DS (alg 8, id 30022): 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, 2001:648:2c30::191:3, UDP_-_EDNS0_4096_D_KN)
  • gov.gr/SOA: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (2001:648:2c30::191:3, UDP_-_EDNS0_4096_D_KN)
  • gov.gr/SOA: 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)
  • gov.gr/TXT: 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, 2001:648:2c30::191:3, UDP_-_EDNS0_4096_D_KN)
  • gr/DNSKEY (alg 8, id 13987): 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. (2001:648:2c30::191:3, UDP_-_EDNS0_4096_D_KN)
  • gr/DNSKEY (alg 8, id 45264): 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. (2001:648:2c30::191:3, UDP_-_EDNS0_4096_D_KN)
  • knhfwt1q3m.gov.gr/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.gr/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.gr/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.gr/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.gr/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.gr/CNAME 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