View on GitHub

DNSViz: A DNS visualization tool

magellanhealth.com

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

RRset statusRRset status

Secure (5)
  • magellanhealth.com/A
  • magellanhealth.com/MX
  • magellanhealth.com/NS
  • magellanhealth.com/SOA
  • magellanhealth.com/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26116)
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 31510)
  • com/DS (alg 8, id 30909)
  • magellanhealth.com/DNSKEY (alg 7, id 14282)
  • magellanhealth.com/DNSKEY (alg 7, id 20519)
  • magellanhealth.com/DNSKEY (alg 7, id 45274)
  • magellanhealth.com/DNSKEY (alg 7, id 55786)
  • magellanhealth.com/DS (alg 7, id 45274)
  • magellanhealth.com/DS (alg 7, id 55786)

Delegation statusDelegation status

Secure (2)
  • . to com
  • com to magellanhealth.com

NoticesNotices

Errors (4)
  • com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:500:856e::30, 2001:502:1ca1::30, 2001:503:83eb::30, 2001:503:a83e::2:30)
  • magellanhealth.com/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • dkfrjc1w8g.magellanhealth.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • magellanhealth.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (34)
  • RRSIG magellanhealth.com/A alg 7, id 20519: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG magellanhealth.com/DNSKEY alg 7, id 20519: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG magellanhealth.com/DNSKEY alg 7, id 20519: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG magellanhealth.com/DNSKEY alg 7, id 20519: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG magellanhealth.com/DNSKEY alg 7, id 20519: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG magellanhealth.com/DNSKEY alg 7, id 45274: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG magellanhealth.com/DNSKEY alg 7, id 45274: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG magellanhealth.com/DNSKEY alg 7, id 45274: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG magellanhealth.com/DNSKEY alg 7, id 45274: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG magellanhealth.com/DNSKEY alg 7, id 55786: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG magellanhealth.com/DNSKEY alg 7, id 55786: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG magellanhealth.com/DNSKEY alg 7, id 55786: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG magellanhealth.com/DNSKEY alg 7, id 55786: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG magellanhealth.com/MX alg 7, id 20519: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG magellanhealth.com/NS alg 7, id 20519: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG magellanhealth.com/SOA alg 7, id 20519: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG magellanhealth.com/TXT alg 7, id 20519: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • magellanhealth.com/A: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:18::254, UDP_-_EDNS0_4096_D_K)
  • magellanhealth.com/DNSKEY (alg 7, id 14282): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:18::254, UDP_-_EDNS0_4096_D_K)
  • magellanhealth.com/DNSKEY (alg 7, id 20519): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:18::254, UDP_-_EDNS0_4096_D_K)
  • magellanhealth.com/DNSKEY (alg 7, id 45274): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:18::254, UDP_-_EDNS0_4096_D_K)
  • magellanhealth.com/DNSKEY (alg 7, id 55786): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:18::254, UDP_-_EDNS0_4096_D_K)
  • magellanhealth.com/DNSKEY: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:18::254, UDP_-_EDNS0_512_D_K)
  • magellanhealth.com/DS (alg 7, id 45274): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • magellanhealth.com/DS (alg 7, id 45274): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • magellanhealth.com/DS (alg 7, id 55786): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • magellanhealth.com/DS (alg 7, id 55786): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • magellanhealth.com/MX: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:18::254, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • magellanhealth.com/SOA: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:18::254, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • magellanhealth.com/TXT: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:18::254, UDP_-_EDNS0_4096_D_K)
  • magellanhealth.com/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • dkfrjc1w8g.magellanhealth.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • magellanhealth.com/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • magellanhealth.com/DNSKEY 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