View on GitHub

DNSViz: A DNS visualization tool

nlm.gov

Updated: 2023-05-22 11:53:06 UTC (366 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Secure (6)
  • nlm.gov/A
  • nlm.gov/AAAA
  • nlm.gov/MX
  • nlm.gov/NS
  • nlm.gov/SOA
  • nlm.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • gov/DNSKEY (alg 8, id 50011)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • nlm.gov/DNSKEY (alg 8, id 16604)
  • nlm.gov/DNSKEY (alg 8, id 38058)
  • nlm.gov/DS (alg 8, id 16604)

Delegation statusDelegation status

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

NoticesNotices

Errors (3)
  • nlm.gov zone: The server(s) were not responsive to queries over TCP. (2607:f220:41e:7055::72, 2607:f220:41e:7055::128)
  • nlm.gov/MX: No response was received from the server over TCP (tried 12 times). (2607:f220:41e:7055::72, 2607:f220:41e:7055::128, TCP_-_EDNS0_4096_D_KN)
  • nlm.gov/SOA: No response was received from the server over TCP (tried 3 times). (2607:f220:41e:7055::72, 2607:f220:41e:7055::128, TCP_-_EDNS0_4096_D_N)
Warnings (10)
  • gov to nlm.gov: Authoritative AAAA records exist for lhcns1.nlm.nih.gov, but there are no corresponding AAAA glue records.
  • gov to nlm.gov: Authoritative AAAA records exist for lhcns2.nlm.nih.gov, but there are no corresponding AAAA glue records.
  • gov to nlm.gov: Authoritative AAAA records exist for ns.nih.gov, but there are no corresponding AAAA glue records.
  • gov to nlm.gov: Authoritative AAAA records exist for ns2.nih.gov, but there are no corresponding AAAA glue records.
  • gov to nlm.gov: Authoritative AAAA records exist for ns3.nih.gov, but there are no corresponding AAAA glue records.
  • nlm.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. (2607:f220:41e:7055::72, 2607:f220:41e:7055::128, UDP_-_EDNS0_4096_D_KN)
  • nlm.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. (2607:f220:41e:7055::72, 2607:f220:41e:7055::128, UDP_-_EDNS0_4096_D_KN)
  • nlm.gov/NS: 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. (2607:f220:41e:7055::72, 2607:f220:41e:7055::128, UDP_-_EDNS0_4096_D_KN)
  • nlm.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. (2607:f220:41e:7055::72, 2607:f220:41e:7055::128, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • nlm.gov/TXT: 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. (2607:f220:41e:7055::72, 2607:f220:41e:7055::128, UDP_-_EDNS0_4096_D_KN)

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