View on GitHub

DNSViz: A DNS visualization tool

yukimochi.me

Updated: 2020-04-17 17:06:11 UTC (5 years 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 (4)
  • yukimochi.me/A
  • yukimochi.me/NS
  • yukimochi.me/SOA
  • yukimochi.me/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (2)
  • yukimochi.me/DNSKEY (alg 13, id 2371)
  • yukimochi.me/DNSKEY (alg 13, id 34505)
Secure (9)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 48903)
  • me/DNSKEY (alg 7, id 2569)
  • me/DNSKEY (alg 7, id 53233)
  • me/DNSKEY (alg 7, id 55358)
  • me/DNSKEY (alg 7, id 56057)
  • me/DS (alg 7, id 2569)
  • me/DS (alg 7, id 2569)
  • yukimochi.me/DS (alg 13, id 2371)

Delegation statusDelegation status

Bogus (1)
  • me to yukimochi.me
Secure (1)
  • . to me

NoticesNotices

Errors (3)
  • me to yukimochi.me: 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. (173.245.58.95, 173.245.59.224, 2606:4700:50::adf5:3a5f, 2606:4700:58::adf5:3be0, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • yukimochi.me/DS (alg 13, id 2371): The cryptographic hash in the Digest field of the DS RR does not match the computed value. See RFC 4035, Sec. 5.2.
  • yukimochi.me/DS (alg 13, id 2371): The cryptographic hash in the Digest field of the DS RR does not match the computed value. See RFC 4035, Sec. 5.2.
Warnings (18)
  • RRSIG me/DNSKEY alg 7, id 2569: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG me/DNSKEY alg 7, id 2569: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG me/DNSKEY alg 7, id 2569: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG me/DNSKEY alg 7, id 2569: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG me/DNSKEY alg 7, id 53233: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG me/DNSKEY alg 7, id 53233: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG me/DNSKEY alg 7, id 53233: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG me/DNSKEY alg 7, id 53233: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG me/DNSKEY alg 7, id 55358: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG me/DNSKEY alg 7, id 55358: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG me/DNSKEY alg 7, id 55358: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG me/DNSKEY alg 7, id 55358: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG yukimochi.me/DS alg 7, id 55358: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • me/DS (alg 7, id 2569): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • me/DS (alg 7, id 2569): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • me/DS (alg 7, id 2569): 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.
  • me/DS (alg 7, id 2569): 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.
  • yukimochi.me/DS 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