View on GitHub

DNSViz: A DNS visualization tool

gatrees.gov

Updated: 2024-07-15 00:17:55 UTC (87 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

Bogus (3)
  • gatrees.gov/A
  • gatrees.gov/NS
  • gatrees.gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20038)
  • ./DNSKEY (alg 8, id 20326)
  • gatrees.gov/DS (alg 5, id 52264)
  • gov/DNSKEY (alg 13, id 2536)
  • gov/DNSKEY (alg 13, id 35496)
  • gov/DS (alg 13, id 2536)
Non_existent (1)
  • gatrees.gov/DNSKEY (alg 5, id 52264)

Delegation statusDelegation status

Bogus (1)
  • gov to gatrees.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (14)
  • gatrees.gov/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (167.194.81.235, 167.195.30.105, UDP_-_EDNS0_4096_D_KN)
  • gatrees.gov/CDNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (167.194.81.235, 167.195.30.105, UDP_-_NOEDNS_)
  • gatrees.gov/CDS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (167.194.81.235, 167.195.30.105, UDP_-_NOEDNS_)
  • gatrees.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (167.194.81.235, 167.195.30.105, UDP_-_EDNS0_4096_D_KN)
  • gatrees.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (167.194.81.235, 167.195.30.105, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • gov to gatrees.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. (167.194.81.235, 167.195.30.105, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gov to gatrees.gov: The DS RRset for the zone included algorithm 5 (RSASHA1), but no DS RR matched a DNSKEY with algorithm 5 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (167.194.81.235, 167.195.30.105, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • l7mt8.udjpr.gatrees.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • gatrees.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • gatrees.gov/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • gatrees.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • gatrees.gov/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
  • gatrees.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • gatrees.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
  • gatrees.gov/DS (alg 5, id 52264): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gatrees.gov/DS (alg 5, id 52264): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gatrees.gov/DS (alg 5, id 52264): 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.
  • gatrees.gov/DS (alg 5, id 52264): 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.

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