View on GitHub

DNSViz: A DNS visualization tool

ustda.gov

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

RRset statusRRset status

Insecure (12)
  • ustda.gov/A
  • ustda.gov/A (NODATA)
  • ustda.gov/AAAA
  • ustda.gov/AAAA (NODATA)
  • ustda.gov/MX
  • ustda.gov/NS
  • ustda.gov/NS
  • ustda.gov/NSEC3PARAM
  • ustda.gov/NSEC3PARAM (NODATA)
  • ustda.gov/SOA
  • ustda.gov/SOA
  • ustda.gov/TXT
Secure (1)
  • gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (8)
  • NSEC proving non-existence of ustda.gov/A
  • NSEC proving non-existence of ustda.gov/AAAA
  • NSEC proving non-existence of ustda.gov/NSEC3PARAM
  • ustda.gov/DNSKEY (alg 13, id 32001)
  • ustda.gov/DNSKEY (alg 13, id 61412)
  • ustda.gov/DNSKEY (alg 13, id 62241)
  • ustda.gov/DNSKEY (alg 8, id 21705)
  • ustda.gov/DNSKEY (alg 8, id 51215)
Secure (10)
  • ./DNSKEY (alg 8, id 11019)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46780)
  • NSEC3 proving non-existence of ustda.gov/DS
  • gov/DNSKEY (alg 8, id 10104)
  • gov/DNSKEY (alg 8, id 40921)
  • gov/DNSKEY (alg 8, id 64280)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 64280)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

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

NoticesNotices

Errors (38)
  • NSEC proving non-existence of ustda.gov/A: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (216.59.57.8, 216.59.60.8, 2602:ffe2:54::8, UDP_-_EDNS0_4096_D_KN)
  • NSEC proving non-existence of ustda.gov/A: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (216.59.57.8, 216.59.60.8, 2602:ffe2:54::8, UDP_-_EDNS0_4096_D_KN)
  • NSEC proving non-existence of ustda.gov/A: The following queries resulted in an answer response, even though the bitmap in the NSEC RR indicates that the queried records don't exist: ustda.gov/A, ustda.gov/AAAA, ustda.gov/NSEC3PARAM See RFC 4035, Sec. 3.1.3.1.
  • NSEC proving non-existence of ustda.gov/A: The following queries resulted in an answer response, even though the bitmap in the NSEC RR indicates that the queried records don't exist: ustda.gov/A, ustda.gov/AAAA, ustda.gov/NSEC3PARAM See RFC 4035, Sec. 3.1.3.1.
  • NSEC proving non-existence of ustda.gov/AAAA: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (216.59.57.8, 216.59.60.8, 2602:ffe2:54::8, UDP_-_EDNS0_4096_D_KN)
  • NSEC proving non-existence of ustda.gov/AAAA: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (216.59.57.8, 216.59.60.8, 2602:ffe2:54::8, UDP_-_EDNS0_4096_D_KN)
  • NSEC proving non-existence of ustda.gov/AAAA: The following queries resulted in an answer response, even though the bitmap in the NSEC RR indicates that the queried records don't exist: ustda.gov/A, ustda.gov/AAAA, ustda.gov/NSEC3PARAM See RFC 4035, Sec. 3.1.3.1.
  • NSEC proving non-existence of ustda.gov/AAAA: The following queries resulted in an answer response, even though the bitmap in the NSEC RR indicates that the queried records don't exist: ustda.gov/A, ustda.gov/AAAA, ustda.gov/NSEC3PARAM See RFC 4035, Sec. 3.1.3.1.
  • NSEC proving non-existence of ustda.gov/NSEC3PARAM: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (216.59.57.8, 216.59.60.8, 2602:ffe2:54::8, UDP_-_EDNS0_4096_D_KN)
  • NSEC proving non-existence of ustda.gov/NSEC3PARAM: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (216.59.57.8, 216.59.60.8, 2602:ffe2:54::8, UDP_-_EDNS0_4096_D_KN)
  • NSEC proving non-existence of ustda.gov/NSEC3PARAM: The following queries resulted in an answer response, even though the bitmap in the NSEC RR indicates that the queried records don't exist: ustda.gov/A, ustda.gov/AAAA, ustda.gov/NSEC3PARAM See RFC 4035, Sec. 3.1.3.1.
  • NSEC proving non-existence of ustda.gov/NSEC3PARAM: The following queries resulted in an answer response, even though the bitmap in the NSEC RR indicates that the queried records don't exist: ustda.gov/A, ustda.gov/AAAA, ustda.gov/NSEC3PARAM See RFC 4035, Sec. 3.1.3.1.
  • NSEC3 proving non-existence of ustda.gov/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 ustda.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • RRSIG ustda.gov/MX alg 8, id 21705: The TTL of the RRset (600) exceeds the value of the Original TTL field of the RRSIG RR covering it (60). See RFC 4035, Sec. 2.2.
  • RRSIG ustda.gov/TXT alg 8, id 21705: The TTL of the RRset (600) exceeds the value of the Original TTL field of the RRSIG RR covering it (60). See RFC 4035, Sec. 2.2.
  • ustda.gov/A: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (23.211.61.66, 95.100.168.64, 95.100.175.65, 96.7.49.67, 184.26.160.64, 193.108.91.61, 2600:1401:2::3d, 2600:1408:1c::43, 2600:1480:7800::42, 2600:1480:b000::40, 2600:1480:f000::40, 2a02:26f0:67::41, UDP_-_EDNS0_4096_D_KN)
  • ustda.gov/AAAA: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (23.211.61.66, 95.100.168.64, 95.100.175.65, 96.7.49.67, 184.26.160.64, 193.108.91.61, 2600:1401:2::3d, 2600:1408:1c::43, 2600:1480:7800::42, 2600:1480:b000::40, 2600:1480:f000::40, 2a02:26f0:67::41, UDP_-_EDNS0_4096_D_KN)
  • ustda.gov/DNSKEY (alg 13, id 32001): The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (23.211.61.66, 95.100.168.64, 95.100.175.65, 96.7.49.67, 184.26.160.64, 193.108.91.61, 2600:1401:2::3d, 2600:1408:1c::43, 2600:1480:7800::42, 2600:1480:b000::40, 2600:1480:f000::40, 2a02:26f0:67::41, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • ustda.gov/DNSKEY (alg 13, id 61412): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (216.59.57.8, 216.59.60.8, 2602:ffe2:54::8, UDP_-_EDNS0_4096_D_KN)
  • ustda.gov/DNSKEY (alg 13, id 61412): The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (23.211.61.66, 95.100.168.64, 95.100.175.65, 96.7.49.67, 184.26.160.64, 193.108.91.61, 2600:1401:2::3d, 2600:1408:1c::43, 2600:1480:7800::42, 2600:1480:b000::40, 2600:1480:f000::40, 2a02:26f0:67::41, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • ustda.gov/DNSKEY (alg 13, id 62241): The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (23.211.61.66, 95.100.168.64, 95.100.175.65, 96.7.49.67, 184.26.160.64, 193.108.91.61, 2600:1401:2::3d, 2600:1408:1c::43, 2600:1480:7800::42, 2600:1480:b000::40, 2600:1480:f000::40, 2a02:26f0:67::41, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • ustda.gov/DNSKEY (alg 8, id 21705): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (23.211.61.66, 95.100.168.64, 95.100.175.65, 96.7.49.67, 184.26.160.64, 193.108.91.61, 2600:1401:2::3d, 2600:1408:1c::43, 2600:1480:7800::42, 2600:1480:b000::40, 2600:1480:f000::40, 2a02:26f0:67::41, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • ustda.gov/DNSKEY (alg 8, id 21705): The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (216.59.57.8, 216.59.60.8, 2602:ffe2:54::8, UDP_-_EDNS0_4096_D_KN)
  • ustda.gov/DNSKEY (alg 8, id 51215): The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (216.59.57.8, 216.59.60.8, 2602:ffe2:54::8, UDP_-_EDNS0_4096_D_KN)
  • ustda.gov/MX: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (216.59.57.8, 216.59.60.8, 2602:ffe2:54::8, UDP_-_EDNS0_4096_D_KN)
  • ustda.gov/MX: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (23.211.61.66, 95.100.168.64, 95.100.175.65, 96.7.49.67, 184.26.160.64, 193.108.91.61, 2600:1401:2::3d, 2600:1408:1c::43, 2600:1480:7800::42, 2600:1480:b000::40, 2600:1480:f000::40, 2a02:26f0:67::41, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • ustda.gov/NS: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (216.59.57.8, 216.59.60.8, 2602:ffe2:54::8, UDP_-_EDNS0_4096_D_KN)
  • ustda.gov/NS: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (23.211.61.66, 95.100.168.64, 95.100.175.65, 96.7.49.67, 184.26.160.64, 193.108.91.61, 2600:1401:2::3d, 2600:1408:1c::43, 2600:1480:7800::42, 2600:1480:b000::40, 2600:1480:f000::40, 2a02:26f0:67::41, UDP_-_EDNS0_4096_D_KN)
  • ustda.gov/NSEC3PARAM: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (23.211.61.66, 95.100.168.64, 95.100.175.65, 96.7.49.67, 184.26.160.64, 193.108.91.61, 2600:1401:2::3d, 2600:1408:1c::43, 2600:1480:7800::42, 2600:1480:b000::40, 2600:1480:f000::40, 2a02:26f0:67::41, UDP_-_EDNS0_4096_D_KN)
  • ustda.gov/SOA: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (216.59.57.8, 216.59.60.8, 2602:ffe2:54::8, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • ustda.gov/SOA: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (23.211.61.66, 95.100.168.64, 95.100.175.65, 96.7.49.67, 184.26.160.64, 193.108.91.61, 2600:1401:2::3d, 2600:1408:1c::43, 2600:1480:7800::42, 2600:1480:b000::40, 2600:1480:f000::40, 2a02:26f0:67::41, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • ustda.gov/TXT: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (216.59.57.8, 216.59.60.8, 2602:ffe2:54::8, UDP_-_EDNS0_4096_D_KN)
  • ustda.gov/TXT: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (23.211.61.66, 95.100.168.64, 95.100.175.65, 96.7.49.67, 184.26.160.64, 193.108.91.61, 2600:1401:2::3d, 2600:1408:1c::43, 2600:1480:7800::42, 2600:1480:b000::40, 2600:1480:f000::40, 2a02:26f0:67::41, UDP_-_EDNS0_4096_D_KN)
  • 23goa168fj.ustda.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • ustda.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • ustda.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • ustda.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
  • NSEC3 proving non-existence of ustda.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of ustda.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • ustda.gov/DNSKEY (alg 13, id 32001): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (216.59.57.8, 216.59.60.8, 2602:ffe2:54::8, UDP_-_EDNS0_4096_D_KN)
  • ustda.gov/DNSKEY (alg 13, id 62241): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (216.59.57.8, 216.59.60.8, 2602:ffe2:54::8, UDP_-_EDNS0_4096_D_KN)
  • ustda.gov/DNSKEY (alg 8, id 51215): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (23.211.61.66, 95.100.168.64, 95.100.175.65, 96.7.49.67, 184.26.160.64, 193.108.91.61, 2600:1401:2::3d, 2600:1408:1c::43, 2600:1480:7800::42, 2600:1480:b000::40, 2600:1480:f000::40, 2a02:26f0:67::41, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • 23goa168fj.ustda.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ustda.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ustda.gov/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