View on GitHub

DNSViz: A DNS visualization tool

walgreens.com

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

RRset statusRRset status

Insecure (5)
  • walgreens.com/A
  • walgreens.com/MX
  • walgreens.com/NS
  • walgreens.com/SOA
  • walgreens.com/TXT
Secure (2)
  • com/SOA
  • com/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 18733)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC3 proving non-existence of walgreens.com/DS
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 53929)
  • com/DS (alg 8, id 30909)

Delegation statusDelegation status

Insecure (1)
  • com to walgreens.com
Secure (1)
  • . to com

NoticesNotices

Errors (3)
  • walgreens.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (204.15.116.132)
  • walgreens.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (204.15.116.132, UDP_-_NOEDNS_)
  • walgreens.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (204.15.116.132, UDP_-_NOEDNS_)
Warnings (2)
  • com to walgreens.com: The glue address(es) for ns7.walgreens.com (204.15.116.132) differed from its authoritative address(es) (204.15.119.56). See RFC 1034, Sec. 4.2.2.
  • walgreens.com/NS: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (2a02:26f0:117::40, 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