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

Bogus (6)
  • gov.gr/A
  • gov.gr/MX
  • gov.gr/NS (NODATA)
  • gov.gr/SOA (NODATA)
  • gov.gr/TXT (NODATA)
  • gr/SOA
Secure (5)
  • gov.gr/A
  • gov.gr/MX (NODATA)
  • gov.gr/NS
  • gov.gr/SOA
  • gov.gr/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 42351)
  • NSEC3 proving non-existence of gov.gr/MX
  • gov.gr/DNSKEY (alg 7, id 41609)
  • gov.gr/DNSKEY (alg 7, id 61908)
  • gov.gr/DS (alg 7, id 45324)
  • gov.gr/DS (alg 7, id 61908)
  • gov.gr/DS (alg 7, id 61908)
  • gr/DNSKEY (alg 7, id 33317)
  • gr/DNSKEY (alg 7, id 35136)
  • gr/DNSKEY (alg 7, id 7835)
  • gr/DS (alg 7, id 35136)
Non_existent (1)
  • gov.gr/DNSKEY (alg 7, id 45324)

Delegation statusDelegation status

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

NoticesNotices

Errors (25)
  • NSEC3 proving non-existence of gov.gr/MX: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of gov.gr/MX: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of gov.gr/MX: The following queries resulted in an answer response, even though the bitmap in the NSEC3 RR indicates that the queried records don't exist: gov.gr/MX See RFC 5155, Sec. 8.5.
  • NSEC3 proving non-existence of gov.gr/MX: The following queries resulted in an answer response, even though the bitmap in the NSEC3 RR indicates that the queried records don't exist: gov.gr/MX See RFC 5155, Sec. 8.5.
  • gov.gr/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (93.174.121.39, UDP_-_EDNS0_4096_D_KN)
  • gov.gr/DNSKEY (alg 7, id 41609): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (93.174.121.39, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gov.gr/DNSKEY (alg 7, id 61908): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (93.174.121.39, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gov.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)
  • gov.gr/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (93.174.121.39, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gov.gr/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (78.104.145.227, UDP_-_EDNS0_512_D_KN)
  • gov.gr/NS (NODATA): An SOA RR with owner name (gr) not matching the zone name (gov.gr) was returned with the NODATA response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (93.174.121.39, UDP_-_EDNS0_4096_D_KN)
  • gov.gr/NS (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (93.174.121.39, UDP_-_EDNS0_4096_D_KN)
  • gov.gr/SOA (NODATA): An SOA RR with owner name (gr) not matching the zone name (gov.gr) was returned with the NODATA response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (93.174.121.39, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • gov.gr/SOA (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (93.174.121.39, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • gov.gr/TXT (NODATA): An SOA RR with owner name (gr) not matching the zone name (gov.gr) was returned with the NODATA response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (93.174.121.39, UDP_-_EDNS0_4096_D_KN)
  • gov.gr/TXT (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (93.174.121.39, UDP_-_EDNS0_4096_D_KN)
  • gr to gov.gr: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (93.174.121.39, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gr to gov.gr: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no DS RR matched a DNSKEY with algorithm 7 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (93.174.121.39, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gr zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:648:2c30::191:3)
  • gr/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (78.104.145.227, UDP_-_EDNS0_512_D_KN)
  • gr/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (93.174.121.39, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • gov.gr/AAAA 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.
  • gov.gr/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • 43bzt70quy.gov.gr/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (47)
  • NSEC3 proving non-existence of gov.gr/MX: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of gov.gr/MX: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of gov.gr/MX 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/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 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/DS alg 7, id 7835: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.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 gov.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 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/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/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.
  • 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 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 gr/DNSKEY alg 7, id 7835: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • gov.gr/A: The server responded with no OPT record, rather than with RCODE FORMERR. See RFC 6891, Sec. 7. (93.174.121.39, UDP_-_EDNS0_4096_D_KN)
  • gov.gr/DS (alg 7, id 45324): 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. (78.104.145.227, 139.91.191.3, UDP_-_EDNS0_4096_D_KN)
  • gov.gr/DS (alg 7, id 45324): 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. (78.104.145.227, 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. (78.104.145.227, 139.91.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. (78.104.145.227, 139.91.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. (78.104.145.227, 139.91.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. (78.104.145.227, 139.91.191.3, UDP_-_EDNS0_4096_D_KN)
  • gov.gr/MX (NODATA): No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (78.104.145.227, UDP_-_EDNS0_4096_D_KN)
  • gov.gr/MX: The server responded with no OPT record, rather than with RCODE FORMERR. See RFC 6891, Sec. 7. (93.174.121.39, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gov.gr/NS (NODATA): The server responded with no OPT record, rather than with RCODE FORMERR. See RFC 6891, Sec. 7. (93.174.121.39, UDP_-_EDNS0_4096_D_KN)
  • gov.gr/SOA (NODATA): The server responded with no OPT record, rather than with RCODE FORMERR. See RFC 6891, Sec. 7. (93.174.121.39, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • 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. (78.104.145.227, 139.91.191.3, UDP_-_EDNS0_4096_D_KN)
  • gov.gr/TXT (NODATA): The server responded with no OPT record, rather than with RCODE FORMERR. See RFC 6891, Sec. 7. (93.174.121.39, 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, UDP_-_EDNS0_4096_D_KN)
  • gr/DNSKEY (alg 7, id 33317): 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. (78.104.145.227, 139.91.191.3, UDP_-_EDNS0_4096_D_KN)
  • 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. (78.104.145.227, 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. (78.104.145.227, 139.91.191.3, UDP_-_EDNS0_4096_D_KN)
  • 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.
  • 43bzt70quy.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.

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