View on GitHub

DNSViz: A DNS visualization tool

research.gov

Updated: 2024-01-17 23:27:02 UTC (308 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

Secure (5)
  • research.gov/A
  • research.gov/AAAA
  • research.gov/NS
  • research.gov/SOA
  • research.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (13)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 30903)
  • gov/DNSKEY (alg 8, id 10104)
  • gov/DNSKEY (alg 8, id 49735)
  • gov/DNSKEY (alg 8, id 64280)
  • gov/DS (alg 8, id 64280)
  • research.gov/DNSKEY (alg 5, id 20524)
  • research.gov/DNSKEY (alg 5, id 42147)
  • research.gov/DNSKEY (alg 5, id 65521)
  • research.gov/DS (alg 5, id 20524)
  • research.gov/DS (alg 5, id 20524)
  • research.gov/DS (alg 5, id 65521)
  • research.gov/DS (alg 5, id 65521)

Delegation statusDelegation status

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

NoticesNotices

Errors (4)
  • research.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2620:10f:6001:2::55, 2620:10f:6001:2::56)
  • research.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:10f:6001:2::55, 2620:10f:6001:2::56, UDP_-_NOEDNS_)
  • research.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:10f:6001:2::55, 2620:10f:6001:2::56, UDP_-_NOEDNS_)
  • 6n10xvhq3z.research.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (27)
  • RRSIG research.gov/A alg 5, id 42147: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG research.gov/AAAA alg 5, id 42147: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG research.gov/DNSKEY alg 5, id 20524: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG research.gov/DNSKEY alg 5, id 20524: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG research.gov/DNSKEY alg 5, id 20524: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG research.gov/DNSKEY alg 5, id 42147: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG research.gov/DNSKEY alg 5, id 42147: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG research.gov/DNSKEY alg 5, id 42147: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG research.gov/DNSKEY alg 5, id 65521: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG research.gov/DNSKEY alg 5, id 65521: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG research.gov/DNSKEY alg 5, id 65521: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG research.gov/NS alg 5, id 42147: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG research.gov/SOA alg 5, id 42147: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG research.gov/TXT alg 5, id 42147: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • research.gov/DS (alg 5, id 20524): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • research.gov/DS (alg 5, id 20524): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • research.gov/DS (alg 5, id 20524): 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.
  • research.gov/DS (alg 5, id 20524): 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.
  • research.gov/DS (alg 5, id 65521): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • research.gov/DS (alg 5, id 65521): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • research.gov/DS (alg 5, id 65521): 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.
  • research.gov/DS (alg 5, id 65521): 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.
  • research.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • research.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • research.gov/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 6n10xvhq3z.research.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • research.gov/MX 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