sungard.com

Updated: 2021-09-08 19:23:25 UTC (1169 days ago) Update now

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

Notices

DNSSEC Authentication Chain

RRset status

Secure (6)

sungard.com/A
sungard.com/MX
sungard.com/NS
sungard.com/NSEC3PARAM
sungard.com/SOA
sungard.com/TXT

DNSKEY/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 status

Secure (2)

. to com
com to sungard.com

Notices

Errors (16)

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. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (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. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (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. See RFC 4035, Sec. 3.2.1. (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). See RFC 6891, Sec. 6.1.4. (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. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (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. See RFC 4035, Sec. 3.2.1. (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). See RFC 6891, Sec. 6.1.4. (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. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (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. See RFC 4035, Sec. 3.2.1. (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). See RFC 6891, Sec. 6.1.4. (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. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (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). See RFC 1035, Sec. 4.2. (107.162.154.76, 107.162.154.77, UDP_-_EDNS0_512_D_KN)
sungard.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
x0wpy34qav.sungard.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
sungard.com/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
sungard.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (28)

RRSIG sungard.com/A alg 10, id 37826: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG sungard.com/DNSKEY alg 10, id 37826: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG sungard.com/DNSKEY alg 10, id 37826: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG sungard.com/DNSKEY alg 10, id 37826: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG sungard.com/MX alg 10, id 37826: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG sungard.com/NS alg 10, id 37826: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG sungard.com/NSEC3PARAM alg 10, id 37826: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG sungard.com/SOA alg 10, id 37826: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG sungard.com/TXT alg 10, id 37826: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
sungard.com/DS (alg 8, id 20755): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
sungard.com/DS (alg 8, id 20755): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
sungard.com/DS (alg 8, id 20755): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
sungard.com/DS (alg 8, id 20755): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
sungard.com/DS (alg 8, id 25939): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
sungard.com/DS (alg 8, id 25939): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
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. See RFC 4509, Sec. 3.
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. See RFC 4509, Sec. 3.
sungard.com/DS (alg 8, id 52027): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
sungard.com/DS (alg 8, id 52027): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
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. See RFC 4509, Sec. 3.
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. See RFC 4509, Sec. 3.
sungard.com/DS (alg 8, id 65047): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
sungard.com/DS (alg 8, id 65047): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
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. See RFC 4509, Sec. 3.
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. See RFC 4509, Sec. 3.
sungard.com/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
sungard.com/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
sungard.com/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.