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

Secure (4)
  • frtibtest.gov/NS
  • frtibtest.gov/NSEC3PARAM
  • frtibtest.gov/SOA
  • frtibtest.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (16)
  • ./DNSKEY (alg 8, id 14748)
  • ./DNSKEY (alg 8, id 20326)
  • frtibtest.gov/DNSKEY (alg 7, id 19595)
  • frtibtest.gov/DNSKEY (alg 7, id 23496)
  • frtibtest.gov/DNSKEY (alg 7, id 29594)
  • frtibtest.gov/DNSKEY (alg 8, id 39291)
  • frtibtest.gov/DNSKEY (alg 8, id 480)
  • frtibtest.gov/DNSKEY (alg 8, id 51441)
  • frtibtest.gov/DNSKEY (alg 8, id 62365)
  • frtibtest.gov/DS (alg 7, id 23496)
  • frtibtest.gov/DS (alg 7, id 23496)
  • frtibtest.gov/DS (alg 8, id 62365)
  • frtibtest.gov/DS (alg 8, id 62365)
  • gov/DNSKEY (alg 8, id 6229)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

Secure (2)
  • . to gov
  • gov to frtibtest.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, 149.101.182.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.186, 149.101.182.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.185, 149.101.82.186, 149.101.182.185, 149.101.182.186, UDP_-_EDNS0_512_D_KN)
  • frtibtest.gov/MX: No response was received from the server over TCP (tried 2 times). See RFC 1035, Sec. 4.2. (149.101.182.185, TCP_-_EDNS0_4096_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.185, 149.101.82.186, 149.101.182.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: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 10 times) with the DO bit set. See RFC 4035, Sec. 3.2.1. (149.101.82.185, 149.101.182.186, UDP_-_EDNS0_4096_)
  • frtibtest.gov/NS: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 11 times) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (149.101.82.186, UDP_-_NOEDNS_)
  • frtibtest.gov/NS: No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). See RFC 6891, Sec. 6.1.4. (149.101.82.185, 149.101.182.186, UDP_-_EDNS0_4096_D_KN)
  • frtibtest.gov/NS: No response was received from the server over UDP (tried 11 times) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (149.101.82.186, UDP_-_EDNS0_4096_D_KN)
  • frtibtest.gov/NS: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (149.101.82.185, 149.101.82.186, 149.101.182.186, UDP_-_EDNS0_4096_D_KN)
  • frtibtest.gov/NSEC3PARAM: 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, 149.101.182.186, UDP_-_NOEDNS_)
  • frtibtest.gov/SOA: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, 149.101.182.186, TCP_-_EDNS0_4096_D_KN, TCP_-_EDNS0_4096_D_KN_0x20)
  • frtibtest.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (149.101.182.186, TCP_-_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 UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.185, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • 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, 149.101.82.186, 149.101.182.186, UDP_-_NOEDNS_)
  • 30i1zturc4.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/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • frtibtest.gov/AAAA 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.
Warnings (46)
  • RRSIG frtibtest.gov/DNSKEY alg 7, id 19595: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/DNSKEY alg 7, id 19595: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/DNSKEY alg 7, id 19595: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/DNSKEY alg 7, id 19595: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/DNSKEY alg 7, id 19595: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/DNSKEY alg 7, id 19595: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/DNSKEY alg 7, id 19595: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/DNSKEY alg 7, id 23496: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/DNSKEY alg 7, id 23496: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/DNSKEY alg 7, id 23496: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/DNSKEY alg 7, id 23496: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/DNSKEY alg 7, id 23496: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/DNSKEY alg 7, id 23496: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/DNSKEY alg 7, id 23496: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/DNSKEY alg 7, id 29594: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/DNSKEY alg 7, id 29594: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/DNSKEY alg 7, id 29594: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/DNSKEY alg 7, id 29594: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/DNSKEY alg 7, id 29594: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/DNSKEY alg 7, id 29594: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/DNSKEY alg 7, id 29594: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/NS alg 7, id 19595: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/NS alg 7, id 29594: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/NSEC3PARAM alg 7, id 19595: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/NSEC3PARAM alg 7, id 29594: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/SOA alg 7, id 19595: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/SOA alg 7, id 19595: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/SOA alg 7, id 29594: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/SOA alg 7, id 29594: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/TXT alg 7, id 19595: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG frtibtest.gov/TXT alg 7, id 29594: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • 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/NS: 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, UDP_-_EDNS0_4096_D_KN)
  • frtibtest.gov/TXT: 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, UDP_-_EDNS0_4096_D_KN)
  • frtibtest.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 30i1zturc4.frtibtest.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • frtibtest.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • frtibtest.gov/AAAA 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