View on GitHub

DNSViz: A DNS visualization tool

srs.gov

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

RRset statusRRset status

Secure (5)
  • srs.gov/MX
  • srs.gov/NS
  • srs.gov/NSEC3PARAM
  • srs.gov/SOA
  • srs.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (22)
  • ./DNSKEY (alg 8, id 14748)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26838)
  • gov/DNSKEY (alg 8, id 57735)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • srs.gov/DNSKEY (alg 7, id 28694)
  • srs.gov/DNSKEY (alg 7, id 39636)
  • srs.gov/DNSKEY (alg 7, id 43880)
  • srs.gov/DNSKEY (alg 7, id 62151)
  • srs.gov/DNSKEY (alg 7, id 7755)
  • srs.gov/DNSKEY (alg 8, id 12213)
  • srs.gov/DNSKEY (alg 8, id 8775)
  • srs.gov/DNSKEY (alg 8, id 9547)
  • srs.gov/DS (alg 7, id 39636)
  • srs.gov/DS (alg 7, id 39636)
  • srs.gov/DS (alg 7, id 62151)
  • srs.gov/DS (alg 7, id 62151)
  • srs.gov/DS (alg 7, id 7755)
  • srs.gov/DS (alg 7, id 7755)
  • srs.gov/DS (alg 8, id 9547)
  • srs.gov/DS (alg 8, id 9547)

Delegation statusDelegation status

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

NoticesNotices

Errors (53)
  • RRSIG srs.gov/DNSKEY alg 7, id 28694: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 28694: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 28694: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 28694: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 28694: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 28694: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 28694: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 28694: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 39636: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 39636: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 39636: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 39636: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 39636: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 39636: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 39636: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 39636: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 62151: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 62151: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 62151: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 62151: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 62151: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 62151: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 62151: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 62151: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 7755: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 7755: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 7755: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 7755: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 7755: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 7755: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 7755: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 7, id 7755: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 8, id 8775: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 8, id 8775: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 8, id 8775: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 8, id 8775: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 8, id 8775: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 8, id 8775: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 8, id 8775: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 8, id 8775: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 8, id 9547: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 8, id 9547: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 8, id 9547: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 8, id 9547: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 8, id 9547: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 8, id 9547: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 8, id 9547: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG srs.gov/DNSKEY alg 8, id 9547: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 3 days after it expires at 2021-09-28 23:51:14+00:00. See RFC 4035, Sec. 5.3.3.
  • srs.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • srs.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • srs.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • 2hw3uza4sk.srs.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • srs.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (58)
  • RRSIG srs.gov/DNSKEY alg 7, id 28694: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 28694: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 28694: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 28694: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 28694: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 28694: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 28694: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 28694: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 39636: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 39636: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 39636: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 39636: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 39636: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 39636: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 39636: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 39636: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 62151: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 62151: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 62151: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 62151: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 62151: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 62151: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 62151: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 62151: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 7755: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 7755: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 7755: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 7755: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 7755: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 7755: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 7755: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 7755: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/MX alg 7, id 28694: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/NS alg 7, id 28694: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/NSEC3PARAM alg 7, id 28694: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/SOA alg 7, id 28694: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG srs.gov/TXT alg 7, id 28694: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • srs.gov/DS (alg 7, id 39636): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • srs.gov/DS (alg 7, id 39636): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • srs.gov/DS (alg 7, id 39636): 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.
  • srs.gov/DS (alg 7, id 39636): 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.
  • srs.gov/DS (alg 7, id 62151): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • srs.gov/DS (alg 7, id 62151): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • srs.gov/DS (alg 7, id 62151): 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.
  • srs.gov/DS (alg 7, id 62151): 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.
  • srs.gov/DS (alg 7, id 7755): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • srs.gov/DS (alg 7, id 7755): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • srs.gov/DS (alg 7, id 7755): 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.
  • srs.gov/DS (alg 7, id 7755): 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.
  • srs.gov/DS (alg 8, id 9547): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • srs.gov/DS (alg 8, id 9547): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • srs.gov/DS (alg 8, id 9547): 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.
  • srs.gov/DS (alg 8, id 9547): 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.
  • srs.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • srs.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • srs.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 2hw3uza4sk.srs.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • srs.gov/DNSKEY 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