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

Bogus (1)
  • srs.gov/SOA
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 (17)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 47671)
  • gov/DNSKEY (alg 8, id 2706)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • srs.gov/DNSKEY (alg 7, id 15014)
  • srs.gov/DNSKEY (alg 7, id 42704)
  • srs.gov/DNSKEY (alg 7, id 64469)
  • srs.gov/DNSKEY (alg 7, id 7755)
  • srs.gov/DNSKEY (alg 8, id 17004)
  • srs.gov/DNSKEY (alg 8, id 30318)
  • srs.gov/DNSKEY (alg 8, id 38880)
  • srs.gov/DNSKEY (alg 8, id 9547)
  • 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 (48)
  • RRSIG srs.gov/DNSKEY alg 7, id 42704: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 42704: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 42704: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 42704: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 42704: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 42704: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 42704: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 42704: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 7755: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 7755: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 7755: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 7755: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 7755: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 7755: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 7755: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 7, id 7755: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 8, id 17004: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 8, id 17004: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 8, id 17004: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 8, id 17004: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 8, id 17004: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 8, id 17004: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 8, id 17004: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 8, id 17004: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 8, id 9547: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 8, id 9547: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 8, id 9547: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 8, id 9547: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 8, id 9547: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 8, id 9547: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 8, id 9547: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/DNSKEY alg 8, id 9547: The Signature Expiration field of the RRSIG RR (2022-05-29 11:10:26+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/MX alg 7, id 42704: The Signature Expiration field of the RRSIG RR (2022-05-29 11:39:08+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/MX alg 8, id 17004: The Signature Expiration field of the RRSIG RR (2022-05-29 11:39:08+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/NS alg 7, id 42704: The Signature Expiration field of the RRSIG RR (2022-05-29 11:34:01+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/NS alg 8, id 17004: The Signature Expiration field of the RRSIG RR (2022-05-29 11:34:01+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/NSEC3PARAM alg 7, id 42704: The Signature Expiration field of the RRSIG RR (2022-05-29 11:17:39+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/NSEC3PARAM alg 8, id 17004: The Signature Expiration field of the RRSIG RR (2022-05-29 11:17:39+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/SOA alg 7, id 42704: The Signature Expiration field of the RRSIG RR (2022-05-29 12:04:52+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/SOA alg 8, id 17004: The Signature Expiration field of the RRSIG RR (2022-05-29 12:04:52+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/TXT alg 7, id 42704: The Signature Expiration field of the RRSIG RR (2022-05-29 11:34:01+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG srs.gov/TXT alg 8, id 17004: The Signature Expiration field of the RRSIG RR (2022-05-29 11:34:01+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • gov to srs.gov: 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. (192.188.22.22, 192.188.22.52, 2001:400:ffff:ffff:ffff::4444, 2001:400:ffff:ffff:ffff::8052, TCP_-_EDNS0_4096_D_KN)
  • srs.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • iyjfv5lrb4.srs.gov/A 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.
  • srs.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (55)
  • RRSIG srs.gov/DNSKEY alg 7, id 42704: 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 42704: 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 42704: 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 42704: 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 42704: 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 42704: 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 42704: 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 42704: 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 42704: 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 42704: 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 42704: 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 42704: 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 42704: 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 42704: 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 42704: 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 42704: 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/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 42704: 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 42704: 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 42704: 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 42704: 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 42704: 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 42704: 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 42704: 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 42704: 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 42704: 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 42704: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • 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.
  • iyjfv5lrb4.srs.gov/A 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.
  • 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