View on GitHub

DNSViz: A DNS visualization tool

frtibtest.gov

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

RRset statusRRset status

Bogus (4)
  • frtibtest.gov/MX
  • frtibtest.gov/NS
  • frtibtest.gov/SOA
  • frtibtest.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 9799)
  • frtibtest.gov/DS (alg 7, id 23496)
  • frtibtest.gov/DS (alg 8, id 62365)
  • gov/DNSKEY (alg 8, id 6229)
  • gov/DNSKEY (alg 8, id 7030)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
Non_existent (2)
  • frtibtest.gov/DNSKEY (alg 7, id 23496)
  • frtibtest.gov/DNSKEY (alg 8, id 62365)

Delegation statusDelegation status

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

NoticesNotices

Errors (22)
  • frtibtest.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186)
  • frtibtest.gov/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, UDP_-_NOEDNS_)
  • frtibtest.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (149.101.82.186, 149.101.182.185, 149.101.182.186, UDP_-_EDNS0_512_D_KN)
  • frtibtest.gov/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (149.101.82.185, 149.101.182.185, 149.101.182.186, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • frtibtest.gov/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.186, UDP_-_NOEDNS_)
  • frtibtest.gov/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (149.101.82.186, UDP_-_EDNS0_512_D_KN)
  • frtibtest.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (149.101.82.185, 149.101.82.186, 149.101.182.185, 149.101.182.186, UDP_-_EDNS0_4096_D_KN)
  • frtibtest.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (149.101.82.185, 149.101.82.186, 149.101.182.185, 149.101.182.186, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20, UDP_-_EDNS0_4096_D_N)
  • frtibtest.gov/SOA: No response was received from the server over TCP (tried 4 times). See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, TCP_-_EDNS0_4096_D_N)
  • frtibtest.gov/SOA: No response was received from the server over TCP (tried 6 times). See RFC 1035, Sec. 4.2. (149.101.182.185, TCP_-_EDNS0_4096_D_N)
  • frtibtest.gov/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.186, UDP_-_NOEDNS_)
  • frtibtest.gov/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (149.101.82.186, 149.101.182.185, 149.101.182.186, UDP_-_EDNS0_4096_D_KN)
  • frtibtest.gov/TXT: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.185, UDP_-_NOEDNS_)
  • gov to frtibtest.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. (149.101.82.185, 149.101.182.185, 149.101.182.186, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gov to frtibtest.gov: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no DS RR matched a DNSKEY with algorithm 7 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (149.101.82.185, 149.101.182.185, 149.101.182.186, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gov to frtibtest.gov: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (149.101.82.185, 149.101.182.185, 149.101.182.186, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • frtibtest.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • frtibtest.gov/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • ex3w6h09pa.frtibtest.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • frtibtest.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • frtibtest.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • frtibtest.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (13)
  • frtibtest.gov/DS (alg 7, id 23496): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • frtibtest.gov/DS (alg 7, id 23496): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • frtibtest.gov/DS (alg 7, id 23496): 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.
  • frtibtest.gov/DS (alg 7, id 23496): 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.
  • frtibtest.gov/DS (alg 8, id 62365): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • frtibtest.gov/DS (alg 8, id 62365): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • frtibtest.gov/DS (alg 8, id 62365): 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.
  • frtibtest.gov/DS (alg 8, id 62365): 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.
  • frtibtest.gov/MX: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (149.101.182.185, 149.101.182.186, UDP_-_EDNS0_4096_D_KN)
  • frtibtest.gov/SOA: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (149.101.182.185, UDP_-_EDNS0_4096_D_KN)
  • frtibtest.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • frtibtest.gov/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • frtibtest.gov/CNAME 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