View on GitHub

DNSViz: A DNS visualization tool

atf.gov

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

RRset statusRRset status

Secure (7)
  • atf.gov/A
  • atf.gov/AAAA
  • atf.gov/MX
  • atf.gov/NS
  • atf.gov/NSEC3PARAM
  • atf.gov/SOA
  • atf.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (13)
  • ./DNSKEY (alg 8, id 18733)
  • ./DNSKEY (alg 8, id 20326)
  • atf.gov/DNSKEY (alg 8, id 32410)
  • atf.gov/DNSKEY (alg 8, id 4971)
  • atf.gov/DNSKEY (alg 8, id 62134)
  • atf.gov/DNSKEY (alg 8, id 62154)
  • atf.gov/DS (alg 8, id 32410)
  • atf.gov/DS (alg 8, id 32410)
  • atf.gov/DS (alg 8, id 62134)
  • atf.gov/DS (alg 8, id 62134)
  • gov/DNSKEY (alg 8, id 56278)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

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

NoticesNotices

Errors (8)
  • atf.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (149.101.180.157)
  • atf.gov/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.180.157, UDP_-_EDNS0_4096_D_KN)
  • atf.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (149.101.180.157, UDP_-_EDNS0_512_D_KN)
  • atf.gov/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (149.101.180.157, UDP_-_EDNS0_512_D_KN)
  • atf.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (149.101.180.157, TCP_-_EDNS0_4096_D_N)
  • g43wz6na2v.atf.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • atf.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • atf.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
  • atf.gov/DS (alg 8, id 32410): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • atf.gov/DS (alg 8, id 32410): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • atf.gov/DS (alg 8, id 32410): 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.
  • atf.gov/DS (alg 8, id 32410): 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.
  • atf.gov/DS (alg 8, id 62134): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • atf.gov/DS (alg 8, id 62134): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • atf.gov/DS (alg 8, id 62134): 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.
  • atf.gov/DS (alg 8, id 62134): 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.
  • g43wz6na2v.atf.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • atf.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