View on GitHub

DNSViz: A DNS visualization tool

genworth.com

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

RRset statusRRset status

Bogus (7)
  • genworth.com/A
  • genworth.com/MX
  • genworth.com/NS
  • genworth.com/NSEC3PARAM
  • genworth.com/NSEC3PARAM
  • genworth.com/SOA
  • genworth.com/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (2)
  • genworth.com/DNSKEY (alg 7, id 38034)
  • genworth.com/DNSKEY (alg 7, id 62669)
Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 61050)
  • com/DNSKEY (alg 13, id 19718)
  • com/DNSKEY (alg 13, id 29942)
  • com/DS (alg 13, id 19718)
  • genworth.com/DS (alg 7, id 8178)
Non_existent (1)
  • genworth.com/DNSKEY (alg 7, id 8178)

Delegation statusDelegation status

Bogus (1)
  • com to genworth.com
Secure (1)
  • . to com

NoticesNotices

Errors (7)
  • com to genworth.com: 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. (206.83.160.21, 206.83.168.21, UDP_-_EDNS0_4096_D_KN)
  • com to genworth.com: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no DS RR matched a DNSKEY with algorithm 7 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (206.83.160.21, 206.83.168.21, UDP_-_EDNS0_4096_D_KN)
  • 7bu0h.je2p1.genworth.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • genworth.com/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • genworth.com/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
  • genworth.com/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • genworth.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (35)
  • ./DNSKEY (alg 8, id 20326): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • ./DNSKEY (alg 8, id 61050): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • RRSIG genworth.com/A alg 7, id 62669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG genworth.com/A alg 7, id 62669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG genworth.com/DNSKEY alg 7, id 38034: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG genworth.com/DNSKEY alg 7, id 38034: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG genworth.com/DNSKEY alg 7, id 38034: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG genworth.com/DNSKEY alg 7, id 38034: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG genworth.com/DNSKEY alg 7, id 62669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG genworth.com/DNSKEY alg 7, id 62669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG genworth.com/DNSKEY alg 7, id 62669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG genworth.com/DNSKEY alg 7, id 62669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG genworth.com/MX alg 7, id 62669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG genworth.com/MX alg 7, id 62669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG genworth.com/NS alg 7, id 62669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG genworth.com/NS alg 7, id 62669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG genworth.com/NSEC3PARAM alg 7, id 62669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG genworth.com/NSEC3PARAM alg 7, id 62669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG genworth.com/SOA alg 7, id 62669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG genworth.com/SOA alg 7, id 62669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG genworth.com/SOA alg 7, id 62669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG genworth.com/SOA alg 7, id 62669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG genworth.com/SOA alg 7, id 62669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG genworth.com/TXT alg 7, id 62669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG genworth.com/TXT alg 7, id 62669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • com/DS (alg 13, id 19718): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • com/DS (alg 13, id 19718): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • genworth.com/DS (alg 7, id 8178): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • genworth.com/DS (alg 7, id 8178): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • genworth.com/CDS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • genworth.com/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 7bu0h.je2p1.genworth.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • genworth.com/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • genworth.com/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • genworth.com/CDNSKEY 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