bradley.edu

Updated: 2022-06-13 19:34:20 UTC (894 days ago) Go to most recent »

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 (5)

bradley.edu/A
bradley.edu/MX
bradley.edu/NS
bradley.edu/SOA
bradley.edu/TXT

DNSKEY/DS/NSEC status

Secure (18)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 47671)
bradley.edu/DNSKEY (alg 10, id 18536)
bradley.edu/DNSKEY (alg 10, id 23732)
bradley.edu/DNSKEY (alg 10, id 32079)
bradley.edu/DNSKEY (alg 13, id 31881)
bradley.edu/DNSKEY (alg 13, id 8284)
bradley.edu/DNSKEY (alg 8, id 41949)
bradley.edu/DNSKEY (alg 8, id 64654)
bradley.edu/DS (alg 10, id 32079)
bradley.edu/DS (alg 10, id 32079)
bradley.edu/DS (alg 13, id 8284)
bradley.edu/DS (alg 13, id 8284)
bradley.edu/DS (alg 8, id 64654)
bradley.edu/DS (alg 8, id 64654)
edu/DNSKEY (alg 8, id 28065)
edu/DNSKEY (alg 8, id 43304)
edu/DS (alg 8, id 28065)

Delegation status

Secure (2)

. to edu
edu to bradley.edu

Notices

Errors (3)

bradley.edu zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:550:1:a::d, 2001:550:1:b::d, 2001:550:1:d::53, 2001:978:1:d::53)
bradley.edu/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:550:1:a::d, 2001:550:1:b::d, 2001:550:1:d::53, 2001:978:1:d::53, UDP_-_NOEDNS_)
bradley.edu/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:550:1:a::d, 2001:550:1:b::d, 2001:550:1:d::53, 2001:978:1:d::53, UDP_-_NOEDNS_)

Warnings (49)

RRSIG bradley.edu/A alg 10, id 18536: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/A alg 10, id 23732: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/DNSKEY alg 10, id 18536: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/DNSKEY alg 10, id 18536: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/DNSKEY alg 10, id 18536: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/DNSKEY alg 10, id 18536: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/DNSKEY alg 10, id 18536: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/DNSKEY alg 10, id 18536: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/DNSKEY alg 10, id 18536: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/DNSKEY alg 10, id 23732: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/DNSKEY alg 10, id 23732: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/DNSKEY alg 10, id 23732: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/DNSKEY alg 10, id 23732: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/DNSKEY alg 10, id 23732: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/DNSKEY alg 10, id 23732: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/DNSKEY alg 10, id 23732: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/DNSKEY alg 10, id 32079: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/DNSKEY alg 10, id 32079: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/DNSKEY alg 10, id 32079: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/DNSKEY alg 10, id 32079: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/DNSKEY alg 10, id 32079: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/DNSKEY alg 10, id 32079: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/DNSKEY alg 10, id 32079: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/MX alg 10, id 18536: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/MX alg 10, id 23732: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/NS alg 10, id 18536: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/NS alg 10, id 23732: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/SOA alg 10, id 18536: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/SOA alg 10, id 23732: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/TXT alg 10, id 18536: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bradley.edu/TXT alg 10, id 23732: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
bradley.edu/DS (alg 10, id 32079): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
bradley.edu/DS (alg 10, id 32079): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
bradley.edu/DS (alg 10, id 32079): 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.
bradley.edu/DS (alg 10, id 32079): 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.
bradley.edu/DS (alg 13, id 8284): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
bradley.edu/DS (alg 13, id 8284): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
bradley.edu/DS (alg 13, id 8284): 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.
bradley.edu/DS (alg 13, id 8284): 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.
bradley.edu/DS (alg 8, id 64654): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
bradley.edu/DS (alg 8, id 64654): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
bradley.edu/DS (alg 8, id 64654): 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.
bradley.edu/DS (alg 8, id 64654): 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.
edu to bradley.edu: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the edu zone): auth0-eu.dns.cogentco.com, auth0-na.dns.cogentco.com See RFC 1034, Sec. 4.2.2.
bradley.edu/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
bradley.edu/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
bradley.edu/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
ilry5h0jg4.bradley.edu/A has warnings; select the "Denial of existence" DNSSEC option to see them.
bradley.edu/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.