View on GitHub

DNSViz: A DNS visualization tool

questdiagnostics.com

« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

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

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 47671)
  • NSEC3 proving non-existence of questdiagnostics.com/DS
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 37269)
  • com/DS (alg 8, id 30909)

Delegation statusDelegation status

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

NoticesNotices

Warnings (4)
  • ./DNSKEY (alg 8, id 20326): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
  • ./DNSKEY (alg 8, id 47671): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
  • com to questdiagnostics.com: The glue address(es) for ns1.questdiagnostics.com (216.203.83.234) differed from its authoritative address(es) (216.203.80.72). See RFC 1034, Sec. 4.2.2.
  • com to questdiagnostics.com: The glue address(es) for ns2.questdiagnostics.com (216.203.91.234) differed from its authoritative address(es) (216.203.88.72). See RFC 1034, Sec. 4.2.2.

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