View on GitHub

DNSViz: A DNS visualization tool

gov.na

Updated: 2023-08-10 10:28:20 UTC (513 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (8)
  • gov.na/A
  • gov.na/MX
  • gov.na/NS
  • gov.na/NSEC3PARAM
  • gov.na/NSEC3PARAM
  • gov.na/SOA
  • gov.na/SOA
  • gov.na/TXT
Secure (3)
  • na/SOA
  • na/SOA
  • na/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (2)
  • gov.na/DNSKEY (alg 7, id 32438)
  • gov.na/DNSKEY (alg 7, id 62511)
Secure (7)
  • ./DNSKEY (alg 8, id 11019)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC3 proving non-existence of gov.na/DS
  • na/DNSKEY (alg 8, id 25079)
  • na/DNSKEY (alg 8, id 57346)
  • na/DNSKEY (alg 8, id 60306)
  • na/DS (alg 8, id 25079)

Delegation statusDelegation status

Insecure (1)
  • na to gov.na
Secure (1)
  • . to na

NoticesNotices

Errors (18)
  • NSEC3 proving non-existence of gov.na/DS: 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.na/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • gov.na zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (41.205.143.146)
  • gov.na zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (41.205.143.146)
  • gov.na/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (41.205.143.146, UDP_-_NOEDNS_)
  • gov.na/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (41.205.143.146, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • gov.na/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (41.205.143.146, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • gov.na/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (41.205.143.146, UDP_-_NOEDNS_)
  • gov.na/NSEC3PARAM: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (41.205.143.146, UDP_-_NOEDNS_)
  • gov.na/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (41.205.143.146, TCP_-_NOEDNS_)
  • gov.na/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (41.205.143.146, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • gov.na/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (41.205.143.146, UDP_-_NOEDNS_)
  • na zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2607:f740:45::54)
  • gov.na/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • p0kievwgmj.gov.na/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.na/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.na/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.na/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (27)
  • NSEC3 proving non-existence of gov.na/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of gov.na/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • RRSIG gov.na/A alg 7, id 32438: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.na/A alg 7, id 32438: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.na/DNSKEY alg 7, id 32438: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.na/DNSKEY alg 7, id 32438: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.na/DNSKEY alg 7, id 32438: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.na/DNSKEY alg 7, id 32438: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.na/DNSKEY alg 7, id 62511: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.na/DNSKEY alg 7, id 62511: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.na/DNSKEY alg 7, id 62511: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.na/DNSKEY alg 7, id 62511: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.na/MX alg 7, id 32438: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.na/MX alg 7, id 32438: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.na/NS alg 7, id 32438: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.na/NS alg 7, id 32438: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.na/NSEC3PARAM alg 7, id 32438: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.na/NSEC3PARAM alg 7, id 32438: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.na/SOA alg 7, id 32438: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.na/SOA alg 7, id 32438: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.na/TXT alg 7, id 32438: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gov.na/TXT alg 7, id 32438: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • gov.na/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • p0kievwgmj.gov.na/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.na/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.na/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.na/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