View on GitHub

DNSViz: A DNS visualization tool

fha.gov

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

RRset statusRRset status

Secure (6)
  • fha.gov/A
  • fha.gov/AAAA
  • fha.gov/NS
  • fha.gov/NSEC3PARAM
  • fha.gov/SOA
  • fha.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 30903)
  • fha.gov/DNSKEY (alg 7, id 16275)
  • fha.gov/DNSKEY (alg 7, id 2850)
  • fha.gov/DNSKEY (alg 7, id 4989)
  • fha.gov/DS (alg 7, id 4989)
  • fha.gov/DS (alg 7, id 4989)
  • gov/DNSKEY (alg 8, id 10104)
  • gov/DNSKEY (alg 8, id 49735)
  • gov/DNSKEY (alg 8, id 64280)
  • gov/DS (alg 8, id 64280)

Delegation statusDelegation status

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

NoticesNotices

Errors (8)
  • fha.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (170.97.67.16, 170.97.67.250, 170.97.67.251, 170.97.167.16, 170.97.167.45, 170.97.167.91)
  • fha.gov/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (170.97.67.16, 170.97.67.250, 170.97.67.251, 170.97.167.16, 170.97.167.45, 170.97.167.91, UDP_-_EDNS0_4096_D_KN)
  • fha.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (170.97.67.16, 170.97.67.250, 170.97.67.251, 170.97.167.16, 170.97.167.45, 170.97.167.91, TCP_-_EDNS0_4096_D_N)
  • fha.gov/TXT: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (170.97.67.16, 170.97.67.250, 170.97.67.251, 170.97.167.16, 170.97.167.45, 170.97.167.91, TCP_-_EDNS0_4096_D_KN)
  • fha.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • fha.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • as2hy76lpo.fha.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • fha.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (20)
  • RRSIG fha.gov/A alg 7, id 16275: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fha.gov/AAAA alg 7, id 16275: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fha.gov/DNSKEY alg 7, id 16275: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fha.gov/DNSKEY alg 7, id 16275: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fha.gov/DNSKEY alg 7, id 16275: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fha.gov/DNSKEY alg 7, id 4989: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fha.gov/DNSKEY alg 7, id 4989: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fha.gov/DNSKEY alg 7, id 4989: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fha.gov/NS alg 7, id 16275: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fha.gov/NSEC3PARAM alg 7, id 16275: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fha.gov/SOA alg 7, id 16275: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG fha.gov/TXT alg 7, id 16275: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • fha.gov/DS (alg 7, id 4989): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • fha.gov/DS (alg 7, id 4989): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • fha.gov/DS (alg 7, id 4989): 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.
  • fha.gov/DS (alg 7, id 4989): 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 to fha.gov: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the gov zone): ns3.hud.gov, ns2.hud.gov, ns4.hud.gov, ns1.hud.gov See RFC 1034, Sec. 4.2.2.
  • fha.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • fha.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • fha.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