View on GitHub

DNSViz: A DNS visualization tool

ttb.gov

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

RRset statusRRset status

Secure (5)
  • ttb.gov/MX
  • ttb.gov/NS
  • ttb.gov/SOA
  • ttb.gov/SOA
  • ttb.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 42351)
  • gov/DNSKEY (alg 8, id 15489)
  • gov/DNSKEY (alg 8, id 27306)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • ttb.gov/DNSKEY (alg 7, id 38340)
  • ttb.gov/DNSKEY (alg 8, id 57648)
  • ttb.gov/DS (alg 7, id 38340)
  • ttb.gov/DS (alg 7, id 38340)

Delegation statusDelegation status

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

NoticesNotices

Errors (14)
  • ttb.gov/MX: The DNSKEY RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (164.95.95.155, 166.123.208.249, 2610:108:3000:100a::155, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_KN)
  • ttb.gov/MX: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (164.95.95.155, 166.123.208.249, 2610:108:3000:100a::155, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_KN)
  • ttb.gov/NS: The DNSKEY RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (164.95.95.155, 166.123.208.249, 2610:108:3000:100a::155, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_KN)
  • ttb.gov/NS: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (164.95.95.155, 166.123.208.249, 2610:108:3000:100a::155, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_KN)
  • ttb.gov/SOA: The DNSKEY RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (164.95.95.155, 2610:108:3000:100a::155, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • ttb.gov/SOA: The DNSKEY RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (166.123.208.249, 2610:108:4000:100a::249, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • ttb.gov/SOA: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (164.95.95.155, 2610:108:3000:100a::155, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • ttb.gov/SOA: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (166.123.208.249, 2610:108:4000:100a::249, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • ttb.gov/TXT: The DNSKEY RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (164.95.95.155, 166.123.208.249, 2610:108:3000:100a::155, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_KN)
  • ttb.gov/TXT: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (164.95.95.155, 166.123.208.249, 2610:108:3000:100a::155, 2610:108:4000:100a::249, UDP_-_EDNS0_4096_D_KN)
  • ttb.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • ttb.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • ttb.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • l7agzodcn8.ttb.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (25)
  • RRSIG ttb.gov/DNSKEY alg 7, id 38340: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ttb.gov/DNSKEY alg 7, id 38340: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ttb.gov/DNSKEY alg 7, id 38340: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ttb.gov/DNSKEY alg 7, id 38340: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ttb.gov/DNSKEY alg 7, id 38340: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ttb.gov/DNSKEY alg 7, id 38340: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ttb.gov/DNSKEY alg 7, id 38340: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ttb.gov/DNSKEY alg 7, id 38340: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): 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.
  • gov/DS (alg 8, id 7698): 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.
  • gov/DS (alg 8, id 7698): 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. (2001:7fe::53, UDP_-_EDNS0_4096_D_KN)
  • gov/DS (alg 8, id 7698): 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. (2001:7fe::53, UDP_-_EDNS0_4096_D_KN)
  • gov/DS (alg 8, id 7698): 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. (2001:7fe::53, UDP_-_EDNS0_4096_D_KN)
  • gov/DS (alg 8, id 7698): 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. (2001:7fe::53, UDP_-_EDNS0_4096_D_KN)
  • ttb.gov/DS (alg 7, id 38340): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ttb.gov/DS (alg 7, id 38340): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ttb.gov/DS (alg 7, id 38340): 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.
  • ttb.gov/DS (alg 7, id 38340): 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.
  • ttb.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ttb.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ttb.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ttb.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • l7agzodcn8.ttb.gov/A 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