View on GitHub

DNSViz: A DNS visualization tool

sungard.com

Updated: 2021-09-08 19:23:25 UTC (900 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Secure (6)
  • sungard.com/A
  • sungard.com/MX
  • sungard.com/NS
  • sungard.com/NSEC3PARAM
  • sungard.com/SOA
  • sungard.com/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (16)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26838)
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 39343)
  • com/DS (alg 8, id 30909)
  • sungard.com/DNSKEY (alg 10, id 37826)
  • sungard.com/DNSKEY (alg 8, id 25939)
  • sungard.com/DNSKEY (alg 8, id 62403)
  • sungard.com/DS (alg 8, id 1651)
  • sungard.com/DS (alg 8, id 20755)
  • sungard.com/DS (alg 8, id 24970)
  • sungard.com/DS (alg 8, id 25939)
  • sungard.com/DS (alg 8, id 25939)
  • sungard.com/DS (alg 8, id 31594)
  • sungard.com/DS (alg 8, id 52027)
  • sungard.com/DS (alg 8, id 65047)
Non_existent (6)
  • sungard.com/DNSKEY (alg 8, id 1651)
  • sungard.com/DNSKEY (alg 8, id 20755)
  • sungard.com/DNSKEY (alg 8, id 24970)
  • sungard.com/DNSKEY (alg 8, id 31594)
  • sungard.com/DNSKEY (alg 8, id 52027)
  • sungard.com/DNSKEY (alg 8, id 65047)

Delegation statusDelegation status

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

NoticesNotices

Errors (12)
  • com to sungard.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. (107.162.154.76, 107.162.154.77, TCP_-_EDNS0_4096_)
  • com to sungard.com: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. (107.162.154.76, 107.162.154.77, TCP_-_EDNS0_4096_)
  • sungard.com/DNSKEY (alg 10, id 37826): DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 10 times) with the DO bit set. (107.162.154.76, 107.162.154.77, TCP_-_EDNS0_4096_)
  • sungard.com/DNSKEY (alg 10, id 37826): No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). (107.162.154.76, 107.162.154.77, UDP_-_EDNS0_4096_D_KN)
  • sungard.com/DNSKEY (alg 10, id 37826): The DNSSEC records necessary to validate the response could not be retrieved from the server. (107.162.154.76, 107.162.154.77, UDP_-_EDNS0_4096_D_KN)
  • sungard.com/DNSKEY (alg 8, id 25939): DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 10 times) with the DO bit set. (107.162.154.76, 107.162.154.77, TCP_-_EDNS0_4096_)
  • sungard.com/DNSKEY (alg 8, id 25939): No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). (107.162.154.76, 107.162.154.77, UDP_-_EDNS0_4096_D_KN)
  • sungard.com/DNSKEY (alg 8, id 25939): The DNSSEC records necessary to validate the response could not be retrieved from the server. (107.162.154.76, 107.162.154.77, UDP_-_EDNS0_4096_D_KN)
  • sungard.com/DNSKEY (alg 8, id 62403): DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 10 times) with the DO bit set. (107.162.154.76, 107.162.154.77, TCP_-_EDNS0_4096_)
  • sungard.com/DNSKEY (alg 8, id 62403): No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). (107.162.154.76, 107.162.154.77, UDP_-_EDNS0_4096_D_KN)
  • sungard.com/DNSKEY (alg 8, id 62403): The DNSSEC records necessary to validate the response could not be retrieved from the server. (107.162.154.76, 107.162.154.77, UDP_-_EDNS0_4096_D_KN)
  • sungard.com/DNSKEY: No response was received from the server over UDP (tried 4 times). (107.162.154.76, 107.162.154.77, UDP_-_EDNS0_512_D_KN)
Warnings (21)
  • RRSIG sungard.com/A alg 10, id 37826: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
  • RRSIG sungard.com/DNSKEY alg 10, id 37826: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
  • RRSIG sungard.com/DNSKEY alg 10, id 37826: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
  • RRSIG sungard.com/DNSKEY alg 10, id 37826: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
  • RRSIG sungard.com/MX alg 10, id 37826: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
  • RRSIG sungard.com/NS alg 10, id 37826: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
  • RRSIG sungard.com/NSEC3PARAM alg 10, id 37826: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
  • RRSIG sungard.com/SOA alg 10, id 37826: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
  • RRSIG sungard.com/TXT alg 10, id 37826: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
  • sungard.com/DS (alg 8, id 25939): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
  • sungard.com/DS (alg 8, id 25939): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
  • sungard.com/DS (alg 8, id 25939): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
  • sungard.com/DS (alg 8, id 25939): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
  • sungard.com/DS (alg 8, id 52027): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
  • sungard.com/DS (alg 8, id 52027): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
  • sungard.com/DS (alg 8, id 52027): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
  • sungard.com/DS (alg 8, id 52027): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
  • sungard.com/DS (alg 8, id 65047): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
  • sungard.com/DS (alg 8, id 65047): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
  • sungard.com/DS (alg 8, id 65047): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
  • sungard.com/DS (alg 8, id 65047): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.

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