View on GitHub

DNSViz: A DNS visualization tool

aast.edu

Updated: 2024-02-20 00:15:24 UTC (12 months ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (5)
  • aast.edu/A
  • aast.edu/MX
  • aast.edu/NS
  • aast.edu/SOA
  • aast.edu/TXT
Secure (2)
  • edu/SOA
  • edu/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 30903)
  • NSEC3 proving non-existence of aast.edu/DS
  • edu/DNSKEY (alg 13, id 30678)
  • edu/DNSKEY (alg 13, id 35663)
  • edu/DS (alg 13, id 35663)

Delegation statusDelegation status

Insecure (1)
  • edu to aast.edu
Secure (1)
  • . to edu

NoticesNotices

Errors (2)
  • aast.edu zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (3.250.17.237)
  • aast.edu/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (3.250.17.237, TCP_-_EDNS0_4096_D_N)
Warnings (3)
  • edu to aast.edu: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the edu zone): aastmt3.aast.edu See RFC 1034, Sec. 4.2.2.
  • edu to aast.edu: The following NS name(s) were found in the delegation NS RRset (i.e., in the edu zone), but not in the authoritative NS RRset: aastmt2.aast.edu See RFC 1034, Sec. 4.2.2.
  • edu to aast.edu: The glue address(es) for aastmt2.aast.edu (3.250.17.237) differed from its authoritative address(es) (20.234.49.237). See RFC 1034, Sec. 4.2.2.

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