View on GitHub

DNSViz: A DNS visualization tool

whitehouseconferenceonaging.gov

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

RRset statusRRset status

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

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (14)
  • ./DNSKEY (alg 8, id 18733)
  • ./DNSKEY (alg 8, id 20326)
  • gov/DNSKEY (alg 8, id 261)
  • gov/DNSKEY (alg 8, id 56278)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • whitehouseconferenceonaging.gov/DNSKEY (alg 8, id 19207)
  • whitehouseconferenceonaging.gov/DNSKEY (alg 8, id 20285)
  • whitehouseconferenceonaging.gov/DNSKEY (alg 8, id 21523)
  • whitehouseconferenceonaging.gov/DNSKEY (alg 8, id 54550)
  • whitehouseconferenceonaging.gov/DS (alg 8, id 19207)
  • whitehouseconferenceonaging.gov/DS (alg 8, id 19207)
  • whitehouseconferenceonaging.gov/DS (alg 8, id 20285)
  • whitehouseconferenceonaging.gov/DS (alg 8, id 20285)

Delegation statusDelegation status

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

NoticesNotices

Errors (3)
  • whitehouseconferenceonaging.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2607:f220:0:1::2a, 2607:f220:0:1::2b, 2607:f220:0:1::2c, 2607:f220:0:1::2d)
  • whitehouseconferenceonaging.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:f220:0:1::2a, 2607:f220:0:1::2b, 2607:f220:0:1::2c, 2607:f220:0:1::2d, UDP_-_NOEDNS_)
  • whitehouseconferenceonaging.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:f220:0:1::2a, 2607:f220:0:1::2b, 2607:f220:0:1::2c, 2607:f220:0:1::2d, UDP_-_NOEDNS_)
Warnings (8)
  • whitehouseconferenceonaging.gov/DS (alg 8, id 19207): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • whitehouseconferenceonaging.gov/DS (alg 8, id 19207): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • whitehouseconferenceonaging.gov/DS (alg 8, id 19207): 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.
  • whitehouseconferenceonaging.gov/DS (alg 8, id 19207): 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.
  • whitehouseconferenceonaging.gov/DS (alg 8, id 20285): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • whitehouseconferenceonaging.gov/DS (alg 8, id 20285): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • whitehouseconferenceonaging.gov/DS (alg 8, id 20285): 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.
  • whitehouseconferenceonaging.gov/DS (alg 8, id 20285): 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.

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