View on GitHub

DNSViz: A DNS visualization tool

cn-ecg.cfe.uber.com

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

RRset statusRRset status

Insecure (2)
  • cn-ecg.cfe.uber.com/A
  • uber.com/SOA
Secure (1)
  • com/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26838)
  • NSEC3 proving non-existence of uber.com/DS
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 39343)
  • com/DS (alg 8, id 30909)

Delegation statusDelegation status

Incomplete (1)
  • uber.com to cfe.uber.com
Insecure (1)
  • com to uber.com
Secure (1)
  • . to com

NoticesNotices

Errors (1)
  • uber.com to cfe.uber.com: No delegation NS records were detected in the parent zone (uber.com). This results in an NXDOMAIN response to a DS query (for DNSSEC), even if the parent servers are authoritative for the child. See RFC 1034, Sec. 4.2.2. (204.74.66.126, 204.74.67.126, 204.74.110.126, 204.74.111.126, 2001:502:4612::27e, 2001:502:f3ff::27e, 2610:a1:1014::27e, 2610:a1:1015::27e, 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