View on GitHub

DNSViz: A DNS visualization tool

gov.sd

Updated: 2021-05-10 08:09:06 UTC (1335 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 (12)
  • gov.sd/NS
  • gov.sd/SOA
  • gov.sd/SOA
  • gov.sd/SOA
  • gov.sd/SOA
  • gov.sd/TXT
  • gov.sd/TXT
  • gov.sd/TXT
  • gov.sd/TXT
  • sd/SOA
  • sd/SOA
  • sd/SOA
Secure (1)
  • ./SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (3)
  • ./DNSKEY (alg 8, id 14631)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC proving non-existence of sd/DS

Delegation statusDelegation status

Insecure (2)
  • . to sd
  • sd to gov.sd

NoticesNotices

Errors (19)
  • gov.sd zone: The server(s) did not respond authoritatively for the namespace. See RFC 1035, Sec. 4.1.1. (196.216.168.26, 2001:43f8:120::26)
  • gov.sd zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (195.229.0.186, 213.42.0.226)
  • gov.sd zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (195.229.0.186, 213.42.0.226)
  • gov.sd zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (185.17.236.93)
  • gov.sd/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (196.29.164.14, 196.29.180.14, UDP_-_EDNS0_512_D_KN)
  • gov.sd/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (195.229.0.186, 213.42.0.226, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gov.sd/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (185.17.236.93, UDP_-_NOEDNS_)
  • gov.sd/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (195.229.0.186, 213.42.0.226, UDP_-_EDNS0_4096_D_KN)
  • gov.sd/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (195.229.0.186, 213.42.0.226, TCP_-_EDNS0_4096_D_N)
  • gov.sd/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (195.229.0.186, 213.42.0.226, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • gov.sd/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (195.229.0.186, 213.42.0.226, UDP_-_EDNS0_4096_D_KN)
  • sd zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (196.29.164.14, 196.29.180.14)
  • sd/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (196.29.164.14, 196.29.180.14, UDP_-_EDNS0_512_D_KN)
  • gov.sd/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.sd/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • 03fmwyrdgp.gov.sd/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.sd/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.sd/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • gov.sd/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (13)
  • gov.sd/NS: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed. See RFC 6891, Sec. 6.1.2. (196.29.164.14, 196.29.180.14, UDP_-_EDNS0_4096_D_KN)
  • gov.sd/SOA: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed. See RFC 6891, Sec. 6.1.2. (196.29.164.14, 196.29.180.14, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • gov.sd/TXT: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed. See RFC 6891, Sec. 6.1.2. (196.29.164.14, 196.29.180.14, UDP_-_EDNS0_4096_D_KN)
  • sd to gov.sd: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed. See RFC 6891, Sec. 6.1.2. (196.29.164.14, 196.29.180.14, UDP_-_EDNS0_4096_D_KN)
  • sd to gov.sd: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the sd zone): ns.cocca.fr, pch.sis.sd See RFC 1034, Sec. 4.2.2.
  • sd to gov.sd: The following NS name(s) were found in the delegation NS RRset (i.e., in the sd zone), but not in the authoritative NS RRset: ns1.uaenic.ae, ns2.uaenic.ae See RFC 1034, Sec. 4.2.2.
  • gov.sd/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.sd/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.sd/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 03fmwyrdgp.gov.sd/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.sd/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.sd/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gov.sd/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