View on GitHub

DNSViz: A DNS visualization tool

hud.gov

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

RRset statusRRset status

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

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 20826)
  • gov/DNSKEY (alg 8, id 261)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • hud.gov/DNSKEY (alg 7, id 1593)
  • hud.gov/DNSKEY (alg 7, id 30783)
  • hud.gov/DNSKEY (alg 7, id 52493)
  • hud.gov/DS (alg 7, id 1593)
  • hud.gov/DS (alg 7, id 1593)

Delegation statusDelegation status

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

NoticesNotices

Errors (14)
  • hud.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (170.97.167.16, 170.97.167.45, 170.97.167.91, 2620:0:c92::167:91)
  • hud.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (170.97.167.16, 170.97.167.45, 170.97.167.91, 2620:0:c92::167:45, 2620:0:c92::167:91, UDP_-_NOEDNS_)
  • hud.gov/AAAA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:0:c92::167:45, UDP_-_NOEDNS_)
  • hud.gov/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:0:c92::167:45, UDP_-_NOEDNS_)
  • hud.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (170.97.67.251, 2620:0:c92::167:45, UDP_-_EDNS0_512_D_KN)
  • hud.gov/MX: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:0:c91::67:250, TCP_-_EDNS0_4096_D_KN)
  • hud.gov/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (170.97.67.16, 170.97.67.251, 2620:0:c91::67:250, UDP_-_EDNS0_512_D_KN)
  • hud.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (170.97.167.16, 170.97.167.45, 170.97.167.91, 2620:0:c92::167:91, UDP_-_NOEDNS_)
  • hud.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (2620:0:c91::67:250, 2620:0:c92::167:45, TCP_-_EDNS0_4096_D_N)
  • hud.gov/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:0:c92::167:45, UDP_-_NOEDNS__0x20)
  • hud.gov/TXT: No response was received from the server over TCP (tried 7 times). See RFC 1035, Sec. 4.2. (170.97.67.16, TCP_-_EDNS0_4096_D_KN)
  • i2uq5kyz4v.hud.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • hud.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • hud.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (30)
  • RRSIG hud.gov/A alg 7, id 30783: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/AAAA alg 7, id 30783: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 1593: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 1593: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 1593: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 30783: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 30783: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 30783: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/MX alg 7, id 30783: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/NS alg 7, id 30783: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/NSEC3PARAM alg 7, id 30783: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/SOA alg 7, id 30783: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/TXT alg 7, id 30783: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • gov to hud.gov: Authoritative AAAA records exist for ns1.hud.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • gov to hud.gov: Authoritative AAAA records exist for ns3.hud.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • gov to hud.gov: Authoritative AAAA records exist for ns4.hud.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • hud.gov/A: 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. (170.97.67.251, UDP_-_EDNS0_4096_D_KN)
  • hud.gov/AAAA: 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. (170.97.67.250, UDP_-_EDNS0_4096_D_KN)
  • hud.gov/DNSKEY (alg 7, id 1593): 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. (170.97.67.250, UDP_-_EDNS0_4096_D_KN)
  • hud.gov/DNSKEY (alg 7, id 30783): 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. (170.97.67.250, UDP_-_EDNS0_4096_D_KN)
  • hud.gov/DNSKEY (alg 7, id 52493): 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. (170.97.67.250, UDP_-_EDNS0_4096_D_KN)
  • hud.gov/DS (alg 7, id 1593): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • hud.gov/DS (alg 7, id 1593): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • hud.gov/DS (alg 7, id 1593): 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.
  • hud.gov/DS (alg 7, id 1593): 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.
  • hud.gov/NS: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (2620:0:c92::167:45, UDP_-_EDNS0_4096_D_KN)
  • hud.gov/NSEC3PARAM: 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. (2620:0:c91::67:250, UDP_-_EDNS0_4096_D_KN)
  • i2uq5kyz4v.hud.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • hud.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • hud.gov/DNSKEY 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