View on GitHub

DNSViz: A DNS visualization tool

_25._tcp.tolc-nsn.gov

Updated: 2021-03-01 17:15:34 UTC (1392 days 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

Bogus (2)
  • _25._tcp.tolc-nsn.gov/TLSA (NXDOMAIN)
  • _tcp.tolc-nsn.gov/NS (NXDOMAIN)
Secure (2)
  • tolc-nsn.gov/A
  • tolc-nsn.gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (13)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 42351)
  • NSEC proving non-existence of _25._tcp.tolc-nsn.gov/TLSA
  • NSEC proving non-existence of _tcp.tolc-nsn.gov/NS
  • gov/DNSKEY (alg 8, id 27306)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • tolc-nsn.gov/DNSKEY (alg 5, id 13800)
  • tolc-nsn.gov/DNSKEY (alg 5, id 29164)
  • tolc-nsn.gov/DNSKEY (alg 5, id 32055)
  • tolc-nsn.gov/DS (alg 5, id 29164)
  • tolc-nsn.gov/DS (alg 5, id 29164)

Delegation statusDelegation status

Secure (2)
  • . to gov
  • gov to tolc-nsn.gov

NoticesNotices

Errors (6)
  • NSEC proving non-existence of _25._tcp.tolc-nsn.gov/TLSA: No NSEC RR covers the SNAME (_25._tcp.tolc-nsn.gov). See RFC 4035, Sec. 3.1.3.2.
  • NSEC proving non-existence of _25._tcp.tolc-nsn.gov/TLSA: No NSEC RR covers the SNAME (_25._tcp.tolc-nsn.gov). See RFC 4035, Sec. 3.1.3.2.
  • NSEC proving non-existence of _tcp.tolc-nsn.gov/NS: No NSEC RR covers the SNAME (_tcp.tolc-nsn.gov). See RFC 4035, Sec. 3.1.3.2.
  • NSEC proving non-existence of _tcp.tolc-nsn.gov/NS: No NSEC RR covers the SNAME (_tcp.tolc-nsn.gov). See RFC 4035, Sec. 3.1.3.2.
  • tolc-nsn.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (64.25.66.6)
  • tolc-nsn.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (64.25.66.6, UDP_-_NOEDNS_)
Warnings (29)
  • RRSIG NSEC proving non-existence of _25._tcp.tolc-nsn.gov/TLSA alg 5, id 13800: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG NSEC proving non-existence of _25._tcp.tolc-nsn.gov/TLSA alg 5, id 32055: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG NSEC proving non-existence of _tcp.tolc-nsn.gov/NS alg 5, id 13800: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG NSEC proving non-existence of _tcp.tolc-nsn.gov/NS alg 5, id 32055: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tolc-nsn.gov/A alg 5, id 13800: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tolc-nsn.gov/A alg 5, id 32055: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tolc-nsn.gov/DNSKEY alg 5, id 13800: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tolc-nsn.gov/DNSKEY alg 5, id 13800: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tolc-nsn.gov/DNSKEY alg 5, id 13800: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tolc-nsn.gov/DNSKEY alg 5, id 29164: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tolc-nsn.gov/DNSKEY alg 5, id 29164: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tolc-nsn.gov/DNSKEY alg 5, id 29164: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tolc-nsn.gov/DNSKEY alg 5, id 32055: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tolc-nsn.gov/DNSKEY alg 5, id 32055: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tolc-nsn.gov/DNSKEY alg 5, id 32055: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tolc-nsn.gov/SOA alg 5, id 13800: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tolc-nsn.gov/SOA alg 5, id 13800: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tolc-nsn.gov/SOA alg 5, id 32055: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG tolc-nsn.gov/SOA alg 5, id 32055: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • gov to tolc-nsn.gov: The following NS name(s) were found in the delegation NS RRset (i.e., in the gov zone), but not in the authoritative NS RRset: dns2.tonation-nsn.gov See RFC 1034, Sec. 4.2.2.
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.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.
  • tolc-nsn.gov/DS (alg 5, id 29164): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • tolc-nsn.gov/DS (alg 5, id 29164): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • tolc-nsn.gov/DS (alg 5, id 29164): 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.
  • tolc-nsn.gov/DS (alg 5, id 29164): 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.
  • tolc-nsn.gov/CNAME 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