View on GitHub

DNSViz: A DNS visualization tool

hud.gov

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

RRset statusRRset status

Bogus (1)
  • hud.gov/SOA
Secure (6)
  • hud.gov/A
  • hud.gov/AAAA
  • hud.gov/MX
  • hud.gov/NS
  • hud.gov/SOA
  • hud.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (1)
  • hud.gov/DNSKEY (alg 7, id 3542)
Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • ./DNSKEY (alg 8, id 48903)
  • gov/DNSKEY (alg 8, id 40176)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • hud.gov/DNSKEY (alg 7, id 1593)
  • hud.gov/DNSKEY (alg 7, id 41438)
  • hud.gov/DNSKEY (alg 7, id 8255)
  • 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 (28)
  • RRSIG hud.gov/A alg 7, id 3542: The Signature Expiration field of the RRSIG RR (2020-07-05 17:50:09+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG hud.gov/AAAA alg 7, id 3542: The Signature Expiration field of the RRSIG RR (2020-07-05 17:50:09+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 1593: The Signature Expiration field of the RRSIG RR (2020-07-05 17:50:09+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 1593: The Signature Expiration field of the RRSIG RR (2020-07-05 17:50:09+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 1593: The Signature Expiration field of the RRSIG RR (2020-07-05 17:50:09+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 1593: The Signature Expiration field of the RRSIG RR (2020-07-05 17:50:09+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 3542: The Signature Expiration field of the RRSIG RR (2020-07-05 17:50:09+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 3542: The Signature Expiration field of the RRSIG RR (2020-07-05 17:50:09+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 3542: The Signature Expiration field of the RRSIG RR (2020-07-05 17:50:09+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 3542: The Signature Expiration field of the RRSIG RR (2020-07-05 17:50:09+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG hud.gov/MX alg 7, id 3542: The Signature Expiration field of the RRSIG RR (2020-07-05 17:50:09+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG hud.gov/NS alg 7, id 3542: The Signature Expiration field of the RRSIG RR (2020-07-05 17:50:09+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG hud.gov/SOA alg 7, id 3542: The Signature Expiration field of the RRSIG RR (2020-07-05 17:50:09+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG hud.gov/TXT alg 7, id 3542: The Signature Expiration field of the RRSIG RR (2020-07-05 17:50:09+00:00) is 2 days in the past. See RFC 4035, Sec. 5.3.1.
  • gov to hud.gov: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (170.97.67.16, 170.97.67.250, 170.97.67.251, 170.97.167.91, 2620:0:c91::67:250, 2620:0:c91::67:251, UDP_-_EDNS0_4096_D_K)
  • gov/DS (alg 8, id 7698): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • hud.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (2620:0:c91::67:250, 2620:0:c91::67:251)
  • hud.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2620:0:c92::167:45, 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. (2620:0:c92::167:45, 2620:0:c92::167:91, UDP_-_NOEDNS_)
  • hud.gov/DNSKEY (alg 7, id 3542): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (170.97.167.16, 170.97.167.45, UDP_-_EDNS0_4096_D_K)
  • hud.gov/DS (alg 7, id 1593): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • hud.gov/DS (alg 7, id 1593): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • hud.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:0:c92::167:45, 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:c91::67:251, TCP_-_EDNS0_4096_D)
  • 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.
  • vua29e146c.hud.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (40)
  • RRSIG hud.gov/A alg 7, id 3542: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/A alg 7, id 8255: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/AAAA alg 7, id 3542: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/AAAA alg 7, id 8255: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 1593: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 1593: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 1593: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 1593: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 1593: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 1593: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 1593: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 3542: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 3542: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 3542: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 3542: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 8255: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 8255: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/DNSKEY alg 7, id 8255: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/MX alg 7, id 3542: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/MX alg 7, id 8255: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/NS alg 7, id 3542: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/NS alg 7, id 8255: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/SOA alg 7, id 3542: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/SOA alg 7, id 8255: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/TXT alg 7, id 3542: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hud.gov/TXT alg 7, id 8255: DNSSEC specification recommends not 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 ns2.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.
  • 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.
  • hud.gov/A: 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.167.91, UDP_-_EDNS0_4096_D_K)
  • 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.167.16, UDP_-_EDNS0_4096_D_K)
  • 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/SOA: 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.167.45, UDP_-_EDNS0_4096_D_K)
  • 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.
  • vua29e146c.hud.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